public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/39316]  New: [lto] revision 144454 - Configure should check for elf support (similar to gmp/mpfr/PPL/CLooG)
Date: Thu, 26 Feb 2009 22:47:00 -0000	[thread overview]
Message-ID: <bug-39316-13830@http.gcc.gnu.org/bugzilla/> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4409 bytes --]

It is my Request for Enhancement that the 'Configury' detect if
there is enough elf support to build gcc - in a similar manner that
gmp, mpfr, PPL and CLooG are tested for.

The configury is waiting until it gets past configuring the gcc directory,
and even detecting that gelf.h is not present, before the build fails. 

This Operating System (Debian GNU/Linux) does have "/usr/include/elf.h"
in a default installation but is 'lacking enough elf' to build without
failing. This should be checked in ../lto_trunk/configure .



# make
...
Configuring stage 1 in ./gcc
configure: creating cache ./config.cache
checking build system type... x86_64-unknown-linux-gnu
...
checking for pthread.h... yes
checking for libelf.h... no
checking for libelf/libelf.h... no
checking for gelf.h... no
checking for libelf/gelf.h... no
checking for CHAR_BIT... yes
...


make[3]: Entering directory `/usr/src/lto_build/lto-plugin'
if /bin/sh ./libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"LTO\ plugin\
for\ ld\" -DPACKAGE_TARNAME=\"lto-plugin\" -DPACKAGE_VERSION=\"0.1\"
-DPACKAGE_STRING=\"LTO\ plugin\ for\ ld\ 0.1\" -DPACKAGE_BUGREPORT=\"\"
-DPACKAGE=\"lto-plugin\" -DVERSION=\"0.1\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I.
-I../../lto_trunk/lto-plugin  -I../../lto_trunk/lto-plugin/../include
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -Wall -Werror -g
-fkeep-inline-functions -MT lto-plugin.lo -MD -MP -MF ".deps/lto-plugin.Tpo" -c
-o lto-plugin.lo ../../lto_trunk/lto-plugin/lto-plugin.c; \
        then mv -f ".deps/lto-plugin.Tpo" ".deps/lto-plugin.Plo"; else rm -f
".deps/lto-plugin.Tpo"; exit 1; fi
libtool: compile:  gcc "-DPACKAGE_NAME=\"LTO plugin for ld\""
-DPACKAGE_TARNAME=\"lto-plugin\" -DPACKAGE_VERSION=\"0.1\"
"-DPACKAGE_STRING=\"LTO plugin for ld 0.1\"" -DPACKAGE_BUGREPORT=\"\"
-DPACKAGE=\"lto-plugin\" -DVERSION=\"0.1\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I.
-I../../lto_trunk/lto-plugin -I../../lto_trunk/lto-plugin/../include
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -Werror -g
-fkeep-inline-functions -MT lto-plugin.lo -MD -MP -MF .deps/lto-plugin.Tpo -c
../../lto_trunk/lto-plugin/lto-plugin.c  -fPIC -DPIC -o .libs/lto-plugin.o
../../lto_trunk/lto-plugin/lto-plugin.c:56:4: error: #error "gelf.h not
available"
../../lto_trunk/lto-plugin/lto-plugin.c:170: error: expected ‘=’, ‘,’, ‘;’,
‘asm’ or ‘__attribute__’ before ‘*’ token
...
../../lto_trunk/lto-plugin/lto-plugin.c:619: error: ‘EV_NONE’ undeclared (first
use in this function)
make[3]: *** [lto-plugin.lo] Error 1
make[3]: Leaving directory `/usr/src/lto_build/lto-plugin'
make[2]: *** [all-stage1-lto-plugin] Error 2
make[2]: Leaving directory `/usr/src/lto_build'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/usr/src/lto_build'
make: *** [all] Error 2

# ls -l /usr/include/elf.h 
-rw-r--r-- 1 root root 110896 2009-01-04 10:10 /usr/include/elf.h

# ls -l /usr/include/gelf.h 
ls: cannot access /usr/include/gelf.h: No such file or directory

# locate gelf.h
(Nothing printed)

# locate elf.h
/usr/include/elf.h
/usr/include/linux/elf.h
/usr/include/sys/elf.h


# gcc/xgcc -v
Using built-in specs.
COLLECT_GCC=gcc/xgcc
Target: x86_64-unknown-linux-gnu
Configured with: ../lto_trunk/configure --prefix=/usr/local/lto
--enable-languages=lto,c++ --enable-stage1-checking=all
--enable-checking=release
Thread model: posix
gcc version 4.4.0 20090218 (experimental) [lto revision 144454] (lto merged
with rev 144262)


-- 
           Summary: [lto] revision 144454 - Configure should check for elf
                    support (similar to gmp/mpfr/PPL/CLooG)
           Product: gcc
           Version: lto
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rob1weld at aol dot com
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39316


             reply	other threads:[~2009-02-26 22:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 22:47 rob1weld at aol dot com [this message]
2009-02-26 23:45 ` [Bug bootstrap/39316] " rob1weld at aol dot com
2009-07-08  6:18 ` bje at gcc dot gnu dot org
2009-07-15  0:52 ` bje at gcc dot gnu dot org
2009-10-03 22:08 ` rguenth at gcc dot gnu dot org
2009-10-03 23:57 ` zadeck at naturalbridge dot com
2009-10-04  9:15 ` rguenth at gcc dot gnu dot org
2009-10-04 10:25 ` rob1weld at aol dot com
2009-10-04 10:32 ` rguenth at gcc dot gnu dot org

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=bug-39316-13830@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).