Binutils-188.8.131.52.2.2 - Pass 1 stuck up after make install
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.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Re: Re: Binutils-184.108.40.206.2.2 - Pass 1 stuck up after make install
Originally posted by Andrew Benton This suggests that make did not go well. Did it end with an error? If not, why was the ld folder not created?
Please tell me how to find the error. If Binutils is the first package to be installed why there should be an error? Is it depending upon what else is available on the host system? I don't understand what is meant by fourth line from top on Binutils page in the book:
Installation depends on: Bash, Bison, Coreutils, Diffutils, Flex, GCC, Gettext, Glibc, Grep, M4, Make, Perl, Sed, and Texinfo
How does it depend upon the packages not yet installed?
You need to install those things on your host system (using apt-get). When I built from Ubuntu I think I had to install gcc, flex and bison. To sort out the error, read the output on the screen after you've run `make'. If it says `error' that's bad, you need to scroll back to the start of the error and look for clues (Google on the keywords)
Originally posted by Andrew Benton You need to install those things on your host system (using apt-get). When I built from Ubuntu I think I had to install gcc, flex and bison. To sort out the error, read the output on the screen after you've run `make'. If it says `error' that's bad, you need to scroll back to the start of the error and look for clues (Google on the keywords)
Thanks. I can install these packages on Host through Synaptic. I have a question regarding gcc version to be used. I had gcc 4 when I tried Binutils. In some post on this forum I have read that gcc 4 should not be used so I removed it. I also have gcc 3.3 and so I tried once again. This time the Binutils could not find gcc on the host (may be due to removal of gcc 4).
lfs@mybox:/mnt/lfs/sources/binutils-build$ ../binutils-220.127.116.11.2.2/configure --prefix=/tools --disable-nls
creating cache ./config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for gcc... no
checking for cc... no
configure: error: no acceptable cc found in $PATH
I would like to know how the packages being compiled find the path to the utilities on the host system and how to ensure this and what is "cc" and how to give its path.
Things like gcc should be in the $PATH of an ordinary user like the user lfs. If gcc-3.3 is available but you're getting an error saying Binutils could not find gcc it's possible you may need to make a symbloic link called gcc pointing at gcc-3.3
Originally posted by Andrew Benton Things like gcc should be in the $PATH of an ordinary user like the user lfs. If gcc-3.3 is available but you're getting an error saying Binutils could not find gcc it's possible you may need to make a symbloic link called gcc pointing at gcc-3.3
sudo ln -s gcc-3.3 /usr/bin/gcc
Thank you very much. I could proceed after installing flex, bison and provide the symbolic link to GCC as suggested by you. I have almost finished Chapter 5 (upto Util-linux) without any problem. I tested GCC pass 2 (it takes so much time) and the results were matching with LFS site. I will keep posting my progress in this thread and request you to see it for one or two days (I hope to finish LFS by this time).
Originally posted by kagashe Thank you very much. I could proceed after installing flex, bison and provide the symbolic link to GCC as suggested by you. I have almost finished Chapter 5 (upto Util-linux) without any problem. I tested GCC pass 2 (it takes so much time) and the results were matching with LFS site. I will keep posting my progress in this thread and request you to see it for one or two days (I hope to finish LFS by this time).
I completed Chapter 5 and initial steps in Chapter 6, installed Glibc, readjusted the toolchain, installed Binutils. When I completed makefile in GCC it was late night and since GCC testing was going to take a few hours I closed for the day and shutdown the computer.
Today I entered the Chroot environment after mounting proc and sys and issued make -k check command in GCCbuild file.
I found all tests failing. Then I deleted GCCbuild directory, made a new directory and makefile but again same result for make -k check command.
Then I started reading Chapter 6 once again and found that I should also mount tmpfs after entering Chroot environment. I did this and again issued make -k check command in GCCbuild directory. There are no errors now and gcc tests have begun. I hope there won't be any problem now and I can proceed with the remaining packages of Chapter 6.
I have one question at this stage. I find that testing in Chroot environment is slow compared to testing GCC in Chapter 5.
I have swap partition on host system. My question is:
Is the Linux system in Chroot environment using the swap on the host? If not how to enable it? Can two systems share one swap? (I hope so).
Today I have finished the installation of LFS. After adding the LFS entry in /boot/grub/menu.lst file in the host system I could boot the newly installed LFS system. I faced following problems during compiling the LFS system.
1. LFS book does not indicate clearly what is required on the host system (except the Kernel and GCC version used). After posting on this forum I came to know that BISON and FLEX are also required on the host system in addition to GCC (which I knew).
2. When you are building the packages in Chapter 6 after entering the Chroot environment you are required to shutdown the machine once or twice since the process takes so much time. The book says that if you reboot you have to mount proc and sysfs before entering the Chroot. This is OK. But before you restart the compilation you are also required to mount tmpfs and all associated nodes, and mount devpts etc.
Thanks for the heads up. I'm using ubuntu breezy preview and also found i needed to install flex and bison before starting. You're posts definitely helped. I also needed a gcc compiler, but when I installed the build-essential package with apt-get as was recommended, it gave me the 4.0 version, which did not work. I'm pretty much a noob, so it was a little messy getting rid of gcc-4.0, but I eventually found my problem was a broken symlink. To sum it up, if using ubuntu (and probably debian), make sure you do the following before starting the whole project:
apt-get install bison flex gcc-3.4
Things should work for you, but you may or may not have to put a symlink in /usr/bin pointing to gcc-3.4.