Blackfin and version scripts

Ralf Wildenhues Ralf.Wildenhues at
Sat Jun 26 21:32:41 CEST 2010

Hello Werner, all,

* Werner Koch wrote on Tue, Jun 22, 2010 at 11:42:43AM CEST:
> 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:
>     libgcrypt_version_script_cmd = -Wl,--version-script=$(srcdir)/libgcrypt.vers
>   else
>     libgcrypt_version_script_cmd = 
>   endif
>   [...]
>   libgcrypt_la_LDFLAGS = $(no_undefined) $(export_symbols) \
>   	$(libgcrypt_version_script_cmd) -version-info \
> $(no_undefined) $(export_symbols) are only used for W32 and not defined
> if we have version script support.

Why is -no-undefined not used unconditionally?  For C-only code, this
shouldn't be a problem (and if it is, we'd like to hear about it).


More information about the Gcrypt-devel mailing list