This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.7 installation failed (on network drive?)
Corinna Vinschen wrote:
>>> cvs -d :pserver:firstname.lastname@example.org:/cvs/cygwin-apps setup
>>> CC=gcc-3 configure
>>> make 'CFLAGS=-g'
>> So I don't need to switch set-gcc-default-3.sh, thanks.
>> Actually, I already checked out and compiled (after installing a
>> bunch of dependencies) over night after cgf's pointer to
>> However, I didn't include the -g flag, assuming that leaving out the
>> final 'strip' step might suffice.
Only because the default CFLAGS has -g in it; if you do need to override it,
you must specifiy -g yourself.
> The important thing here is to avoid the default -O2 flag. It makes
> debugging a lot harder.
I'd recommend using CFLAGS='-g3 -O0' myself. It's worth having the debug
info level turned right up.
FTR, I configure like this:
$ ./configure -C --disable-shared --host=i686-pc-mingw32 \
--build=i686-pc-cygwin CC="gcc-3 -mno-cygwin" CXX="g++-3 -mno-cygwin"
CC_FOR_TARGET="gcc-3 -mno-cygwin" CC_FOR_BUILD="gcc-3 -mno-cygwin" \
CXX_FOR_TARGET="g++-3 -mno-cygwin" --disable-shared
I need to go back and check whether all of those are strictly necessary, but
I did find gcc-4 kept creeping back into my builds without them. IIRC, the
gpg-error lib needs to run a generator exe during the build, and I figured we
should probably build that as a mingw exe too, hence the _FOR_BUILD settings.
I'm not sure if the FOR_TARGET settings are needed still, I wasn't systematic
in testing this, just kept adding settings until gcc-4 stopped showing up in
the build logs.