On 5/15/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
Hi once again!
Am Sonntag, 14. Mai 2006 23:05 schrieb Mag. Leonhard Landrock:
> Am Sonntag, 14. Mai 2006 20:41 schrieb Dan Nicholson:
> >
> > cat > dummy.c << "EOF"
> > #include <stdio.h>
> > main(){}
> > EOF
> >
> > cc -H dummy.c
Let's try this check again with xgcc and see what's going on. See
below for more details.
/sources/gcc-build/gcc/xgcc -B/sources/gcc-build/gcc/
-B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem
/usr/i686-pc-linux-gnu/include -isystem /usr/i686-pc-linux-gnu/sys-include -O2
-DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -isystem ./include -I. -I. -I../../gcc-4.0.3/gcc
-I../../gcc-4.0.3/gcc/. -I../../gcc-4.0.3/gcc/../include
-I../../gcc-4.0.3/gcc/../libcpp/include -g0 -finhibit-size-directive
-fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss
-fno-unit-at-a-time -fno-omit-frame-pointer
\
-c ../../gcc-4.0.3/gcc/crtstuff.c -DCRT_BEGIN \
-o crtbegin.o
OK, so let's try to set this up just as the environment was during make.
$ cd /sources/gcc-build/gcc
$ cat > dummy.c << "EOF"
#include <stdio.h>
main(){}
EOF
$ /sources/gcc-build/gcc/xgcc -B/sources/gcc-build/gcc/
-B/usr/i686-pc-linux-gnu/bin/ \
-B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include \
-isystem /usr/i686-pc-linux-gnu/sys-include -O2 -DIN_GCC -W -Wall \
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition \
-isystem ./include -I. -I. -I../../gcc-4.0.3/gcc -I../../gcc-4.0.3/gcc/. \
-I../../gcc-4.0.3/gcc/../include -I../../gcc-4.0.3/gcc/../libcpp/include \
-H dummy.c
Hopefully there's no hidden environment settings there that would
affect this test. You could also do this simpler test just to see
where xgcc looks for headers by default.
$ /sources/gcc-build/gcc/xgcc -v dummy.c | grep include
I believe it should be finding the headers in /usr/include, but I
might be wrong. Otherwise, it would find them in /tools/include.
There was some discussion about this a few months back.
2.) Within the "chroot environment" I
did "/sources/gcc-build/gcc/xgcc -print-search-dirs"
<snip>
That all looks correct to me, but unfortunately it doesn't give us the
header search path.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
