--- Comment #5 from rguenth at gcc dot gnu dot org 2009-10-04 09:14 ---
I see. This particular issue should be fixed as libelf and the clone from
elfutils use different SONAMEs and the configure test in GCC checks for the
actual features it uses with a link test. The only thing that
--- Comment #6 from rob1weld at aol dot com 2009-10-04 10:25 ---
(In reply to comment #5)
I see. This particular issue should be fixed as libelf and the clone from
elfutils use different SONAMEs and the configure test in GCC checks for the
actual features it uses with a link test.
--- Comment #7 from rguenth at gcc dot gnu dot org 2009-10-04 10:32 ---
2009-09-14 Diego Novillo dnovi...@google.com
* configure.ac: Add link test to check for some of the
libelf functions used.
Tidy some formatting.
* configure: Regenerate.
--
--- Comment #3 from rguenth at gcc dot gnu dot org 2009-10-03 22:08 ---
I'm not 100% sure (I don't really understand this bug), but it should be fixed.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #4 from zadeck at naturalbridge dot com 2009-10-03 23:57
---
Richard,
the problem is that at least for the linux world there are two elf
implementations that while they claim to be compatible are distinctly different
on the inside. LTO, for better or worse, needs to use
--- Comment #2 from bje at gcc dot gnu dot org 2009-07-15 00:51 ---
*** Bug 39097 has been marked as a duplicate of this bug. ***
--
bje at gcc dot gnu dot org changed:
What|Removed |Added
--
bje at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |bje at gcc dot gnu dot org
|dot org
--- 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)
