Hi Dan!
I noticed your second post, but just to make sure I try both tests (the one
from this mail and the one from the other mail).
Am Montag, 15. Mai 2006 23:30 schrieb Dan Nicholson:
> On 5/15/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
> > Hi once again!
> >
>
> OK, so let's try to set this up just as the environment was during make.
Here it comes:
01.) Start a shell as user "root".
02.) export LFS=/media/sdb3
03.) mount /dev/sdb3 $LFS
04.) mount --bind /dev $LFS/dev
05.) mount -vt devpts devpts $LFS/dev/pts
06.) mount -vt tmpfs shm $LFS/dev/shm
07.) mount -vt proc proc $LFS/proc
08.) mount -vt sysfs sysfs $LFS/sys
09.) chroot "$LFS" /tools/bin/env -i \
HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
/tools/bin/bash --login +h
10.) cd /sources/gcc-build/
> $ cd /sources/gcc-build/gcc
11.) cd gcc/
> $ cat > dummy.c << "EOF"
> #include <stdio.h>
> main(){}
> EOF
12.) cat > dummy.c << "EOF"
13.) #include <stdio.h>
14.) main(){}
15.) 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
16.) /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.
Step 16. results in "bash: -B/usr/i686-pc-linux-gnu/bin/: No such file or
directory". An "ls /usr" shows the following: "bin doc include info lib
local man sbin share src"
So I took a try with 16b.
16b.) /sources/gcc-build/gcc/xgcc -B/sources/gcc-build/gcc/ \
-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
Step 16b. returns the following:
xgcc: -I../../gcc-4.0.3/gcc/../include: No such file or directory
xgcc: -H: No such file or directory
dummy.c:1:19: error: stdio.h: No such file or directory
dummy.c:2: warning: return type defaults to 'int'
dummy.c:2: warning: function declaration isn't a prototype
dummy.c: In function 'main':
dummy.c:2: warning: old-style function definition
> $ /sources/gcc-build/gcc/xgcc -v dummy.c | grep include
17.) /sources/gcc-build/gcc# /sources/gcc-build/gcc/xgcc -v dummy.c | grep
include
RESULT:
=====
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.0.3/configure --prefix=/usr --libexecdir=/usr/lib
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-clocale=gnu --enable-languages=c,c++
Thread model: posix
gcc version 4.0.3
cc1 -quiet -v -iprefix
/sources/gcc-build/gcc/../lib/gcc/i686-pc-linux-gnu/4.0.3/
dummy.c -quiet -dumpbase dummy.c -mtune=pentiumpro -auxbase
dummy -version -o /tmp/ccLFWB4W.s
xgcc: installation problem, cannot exec 'cc1': No such file or directory
> 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.
Can you give me some new hints on what to try next?
> --
> Dan
Leonhard.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
