From: Diego Novillo <dnovillo@google.com>
To: Sandeep Soni <soni.sandeepb@gmail.com>
Cc: mike <mikereape@onetel.com>, gcc <gcc@gcc.gnu.org>
Subject: Re: Build Error
Date: Tue, 11 May 2010 13:00:00 -0000 [thread overview]
Message-ID: <AANLkTikVDE7bNUGzy6JOMyF_Q2KjwGTOe6p-iOZ0Egm-@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilNW9hv8_oWW4VTj4YWum2IqJoGM3VB1uCRFn1Z@mail.gmail.com>
[ Moved to gcc@gcc.gnu.org ]
On Tue, May 11, 2010 at 08:46, Sandeep Soni <soni.sandeepb@gmail.com> wrote:
> On Tue, May 11, 2010 at 4:53 PM, Diego Novillo <dnovillo@google.com> wrote:
>> On Tue, May 11, 2010 at 02:24, Sandeep Soni <soni.sandeepb@gmail.com> wrote:
>>
>>> I installed elfutils-libelf-devel-0.145-1 and that worked.
>>
>> Yes. Older libelfs will not work. However, you should've gotten a
>> configuration-time error. If you can reproduce, could you file a bug?
>> The checking done during configuration did not spot the old version
>> of libelf.
>>
>
> Here was the configuration output:
>
> [root@Sandy build]# ../trunk/configure
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking target 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 a sed that does not truncate output... /bin/sed
> checking for gawk... gawk
> 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 the correct version of gmp.h... yes
> checking for the correct version of mpfr.h... yes
> checking for the correct version of mpc.h... yes
> checking for the correct version of the gmp/mpfr/mpc libraries... yes
> checking for version 0.10 (or later revision) of PPL... no
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking libelf.h usability... yes
> checking libelf.h presence... yes
> checking for libelf.h... yes
> checking gelf.h usability... yes
> checking gelf.h presence... yes
> checking for gelf.h... yes
> checking libelf/libelf.h usability... yes
> checking libelf/libelf.h presence... yes
> checking for libelf/libelf.h... yes
> checking libelf/gelf.h usability... yes
> checking libelf/gelf.h presence... yes
> checking for libelf/gelf.h... yes
> checking for the correct version of libelf... yes
> checking for elf_getshdrstrndx... no
> checking for elf_getshstrndx... yes
> The following languages will be built: c,c++,fortran,java,lto,objc
> *** This configuration is not supported in the following subdirectories:
> target-libada gnattools
> (Any other directories should still work fine.)
> checking for default BUILD_CONFIG... bootstrap-debug
> *** removing build-i686-pc-linux-gnu/libiberty/Makefile to force reconfigure
> *** removing build-i686-pc-linux-gnu/fixincludes/Makefile to force reconfigure
> *** removing prev-intl/Makefile to force reconfigure
> *** removing intl/Makefile to force reconfigure
> *** removing prev-libiberty/Makefile to force reconfigure
> *** removing libiberty/Makefile to force reconfigure
> *** removing prev-zlib/Makefile to force reconfigure
> *** removing zlib/Makefile to force reconfigure
> *** removing prev-libcpp/Makefile to force reconfigure
> *** removing libcpp/Makefile to force reconfigure
> *** removing prev-libdecnumber/Makefile to force reconfigure
> *** removing libdecnumber/Makefile to force reconfigure
> *** removing prev-gcc/Makefile to force reconfigure
> *** removing gcc/Makefile to force reconfigure
> checking for bison... bison -y
> checking for bison... bison
> checking for gm4... no
> checking for gnum4... no
> checking for m4... m4
> checking for flex... flex
> checking for flex... flex
> checking for makeinfo... makeinfo
> 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 cc... cc
> checking for c++... c++
> checking for gcc... gcc
> checking for gcj... no
> checking for gfortran... gfortran
> checking for ar... no
> checking for ar... ar
> checking for as... no
> checking for as... as
> checking for dlltool... no
> checking for dlltool... no
> checking for ld... no
> checking for ld... ld
> checking for lipo... no
> checking for lipo... no
> checking for nm... no
> checking for nm... nm
> checking for objdump... no
> checking for objdump... objdump
> checking for ranlib... no
> checking for ranlib... ranlib
> checking for strip... no
> checking for strip... strip
> checking for windres... no
> checking for windres... no
> checking for windmc... no
> checking for windmc... no
> checking where to find the target ar... host tool
> checking where to find the target as... host tool
> checking where to find the target cc... just compiled
> checking where to find the target c++... just compiled
> checking where to find the target c++ for libstdc++... just compiled
> checking where to find the target dlltool... host tool
> checking where to find the target gcc... just compiled
> checking where to find the target gcj... just compiled
> checking where to find the target gfortran... just compiled
> checking where to find the target ld... host tool
> checking where to find the target lipo... host tool
> checking where to find the target nm... host tool
> checking where to find the target objdump... host tool
> checking where to find the target ranlib... host tool
> checking where to find the target strip... host tool
> checking where to find the target windres... host tool
> checking where to find the target windmc... host tool
> 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
>
>
> There were these lines :
> checking for the correct version of libelf... yes
> checking for elf_getshdrstrndx... no
> checking for elf_getshstrndx... yes
>
> I think this is fine.Right?
Hmm, it did not detect elf_getshdrstrndx and yet it tried to use it
later on. I think that's the bug. Yes, please file a bug. I believe
it's going to be easy to fix, though. There should be an unguarded
use of that function somewhere, it needs to be changed.
>
> If not, should I file a bug?
>
>>> However, now I face a different error that says:
>>>
>>> make[2]: Entering directory `/home/Sandy/Development/build'
>>> make[3]: Entering directory `/home/Sandy/Development/build'
>>> rm -f stage_current
>>> make[3]: Leaving directory `/home/Sandy/Development/build'
>>> Comparing stages 2 and 3
>>> warning: gcc/cc1-checksum.o differs
>>> warning: gcc/cc1obj-checksum.o differs
>>> warning: gcc/cc1plus-checksum.o differs
>>> Bootstrap comparison failure!
>>> gcc/gcc.o differs
>>> gcc/plugin.o differs
>>> make[2]: *** [compare] Error 1
>>> make[2]: Leaving directory `/home/Sandy/Development/build'
>>> make[1]: *** [stage3-bubble] Error 2
>>> make[1]: Leaving directory `/home/Sandy/Development/build'
>>> make: *** [all] Error 2
>>
>> Did you start the build from scratch after installing the new libelf?
>>
>
> Yes.I mean, did make clean and started from configure step again.
>
> ../trunk/configure
> make
>
> Should I delete the previous build directory altogether and then start
> the build again?
Yes, try from whole cloth.
Diego.
next parent reply other threads:[~2010-05-11 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <l2x38f1d9be1005100303s856c766ek1a873b940dffc0b0@mail.gmail.com>
[not found] ` <s2g38f1d9be1005100315m4447178en17af5c1b4b5e5318@mail.gmail.com>
[not found] ` <4BE7E328.70003@onetel.com>
[not found] ` <AANLkTikMn1UDfL_F5h6LChkSyQvvEH2bdyRK6acR2LCj@mail.gmail.com>
[not found] ` <AANLkTikEgxs7sGkQrdjZ46dUSiKAYaP490PznurOFMzo@mail.gmail.com>
[not found] ` <AANLkTilNW9hv8_oWW4VTj4YWum2IqJoGM3VB1uCRFn1Z@mail.gmail.com>
2010-05-11 13:00 ` Diego Novillo [this message]
2010-05-11 14:25 ` Sandeep Soni
2010-05-12 11:56 ` mike
2007-02-23 14:09 build Error sameer sinha
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 13:38 build error bob_rossi
2006-10-17 14:45 bob_rossi
2006-10-17 22:27 ` Brian Dessent
2003-01-03 17:37 Build error Pedro Manuel Augusto
2003-01-03 18:24 ` Jeff Sturm
2003-01-07 11:36 ` Pedro Manuel Augusto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikVDE7bNUGzy6JOMyF_Q2KjwGTOe6p-iOZ0Egm-@mail.gmail.com \
--to=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=mikereape@onetel.com \
--cc=soni.sandeepb@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).