wx 2.6 cvs branch: configure --prefix problem w/ gcc in cygwin

[John Labenski]

On 12/1/06, Vadim Zeitlin <vadim at wxwindows.org> wrote:
> On Thu, 30 Nov 2006 15:05:34 -0500 John Labenski <jlabenski at gmail.com> wrote:
>
> JL> Using wxWidgets 2.6 from CVS I get this error using cygwin in MSW 2000.
> JL>
> JL> $ ./config_gcc_static_debug >config_gcc_static_debug_out
> JL> configure: error: expected an absolute directory name for --exec_prefix: NONE
>
>  This is pretty strange. Looking at configure code (you can easily find the
> relevant place by searching for the error message), NONE is explicitly
> handled for exec_prefix. Could there be a stray space in it somehow?

I dunno, I'll check. It is the exact same script I used before since I
copy it out of the build dir I create, delete the whole build dir,
recreate it, and copy the script back. See below for why I use a
separate build dir.

> JL> where the script config_gcc_static_debug contains this
> JL>
> JL> ../configure \
> JL> --prefix=/mnt/d/wxCVS/wxWidgets/wxWidgets_26/wxWidgets/config_gcc_static_debug \
>
>  What is /mnt/d? The DOS drives are usually accessed as /cygdrive/d under
> Cygwin.

I mount the D: drive in mnt/d with DOS line endings so that I don't
have CRLF trouble with CVS. This is how I've been doing it with
success for years.

> JL> and yes the --prefix dir is correct and points to the location of the
> JL> config_gcc_static_debug script.
>
>  But it should point to a directory... I really don't understand what are
> you trying to do.

Just to be sure, I checkout the 26 branch using cygwin into
D:\wxCVS\wxWidgets\wxWidgets_26\wxWidgets
eg. /mnt/d/wxCVS/wxWidgets/wxWidgets_26/wxWidgets
Then I create
/mnt/d/wxCVS/wxWidgets/wxWidgets_26/wxWidgets/config_gcc_static_debug
and run the script above in that dir so I don't pollute the root dir
of wxWidgets. This allows me to have multiple builds, debug, release,
dll, etc. I can also very easily completely delete any one of them and
rebuild it.

I'll try deleting everything and starting over tomorrow, but it
doesn't make sense since the last cvs update I did didn't modify
configure, just a few headers and src files. Maybe I've updated
cygwin's autoconf stuff in the meantime?

Thanks,
    John Labenski