[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Blackfin and version scripts

From: Mike Frysinger
Subject: Re: Blackfin and version scripts
Date: Wed, 23 Jun 2010 01:36:34 -0400
User-agent: KMail/1.13.1 (Linux/2.6.34; KDE/4.4.3; x86_64; ; )

On Wednesday, June 23, 2010 01:08:31 Ralf Wildenhues wrote:
> * Russ Allbery wrote on Tue, Jun 22, 2010 at 11:00:04PM CEST:
> > I would dearly, dearly love for libtool to pick up a --version-script
> > option that would pass in the full version script on platforms with
> > linkers that understand it, turn it into a symbol export list on
> > platforms that only support that,
> is this doable programmatically?  Without a full version script parser?

i guess it depends on how much you want to support.  the full syntax is here:

the non-C language support makes me think it'd require a lot of work to be 
100% complete, but ive personally never seen people use that in version 
scripts before (and ive quite a bit in the open source world).  so if we kept 
the scope to C-only symbols ...

the linker is pretty unforgiving of improperly formatted files (which works 
for us).  since we only need to mung the symbol nodes, and those:
 - cannot have spaces
 - must be terminated by a semicolon
 - appear between the braces

seems like it wouldnt be too bad ?

alternative might be to do something like -export-symbols where libtool has 
its own method for managing lists of symbols, but extend it to handle 
versioning information as available with GNU/Solaris linkers.  then that would 
take care of outputting the version script with the symbol prefix which 
libtool already knows.

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]