[lfs-support] Problem on compiling and installing Binutils-2.21.1a

Uthayanan suthayanan at gmail.com
Tue Jan 10 06:28:35 PST 2012


Thank You all for the support . :)

On Tue, Jan 10, 2012 at 6:19 PM, Eleanore Boyd <cara117 at cox.net> wrote:

>  On 1/10/2012 5:27 AM, Uthayanan wrote:
>
> This time I got loads of "no " . I think I should slow little bit down and
> do the whole process again..
>
>
> lfsuthayan at ubuntu:~$ cd /mnt/lfs/Sources/binutils-2.21.1
> lfsuthayan at ubuntu:/mnt/lfs/Sources/binutils-2.21.1$../binutils-2.21.1/configure \
> >     --target=$LFS_TGT --prefix=/tools \
> >     --disable-nls --disable-werror
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
>  checking target system type... i686-lfs-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 a sed that does not truncate output... /bin/sed
> checking for gawk... no
> checking for mawk... mawk
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
>  checking whether g++ accepts -g... yes
> checking for gnatbind... no
> checking for gnatmake... no
> checking whether compiler driver understands Ada... no
> checking how to compare bootstrapped objects... cmp --ignore-initial=16
> $$f1 $$f2
> checking for objdir... .libs
> checking for version 0.10 (or later revision) of PPL... no
> checking for default BUILD_CONFIG...
> checking for bison... no
> checking for byacc... no
> checking for yacc... no
> checking for bison... no
> checking for gm4... no
> checking for gnum4... no
> checking for m4... no
> checking for flex... no
> checking for lex... no
> checking for flex... no
> checking for makeinfo... no
> checking for expect... no
> checking for runtest... no
> checking for ar... ar
> checking for as... as
> checking for dlltool... no
> checking for ld... ld
> checking for lipo... no
> checking for nm... nm
> checking for ranlib... ranlib
> checking for strip... strip
> checking for windres... no
> checking for windmc... no
> checking for objcopy... objcopy
> checking for objdump... objdump
> checking for i686-lfs-linux-gnu-cc... no
> checking for i686-lfs-linux-gnu-gcc... no
> checking for i686-lfs-linux-gnu-c++... no
> checking for i686-lfs-linux-gnu-g++... no
> checking for i686-lfs-linux-gnu-cxx... no
> checking for i686-lfs-linux-gnu-gxx... no
> checking for i686-lfs-linux-gnu-gcc... no
> checking for i686-lfs-linux-gnu-gcj... no
> checking for i686-lfs-linux-gnu-gfortran... no
> checking for i686-lfs-linux-gnu-ar... i686-lfs-linux-gnu-ar
> checking for i686-lfs-linux-gnu-as... i686-lfs-linux-gnu-as
> checking for i686-lfs-linux-gnu-dlltool... no
> checking for i686-lfs-linux-gnu-ld... i686-lfs-linux-gnu-ld
> checking for i686-lfs-linux-gnu-lipo... no
> checking for i686-lfs-linux-gnu-nm... i686-lfs-linux-gnu-nm
> checking for i686-lfs-linux-gnu-objdump... i686-lfs-linux-gnu-objdump
> checking for i686-lfs-linux-gnu-ranlib... i686-lfs-linux-gnu-ranlib
> checking for i686-lfs-linux-gnu-strip... i686-lfs-linux-gnu-strip
> checking for i686-lfs-linux-gnu-windres... no
> checking for i686-lfs-linux-gnu-windmc... 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... pre-installed
> checking where to find the target c++... pre-installed
> checking where to find the target c++ for libstdc++... pre-installed
> checking where to find the target dlltool... just compiled
> checking where to find the target gcc... pre-installed
> checking where to find the target gcj... pre-installed
> checking where to find the target gfortran... pre-installed
> checking where to find the target ld... just compiled
> checking where to find the target lipo... pre-installed
> 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 where to find the target windmc... just compiled
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking whether -fkeep-inline-functions is supported... yes
> configure: creating ./config.status
> config.status: creating Makefile
> lfsuthayan at ubuntu:/mnt/lfs/Sources/binutils-2.21.1$
>
>  On Tue, Jan 10, 2012 at 4:31 PM, Firerat <firer4t at googlemail.com> wrote:
>
>> Let's have a small time out and think about this....
>>
>> make failed as it found no Makefile, this is created by configure.
>>
>> Binutils is a little 'odd' in you build it outside of the source dir
>>
>> in sources you should have the tarball, binutils-x.y.z/ and binutils-build
>>
>> I suspect you have untared binutils, then created ../binutils-build
>> Easy mistake to make....
>>
>> The book assumes you are in the packages source dir
>> Untar binutils, cd into the created dir and then follow the book
>>  On Jan 10, 2012 10:45 AM, "Uthayanan" <suthayanan at gmail.com> wrote:
>>
>>> Hi Firerat,
>>>
>>>  lfsuthayan at ubuntu:/$ make -j1
>>> make: *** No targets specified and no makefile found.  Stop.
>>>
>>>  I also tried in following way
>>>
>>>  lfsuthayan at ubuntu:/$ export MAKEFLAGS='-j 1'
>>> lfsuthayan at ubuntu:/$ make -j1
>>> make: *** No targets specified and no makefile found.  Stop.
>>>
>>>  But earlier, Since My laptop is core to duo i set it to two and i
>>> didnt get any sort of error.
>>>
>>> On Tue, Jan 10, 2012 at 4:07 PM, Firerat <firer4t at googlemail.com> wrote:
>>>
>>>>
>>>> On Jan 10, 2012 10:22 AM, "Uthayanan" <suthayanan at gmail.com> wrote:
>>>> >
>>>> > Hi Firerat
>>>> >
>>>> > Book says the required disk space should be 350 MB. But my
>>>> binutils-build is only 508K
>>>> >
>>>> > lfsuthayan at ubuntu:/mnt/lfs/Sources$ ls -lh binutils-build/
>>>> > total 508K
>>>> >
>>>> > that means , I am missing something no .... btw I used ubuntu to
>>>> create my lfs partition.. is there any thing to do with that ?
>>>> >
>>>> > On Tue, Jan 10, 2012 at 3:45 PM, Firerat <firer4t at googlemail.com>
>>>> wrote:
>>>> >>
>>>> >>
>>>> >> On Jan 10, 2012 9:48 AM, "Uthayanan" <suthayanan at gmail.com> wrote:
>>>> >> >
>>>> >> > Hi Sandip,
>>>> >> >
>>>> >> > I followed the book.. During the compilation i didnt get any
>>>> errors.. Then during the installation I got the above warning and system
>>>> >> > got out of the installation mode soon after the errors.
>>>> >> > Do we have different options in compilation ?
>>>> >> >
>>>> >> > On Tue, Jan 10, 2012 at 3:13 PM, sandip sitapara <
>>>> s13884neo at gmail.com> wrote:
>>>> >> >>
>>>> >> >> There is no error. Just messages that there is nothing to be
>>>> installed. I am not sure but testsuit shouldn't be install in system it is
>>>> just to check the correct installation and dependencies to run that
>>>> software correctly.Also you have to look the compilation options while
>>>> building the same.
>>>> >> >>
>>>> >> >> On Tue, Jan 10, 2012 at 3:05 PM, Uthayanan <suthayanan at gmail.com>
>>>> wrote:
>>>> >> >>>
>>>> >> >>> Hi Group,
>>>> >> >>>
>>>> >> >>> I get following error when I try to install the binutils. I am
>>>> new to lfs and may be this one may be a silly question to ask:) . Please
>>>> help me on this
>>>> >> >>>
>>>> >> >>> make[3]: Entering directory
>>>> `/mnt/lfs/Sources/binutils-build/libiberty/testsuite'
>>>> >> >>> make[3]: Nothing to be done for `install'.
>>>> >> >>> make[3]: Leaving directory
>>>> `/mnt/lfs/Sources/binutils-build/libiberty/testsuite'
>>>> >> >>> make[2]: Leaving directory
>>>> `/mnt/lfs/Sources/binutils-build/libiberty'
>>>> >> >>> make[1]: Nothing to be done for `install-target'.
>>>> >> >>> make[1]: Leaving directory `/mnt/lfs/Sources/binutils-build'
>>>> >> >>> lfsuthayan at ubuntu:/mnt/lfs/Sources/binutils-build$
>>>> >> >>> lfsuthayan at ubuntu:/mnt/lfs/Sources/binutils-build$
>>>> >> >>>
>>>> >> >>>
>>>> >> >>>
>>>> >> >>> Thanks
>>>> >> >>>
>>>> >> >>>
>>>> >> >>> --
>>>> >> >>> Regards,
>>>> >> >>> s uthay
>>>> >> >>>
>>>> >> >>> --
>>>> >> >>> http://linuxfromscratch.org/mailman/listinfo/lfs-support
>>>> >> >>> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
>>>> >> >>> Unsubscribe: See the above information page
>>>> >> >>>
>>>> >> >>
>>>> >> >>
>>>> >> >> --
>>>> >> >> http://linuxfromscratch.org/mailman/listinfo/lfs-support
>>>> >> >> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
>>>> >> >> Unsubscribe: See the above information page
>>>> >> >>
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > Regards,
>>>> >> > s uthay
>>>> >> >
>>>> >> > --
>>>> >> >
>>>> >> >
>>>> >>
>>>> >> The make install simply runs make install in each directory, the
>>>> testsuite doesn't have a install target...it is just stating it That is
>>>> perfectly normal
>>>> >>
>>>> >> Warnings can usually be ignored, unless you are working with the
>>>> code and want to resolve them
>>>> >>
>>>> >> Regards 'options in compilation'
>>>> >> for the moment follow the book exactly  *do not* deviate from the
>>>> book, you will only get lost.
>>>> >>
>>>> >> When you come across something that reads
>>>> >> <EDITME<xxx>EDITME>
>>>> >> or the like, then you need to modify for your needs, e.g. timezone
>>>> in glibc, papersize in groff, but CEOs those bridges when you get to them :)
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> http://linuxfromscratch.org/mailman/listinfo/lfs-support
>>>> >> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
>>>> >> Unsubscribe: See the above information page
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Regards,
>>>> > s uthay
>>>> >
>>>>
>>>> Ok, well the copy'n'paste you did doesn't detail any errors
>>>>
>>>> Do
>>>>     make -j1
>>>>
>>>> Why -j1 ?
>>>> If you set MAKEFLAGS="-j<n>" to take advantage of multiple cores the
>>>> error can be hidden higher up in the compiler spew,,, -j1 will make it
>>>> easier to read
>>>>
>>>> As binutils is the first package it may well be worth going back and
>>>> starting again, it will be something simple, probably a missing package on
>>>> your host system
>>>>
>>>> --
>>>> http://linuxfromscratch.org/mailman/listinfo/lfs-support
>>>> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
>>>> Unsubscribe: See the above information page
>>>>
>>>>
>>>
>>>
>>>  --
>>> Regards,
>>> s uthay
>>>
>>> --
>>> http://linuxfromscratch.org/mailman/listinfo/lfs-support
>>> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
>>> Unsubscribe: See the above information page
>>>
>>>
>> --
>> http://linuxfromscratch.org/mailman/listinfo/lfs-support
>> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
>> Unsubscribe: See the above information page
>>
>>
>
>
>  --
> Regards,
> s uthay
>
>
>  There's nothing wrong with your new output. I believe you are simply very
> green in the ways of Linux and compiling. (Also, don't send a list an
> invitation to an email service. First, kinda pointless, and second, it can
> be rude, especially when some of us already have another email account with
> that service.)
>
> Elly
>
> --
> http://linuxfromscratch.org/mailman/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information page
>
>


-- 
Regards,
s uthay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfromscratch.org/pipermail/lfs-support/attachments/20120110/cdd230de/attachment.html>


More information about the lfs-support mailing list