ln -vs libgcc.a `gcc -print-libgcc-file-name

jpeters · 03-26-2009, 01:13 AM

From 5.5. GCC-4.3.2 -Pass 1

Can't create this link, as the file already exists in the host system:

Code:

ln -vs libgcc.a `gcc -print-libgcc-file-name | \
    sed 's/libgcc/&_eh/'`

Code:

ln: creating symbolic link `/usr/lib/gcc/i486-t2-linux-gnu/4.2.2/libgcc_eh.a': File exists

knudfl · 03-26-2009, 03:02 AM

When you are using the correct 'configure' line
with " --prefix=/tools " for install destination,
gcc is installed to //tools and then ...

.. please go to //tools and make the symbolic link
with the just installed gcc result.

LFS should in no way be mixed up with your host system.
.....

jpeters · 03-26-2009, 04:15 AM

Okay...I linked /tools/lib....../4.3.2/libgcc.a --> libgcc_eh.a

Command 'gcc -print-libgcc-file-name' prints from /usr/lib/gcc.
Otherwise, files are correctly installed into /tools.

I also just found I couldn't make Linux API headers (5.6) while in lfs usr (as the book
recommends to keep host separate), because dependencies required compiling from root (which worked fine).

jpeters · 03-26-2009, 10:40 PM

Found the problem: lfs wasn't reading the local .bashrc file, so path to /tools wasn't in PATH.
(I was using a login user, since puppy didn't have shadow-utils). Now it's working correctly.