--- Additional Comments From ian at airs dot com 2009-10-13 00:54 ---
As far as I am concerned, gold has been released. The question now is what
changes distros will want to see before picking it up as the default linker for
those targets which it supports.
--
http://sourceware.org/b
--- Additional Comments From apratt at us dot ibm dot com 2009-10-13 00:27
---
It's the second one, with a variation. I wouldn't expect your second example to
link successfully as written. If you change it so main() calls both a() and b(),
it will link with today's GNU linker. That's bec
--- Additional Comments From fche at redhat dot com 2009-10-12 23:53
---
I'm confused about whether gold's lack of DT_NEEDED resolution is
intended to affect only pure-indirect or merely mixed-direct-indirect
dependencies. Specifically:
liba { int a() { return b(); } }
libb { int b() {
--- Additional Comments From amodra at bigpond dot net dot au 2009-10-12
23:25 ---
Fixed
--
What|Removed |Added
Status|NEW |RESOLVED
--- Additional Comments From hjl dot tools at gmail dot com 2009-10-12
23:18 ---
Created an attachment (id=4275)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=4275&action=view)
A patch
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10740
--- You are receiving this m
--
What|Removed |Added
Severity|critical|normal
http://sourceware.org/bugzilla/show_bug.cgi?id=10735
--- You are receiving this mail because:
--- Additional Comments From ian at airs dot com 2009-10-12 22:35 ---
Comment #7 does not necessarily indicate that there are a lot of packages which
provide a union-of-defined-symbols interface. What is indicates is that a lot
of people think that linking against the KDE or GNOME librar
--- Additional Comments From apratt at us dot ibm dot com 2009-10-12 22:25
---
Pretty common, based on the link in comment #7. The vast majority of those
failures are due to unresolved symbols, and it's possible many (most? virtually
all?) of them are due to programs expecting the old be
--- Additional Comments From ian at airs dot com 2009-10-12 20:15 ---
Carrying on, it's true that gold's behaviour does impose a burden when using
shared libraries which come in bundles. If a package provides a shared library
which includes other shared libraries, and the interface of th
--- Additional Comments From ian at airs dot com 2009-10-12 20:02 ---
To be clear, gold does not require that you enumerate all indirect dependencies
of shared libraries. gold will not complain if a shared library refers to a
function defined in some dependency of that shared library.
W
--- Additional Comments From fche at redhat dot com 2009-10-12 16:10
---
IMO, ld's automagic searching is a good thing. Asking a program to enumerate
all the indirect dependencies of shared libraries is a burden that they may not
be equipped to carry. How do you envision this be automa
--
What|Removed |Added
CC||fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10238
--- You are receiving this ma
--- Additional Comments From amodra at bigpond dot net dot au 2009-10-12
13:21 ---
Unfortunately the patch isn't correct. We might map a unique section to an
output section that later has some other section or data mapped.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10749
---
13 matches
Mail list logo
