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] [lto] revision 144454 - Configure should check for elf support (similar to gmp/mpfr/PPL/CLooG)
Date: Thu, 26 Feb 2009 23:45:00 -0000	[thread overview]
Message-ID: <20090226234500.1224.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39316-13830@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from rob1weld at aol dot com  2009-02-26 23:44 -------
This Bug Report is about the failure to detect that the proper
headers and libraries are present _before_ building can be attempted.


Even after the extra effort to install libelf (to ensure that
the scripts would work) still results in the same error message:

# locate gelf.h
/usr/local/include/gelf.h
/usr/local/include/libelf/gelf.h
/usr/src/libelf-0.8.10/lib/gelf.h

but there is already a report made for _after_ installing libelf:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39019

Rob


-- 


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


  reply	other threads:[~2009-02-26 23:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 22:47 [Bug bootstrap/39316] New: " rob1weld at aol dot com
2009-02-26 23:45 ` rob1weld at aol dot com [this message]
2009-07-08  6:18 ` [Bug bootstrap/39316] " 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=20090226234500.1224.qmail@sourceware.org \
    --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).