creating a simlink after gcc-4.4.1 package has been installed
Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Hello,
I use LFS 6.5 book ver, my host system Centos 5.2
I did already install binutils and while installing gcc-4.4.1 package, the last thing to do is to create the symlink for libgcc_eh.a :
Code:
Using --disable-shared means that the libgcc_eh.a file isn't created and installed. The Glibc package
depends on this library as it uses -lgcc_eh within its build system. This dependency can be satisfied by creating a
symlink to libgcc.a, since that file will end up containing the objects normally contained in libgcc_eh.a:
ln -vs libgcc.a `$LFS_TGT-gcc -print-libgcc-file-name | \
sed 's/libgcc/&_eh/'`
a little bit confusing me, what is $LFS_TGT-gcc, I got $LFS_TGT variable defind and when I try to create the symlink following the command above it complaing me that:
Code:
ln -vs libgcc.a `$LFS_TGT-gcc -print-libgcc-file-name | \
> sed 's/libgcc/&_eh/'`
bash: i686-lfs-linux-gnu-gcc: command not found
create symbolic link `./libgcc.a' to `libgcc.a'
Just, I guess ,I missed something through reading the book but still could not find the problem, where $LFS_TGT-gcc definition took from
The question mark [previous post was edited during my reply] confuses me a bit. I have to assume you tried both commands and both have the same (failed) result.
The question mark [previous post was edited during my reply] confuses me a bit. I have to assume you tried both commands and both have the same (failed) result.
You were rigth I did some edit to my original post
Code:
$echo $PATH
/tools/bin:/bin:/usr/bin
Quote:
ls -ld /tools/i686*
drwxr-xr-x 4 lfs lfs 4096 Oct 25 00:03 /tools/i686-lfs-linux-gnu
Code:
ls -l /tools/bin/i686*gcc
/bin/ls: i686*gcc : No such file or directory
strange, it is look like I don't have file tools/bin/i686-lfs-linux-gnu-gcc installed
By the way, I tried to install this package on another host(this time it is Suse 10 server) machine, and here there is a
Code:
[lfs@suseLFS:/lfs> ls -l tools/bin/i6*gcc
-rwxr-xr-x 2 lfss lfss 438499 Oct 26 20:22 tools/bin/i686-lfs-linux-gnu-gcc
I got this file
after installation has been complited, I successfully created symlink to libgcc.a file
What could be missed on my Centos 5.2 host system? Actually the quitions is why this file did not created, while compiltion and installation of gcc package
1) Centos 5.2, as installed, isn't a suitable host for building LFS (did you do the iv. Host System Requirements step and all was ok?)
2) Something went wrong in the previous steps (either binutils or gcc).
If the first point is not the issue then I would suggest removing what you have done so far (I'm talking about chapter 5) and start over. Double check each step to see if anything odd happens.
If the first point is not the issue then I would suggest removing what you have done so far (I'm talking about chapter 5) and start over. Double check each step to see if anything odd happens.
This is already the second time (and I guess the last one ) when I remove and rebuild my LFS system FROM THE SCRATCH . This time is the same to previas one, I don't know what was the problem exactly ,but cleaning the system totally helped me to install gcc pack successfuly at this time. I suppose that, it happend me throgh copy and past stuffs from the book, honestly said, I did not check things twice, so I guess, that is THE problem of mine
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.