Mike Frysinger writes:
> 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
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 i
Ralf Wildenhues writes:
> * 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
Hello Russ, all,
* 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
Werner Koch writes:
> (4) Let libtool do something. This may be an option to detect
> -Wl,--version-script=foo on the command line and hook in a sed to
> transform the symbols. It is pretty common that symols are all prefixed
> with something like "foo_" or "_foo_" and thus the option could tak
Hi!
Mike and Robin found a build problem with libgcrypt on Blackfin using
the GNU toolchain: Libgcrypt as most other GnuPG related libraries tries
to keep a well defined ABI and thus use a version script to guarantee
that. The version script is passed to libtool this way:
if HAVE_LD_VERSION_SC
