LFS V6.3 5.5. Linux-18.104.22.168 API Headers
lee.mccafferty at gmail.com
Tue Jan 15 19:39:39 PST 2008
On Tue, 2008-01-15 at 18:04 -0800, Dan Nicholson wrote:
> On Jan 15, 2008 5:33 PM, Lee McCafferty <lee.mccafferty at gmail.com> wrote:
> > On Tue, 2008-01-15 at 17:22 -0800, Dan Nicholson wrote:
> > >
> > > It appears you're still using your host's gcc instead of the one at
> > > /tools/bin/gcc. Perhaps you missed the /tools/bin/cc -> gcc symlink?
> > > Maybe /tools/bin is not at the beginning of your PATH? What's the
> > > output of `which cc' and `which gcc'?
> > >
> > > --
> > > Dan
> > Wow, speedy reply. Thanks. That could be the problem, although I did do
> > the symlink I may have done it wrong.
> > which cc gives -> /usr/bin/cc
> > which gcc gives -> /usr/bin/gcc
> > If that should be /tools/bin/cc then I have indeed done it wrong.
> Yep, that's a problem. You'll have to start Ch. 5 over because the gcc
> pass 1 build needs to find /tools/bin/ld to do the proper feature
> tests. In addition to having /tools/bin first in $PATH, also make sure
> that that you have the environment setup correctly so `set +h' is run
> during when you switch to the lfs user. You can see if this is the
> case if you do `echo $-' and "h" is _not_ there. If "h" is there, you
> should back up to Ch. 4.4 and make sure that you have that all worked
> out correctly.
Thanks for your help, I will go back over the steps tomorrow. One last
question, in which directory should I create the symlink
to /tools/bin/cc ?
More information about the lfs-support