gcc/chroot env- [argv.o] - persists

Barry barry at hartford.uconn.edu
Tue Jan 2 14:15:02 PST 2001


Bill Suit wrote:
> 
> On Tuesday 02 January 2001 04:14 pm, you wrote:
> > > root:~# gcc --verbose
> > > Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/specs
> > > gcc version 2.95.2 19991024 (release)
> > > root:~#
> > >
> > > I don't know where the rest of you output comes from.
> >
> > that's correct. you actually have to compile a source file for the other
> > info to show up> That's why, after a 'make bootstrap' failed, you must run
> > this and show us the output:
> >
> > cd gcc-build/libiberty
> > gcc --verbose -c -DHAVE_CONFIG_H \
> > -march=i586 -I. -I../../gcc-2.95.2/libiberty/../include \
> > -fpic .../../gcc-2.95.2/libiberty/argv.c -o pic/argv.o
> >
> > show us that output
> 
> The output from the chroot env:
> 
> root:/usr/src/gcc-build/libiberty# gcc --verbose -c -DHAVE_CONFIG_H \
> > -march=i586 -I. -I../../gcc-2.95.2/libiberty/../include \
> > -fpic .../../gcc-2.95.2/libiberty/argv.c -o pic/argv.o
> gcc: .../../gcc-2.95.2/libiberty/argv.c: No such file or directory
> Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/specs
> gcc version 2.95.2 19991024 (release)
> root:/usr/src/gcc-build/libiberty#
> 
> I hope this is what you were looking for :>) Bill

tell me what you get when you type 

ls /usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/include

do this in the chroot'ed environment...

this should shed some light on the situation...

-- 
Unsubscribe: send email to lfs-apps-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message




More information about the blfs-support mailing list