This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: later w32api package required to build cygwin
David Starks-Browning wrote:
> workaround for building Cygwin is to replace -isystem with -I in
> FLAGS_FOR_TARGET. At least, I think that will work. I'll try it now.
>
David,
that doesn't seem to work either and I don't hink I get quite as far. This
time I got:
/usr/bin/c++ -L/usr/develop/obj/i686-pc-cygwin/winsup
-L/usr/develop/obj/i686-pc
-cygwin/winsup/cygwin -L/usr/develop/obj/i686-pc-cygwin/winsup/w32api/lib
-isyst
em /usr/develop/src/winsup/include -isystem
/usr/develop/src/winsup/cygwin/inclu
de -I /usr/develop/src/winsup/w32api/include -isystem
/usr/develop/src/newlib/li
bc/sys/cygwin -isystem /usr/develop/src/newlib/libc/sys/cygwin32
-B/usr/develop/
obj/i686-pc-cygwin/newlib/ -isystem
/usr/develop/obj/i686-pc-cygwin/newlib/targ-
include -isystem /usr/develop/src/newlib/libc/include -c -nostdinc++ -nostdinc
-
DHAVE_CONFIG_H -g -O2 -Wall -Wwrite-strings -fno-common -pipe -Winline
-fbuilti
n -I. -I/usr/develop/src/winsup/cygwin
-I/usr/develop/src/newlib/libc/sys/c
ygwin/include -I/usr/develop/src/winsup/cygwin/config/i386
-I/usr/lib/gcc-lib/i
686-pc-cygwin/3.2//include -fno-rtti -fno-exceptions -o ./cygthread.o
/usr/devel
op/src/winsup/cygwin/cygthread.cc
/usr/develop/src/winsup/cygwin/cygthread.cc: In static member function `static
DWORD cygthread::stub(void*)':
/usr/develop/src/winsup/cygwin/cygthread.cc:31: `DECLARE_TLS_STORAGE'
undeclared (first use this function)
/usr/develop/src/winsup/cygwin/cygthread.cc:31: (Each undeclared identifier is
reported only once for each function it appears in.)
make[2]: *** [cygthread.o] Error 1
make[2]: Leaving directory `/usr/develop/obj/i686-pc-cygwin/winsup/cygwin'
make[1]: *** [cygwin] Error 1
make[1]: Leaving directory `/usr/develop/obj/i686-pc-cygwin/winsup'
make: *** [all-target-winsup] Error 2
One thing I just noticed in the above is that when I changed the -isystem to -I
for the /usr/develop/src/winsup/w32api/include but looking at the above I
noticed that even after that part of the command we have:
-I/usr/lib/gcc-lib/i686-pc-cygwin/3.2//include
isn't this still going to circumvent our using -I
/usr/develop/src/winsup/w32api/include
Just curious.
bk