build from newlib directory broken for cygwin
Corinna Vinschen
vinschen@redhat.com
Mon May 19 19:38:00 GMT 2003
On Sat, May 17, 2003 at 04:54:30PM -0400, Christopher Faylor wrote:
> I just wanted to enter for the record, the fact that I can no longer
> build a cygwin version of newlib by cd'ing to a newlib build directory
> and typing "make".
>
> I know that Corinna knows about this problem but I thought I should
> probably archive it for the record.
I can't reproduce that problem, though. Did you reconfigure once from
the top level? After having done this once, a `make' inside of newlib
has all the correct paths AFAICS:
gcc \
-L/build/cygwin/bin/i686-pc-cygwin/winsup \
-L/build/cygwin/bin/i686-pc-cygwin/winsup/cygwin \
-L/build/cygwin/bin/i686-pc-cygwin/winsup/w32api/lib \
-isystem /src/cygwin/src/winsup/include \
-isystem /src/cygwin/src/winsup/cygwin/include \
-isystem /src/cygwin/src/winsup/w32api/include \
-B/build/cygwin/bin/i686-pc-cygwin/newlib/ \
-isystem /build/cygwin/bin/i686-pc-cygwin/newlib/targ-include \
-isystem /src/cygwin/src/newlib/libc/include \
-DPACKAGE=\"newlib\" -DVERSION=\"1.11.0\" \
-I. \
-I/src/cygwin/src/newlib/libm/common \
[...]
It builds fine on my system. I even removed /usr/include entirely to
get no side effects by searching system paths.
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:vinschen@redhat.com
More information about the Newlib
mailing list