Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Dear Friends, i'm compiling the binutils-2.17 in LFS (linux From Scratch), and when i enter the command "make", it goeas to infinite loop...
i know the make command is used for compilation,, but currently it takes 2:30 hours, which is the enough time... so please tell me, that is it the error or what is it,,,
Dear Friends, i'm compiling the binutils-2.17 in LFS (linux From Scratch), and when i enter the command "make", it goeas to infinite loop...
i know the make command is used for compilation,, but currently it takes 2:30 hours, which is the enough time... so please tell me, that is it the error or what is it,,,
The Steps i have performed to compile the binutils-2.17
Hi,
Dear tanushreevk i have performed the following steps...
1. first i have copy the binutils-2.17.tar.bz2 package to my source folder.
2. extract the files "tar xf binutils-2.17.tar.bz2"
3. cd binutils-2.17
4. make
after the above step # 4, the compilation starts, but its seems like a infinite loops, because it takes more the 2 Hrs...
Now please suggest any suitable solution for this issue...
creating Makefile
make: Warning: File `../binutils-2.17/Makefile.in' has modification time 2e+08 s in the future
CONFIG_SHELL="/bin/sh" /bin/sh ./config.status --recheck
running /bin/sh ../binutils-2.17/configure --prefix=/tools--disable-nls --disable-werror --no-create --no-recursion
loading 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... (cached) /usr/bin/install -c
checking whether ln works... (cached) yes
checking whether ln -s works... (cached) yes
checking for gcc... (cached) gcc -B/usr/bin/
checking whether the C compiler (gcc -B/usr/bin/ ) works... yes
checking whether the C compiler (gcc -B/usr/bin/ ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc -B/usr/bin/ accepts -g... (cached) yes
checking for gnatbind... no
checking whether compiler driver understands Ada... (cached) no
checking how to compare bootstrapped objects... (cached) cmp --ignore-initial=16 $$f1 $$f2
checking for correct version of gmp.h... no
checking for bison... (cached) bison -y
checking for bison... (cached) bison
checking for gm4... (cached) m4
checking for flex... (cached) flex
checking for flex... (cached) flex
checking for makeinfo... (cached) makeinfo
checking for expect... no
checking for runtest... no
checking for i686-pc-linux-gnu-ar... (cached) ar
checking for i686-pc-linux-gnu-as... (cached) as
checking for i686-pc-linux-gnu-dlltool... no
checking for dlltool... no
checking for i686-pc-linux-gnu-ld... (cached) /usr/bin/ld
checking for i686-pc-linux-gnu-lipo... no
checking for lipo... no
checking for i686-pc-linux-gnu-nm... (cached) nm
checking for i686-pc-linux-gnu-ranlib... (cached) ranlib
checking for i686-pc-linux-gnu-strip... (cached) strip
checking for i686-pc-linux-gnu-windres... no
checking for windres... no
checking for i686-pc-linux-gnu-objcopy... (cached) objcopy
checking for i686-pc-linux-gnu-objdump... (cached) objdump
checking for i686-pc-linux-gnu-gcj... no
checking for gcj... no
checking for i686-pc-linux-gnu-gfortran... no
checking for gfortran... no
checking for ar... no
checking for as... no
checking for dlltool... no
checking for i686-pc-linux-gnu-dlltool... no
checking for dlltool... no
checking for ld... no
checking for lipo... no
checking for i686-pc-linux-gnu-lipo... no
checking for lipo... no
checking for nm... no
checking for objdump... no
checking for ranlib... no
checking for strip... no
checking for windres... no
checking for i686-pc-linux-gnu-windres... no
checking for windres... no
checking where to find the target ar... just compiled
checking where to find the target as... just compiled
checking where to find the target cc... host tool
checking where to find the target c++... host tool
checking where to find the target c++ for libstdc++... host tool
checking where to find the target dlltool... just compiled
checking where to find the target gcc... host tool
checking where to find the target gcj... host tool
checking where to find the target gfortran... host tool
checking where to find the target ld... just compiled
checking where to find the target lipo... host tool
checking where to find the target nm... just compiled
checking where to find the target objdump... just compiled
checking where to find the target ranlib... just compiled
checking where to find the target strip... just compiled
checking where to find the target windres... just compiled
checking whether to enable maintainer-specific portions of Makefiles... no
creating ./config.status
CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating Makefile
make: Warning: File `../binutils-2.17/Makefile.in' has modification time 2e+08 s in the future
CONFIG_SHELL="/bin/sh" /bin/sh ./config.status --recheck
running /bin/sh ../binutils-2.17/configure --prefix=/tools--disable-nls --disable-werror --no-create --no-recursion
loading 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... (cached) /usr/bin/install -c
checking whether ln works... (cached) yes
checking whether ln -s works... (cached) yes
checking for gcc... (cached) gcc -B/usr/bin/
checking whether the C compiler (gcc -B/usr/bin/ ) works... yes
checking whether the C compiler (gcc -B/usr/bin/ ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc -B/usr/bin/ accepts -g... (cached) yes
checking for gnatbind... no
checking whether compiler driver understands Ada... (cached) no
checking how to compare bootstrapped objects... (cached) cmp --ignore-initial=16 $$f1 $$f2
checking for correct version of gmp.h... no
checking for bison... (cached) bison -y
checking for bison... (cached) bison
checking for gm4... (cached) m4
checking for flex... (cached) flex
checking for flex... (cached) flex
checking for makeinfo... (cached) makeinfo
checking for expect... no
checking for runtest... no
checking for i686-pc-linux-gnu-ar... (cached) ar
checking for i686-pc-linux-gnu-as... (cached) as
checking for i686-pc-linux-gnu-dlltool... no
checking for dlltool... no
checking for i686-pc-linux-gnu-ld... (cached) /usr/bin/ld
checking for i686-pc-linux-gnu-lipo... no
checking for lipo... no
checking for i686-pc-linux-gnu-nm... (cached) nm
checking for i686-pc-linux-gnu-ranlib... (cached) ranlib
checking for i686-pc-linux-gnu-strip... (cached) strip
checking for i686-pc-linux-gnu-windres... no
checking for windres... no
checking for i686-pc-linux-gnu-objcopy... (cached) objcopy
checking for i686-pc-linux-gnu-objdump... (cached) objdump
checking for i686-pc-linux-gnu-gcj... no
checking for gcj... no
checking for i686-pc-linux-gnu-gfortran... no
checking for gfortran... no
checking for ar... no
checking for as... no
checking for dlltool... no
checking for i686-pc-linux-gnu-dlltool... no
checking for dlltool... no
checking for ld... no
checking for lipo... no
checking for i686-pc-linux-gnu-lipo... no
checking for lipo... no
checking for nm... no
checking for objdump... no
checking for ranlib... no
checking for strip... no
checking for windres... no
checking for i686-pc-linux-gnu-windres... no
checking for windres... no
checking where to find the target ar... just compiled
checking where to find the target as... just compiled
checking where to find the target cc... host tool
checking where to find the target c++... host tool
checking where to find the target c++ for libstdc++... host tool
checking where to find the target dlltool... just compiled
checking where to find the target gcc... host tool
checking where to find the target gcj... host tool
checking where to find the target gfortran... host tool
checking where to find the target ld... just compiled
checking where to find the target lipo... host tool
checking where to find the target nm... just compiled
checking where to find the target objdump... just compiled
checking where to find the target ranlib... just compiled
checking where to find the target strip... just compiled
checking where to find the target windres... just compiled
checking whether to enable maintainer-specific portions of Makefiles... no
creating ./config.status
CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating Makefile
make: *** Deleting file `Makefile'
make: *** [Makefile] Error 1
make: Warning: File `../binutils-2.17/Makefile.in' has modification time 2e+08 s in the future
This is the problem which triggers the "infinite loop". Look at the timestamp of the installation files if one or more (or all) of them are in the future you can touch them and try to compile again. Unless it is a problem with your system clock: does it display the correct time and date?
you are ri8 that this is the CMOS bettery problem, and i have the same problem, and i have changed my CMOS bettery and now i have successfuly compiled the kernel.
and Congrats to me that i have successfuly created my own Linux from scratch. and i have names it LMLinux.
so i suggest you to change ur CMOS bettery, because time stamp this compiling have the great role. so,
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.