Mailing-List: contact dev-help@lucy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucy.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAAS6=7jNC2HL4-sO_3ZOxzhCNdzOAa+LcD4aEqbj6VQxiCBeWg@mail.gmail.com>
References: <4F903955.5020608@aevum.de>
 <CAAS6=7hMpzOg8xdC3=1gv5tGGyA=pcUSdXeO2sijG+heQr9AJw@mail.gmail.com>
 <4F913440.10100@aevum.de>
 <CAAS6=7gGQAyNsC+T-63zdfAzGCAc4BK8KOj4eZ_-JPdnqFTwbg@mail.gmail.com>
 <4F941F97.4090504@aevum.de>
 <CAAS6=7gx3aAaVxgFdf2w5EJOXMikOVN1ymLfkfR_T37GAjGz2Q@mail.gmail.com>
 <4F95385B.7070701@aevum.de>
 <CAAS6=7jNC2HL4-sO_3ZOxzhCNdzOAa+LcD4aEqbj6VQxiCBeWg@mail.gmail.com>
From: Nathan Kurz <nate@verse.com>
Date: Mon, 23 Apr 2012 12:49:34 -0700
Message-ID: 
 <CAFAN8vw1HFzBVt03b0LgoUM6q7zfkXaS8WR1hvZboxh7+bSMFw@mail.gmail.com>
To: dev@lucy.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [lucy-dev] OFFSET globals

On Mon, Apr 23, 2012 at 7:55 AM, Marvin Humphrey <marvin@rectangular.com> w=
rote:
> My understanding is that in the event that two ELF DSOs export the same
> symbol, the general rule is that the last library loaded wins[1]:

I'm pretty sure that at runtime it's the first definition found that
wins, which is why LD_PRELOAD can be used to override functions like
malloc().

> =C2=A0 =C2=A0http://www.akkadia.org/drepper/dsohowto.pdf

"Note that there is no problem if the scope contains more than one
definition of the same symbol. The symbol lookup algorithm simply
picks up the first definition it finds." p.6, 1.5.2

> [1] "How to Write Shared Libraries" by Ulrich Drepper, section 1.4.5.

Thought maybe you were referencing a different version of the paper,
then figured out that you meant "1.5.4" (transposition).

---

I've been planning to chime in on this, but haven't had time to do it
justice.  My quick thoughts are that:

1) This can and should be solved through DSO symbol versioning.
2) It's great to get things right so as to have a solid foundation, but
3) We got along just fine for years without actually implementing this, thu=
s
4) We don't need to solve this right now, just future-proof ourselves.

I'm rusty and busy, though, and might not be of immediate help.  In
addition to Ulrich's paper, Ian's series here might be a good
refresher: http://www.airs.com/blog/page/4?s=3D%22linkers+part%22

I haven't found a good overview of the links, but versioning is covered in
Part 9: Symbol Versions http://www.airs.com/blog/archives/46
Part 13: Symbol Versions Redux http://www.airs.com/blog/archives/50

--nate