Got it. Thanks. It's relative to /lib, not $LFS/sources/gcc-build as I had thought initially.
I'll have another look at ln(1). On 03/21/2012 10:25 PM, Ken Moffat wrote: > On Wed, Mar 21, 2012 at 09:54:18PM +0200, Alexander Kapshuk wrote: > >> (6). While still in $LFS/sources/gcc-build, I ran ln -sv ../usr/bin/cpp >> /lib; And this is where I found it confusing, ../usr/bin/cpp == >> $LFS/sources/usr/bin/cpp; but /usr/bin/cpp isn't found in $LFS/sources. >> It's found is $LFS/usr/bin/cpp; I thought that ln was supposed to create >> a link to an existing file whether using an absolute or a relative path; >> >> I hope I'm making sense here. >> >> > The 'ln' command has many different ways of being invoked (see 'man > ln'). In this case, ../usr/bin/ is relative to /lib/ so we create > /lib/cpp as a symlink to /usr/bin/cpp. Similarly, the next > instruction creates a symlink to /usr/bin/gcc called /usr/bin/cc. > > ĸen > -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
