Creating a symlink to libgcc.a
Section 5.5.1 in LFS Version 6.8 and I'm using Fedora 15 as the host system.
Quote:
Code:
ln: failed to create symbolic link 'x86_64-lfs-linux-gnu-gcc -print-libgcc-file-name | sed \'s/libgcc/&_eh\'': No such file or directory Code:
/mnt/lfs/tools/bin/x86_64-lfs-linux-gnu-gcc Code:
/mnt/lfs/sources/gcc-build/gcc/libgcc.a Is this a place where I'll have to deviate from the book because I'm using x86_64? If so, how would I modify the command and where can I learn more about why? |
I would guess it's complaining that libgcc.a doesn't exist in the directory you're running it in. What directory are you in? And which should you be in?
|
The book was unclear about it.
I've tried /mnt/lfs/sources/gcc-build/ because that's where I already was. I didn't want to create a seemingly correct link and screw up glibc later so I haven't tried any others. Would /mnt/lfs/tools/lib/gcc/x86_64-lfs-linux-gnu/4.5.2/ be the correct one? Or maybe /mnt/lfs/tools/bin/? |
Hi,
This looks strange: Quote:
Are you sure you used back-ticks and not single quotes? I.e.: Code:
`$LFS_TGT-gcc -print-libgcc-file-name | sed 's/libgcc/&_eh/'` There's no need to deviate from the book at any point, it works as described. |
I wasn't aware that there was a difference between backticks and single quotes.
You'd figure I would have learned that in school at some point... I'll jump right on it when I get home from work and I'll let you know how it goes. Thank you both for your help. |
You're welcome :)
|
Worked first try.
|
All times are GMT -5. The time now is 08:10 PM. |