Hi Niels, Tracking which internal symbols exist on different architectures to avoid errors and warnings when generating the symbols files for Debian is a major PITA, but I should probably give up on that and simply tag them all "optional". But have you considered hiding them? https://developer.apple.com/ library/archive/documentation/DeveloperTools/Conceptual/DynamicLibraries/100- Articles/DynamicLibraryDesignGuidelines.html, https://gcc.gnu.org/onlinedocs/ gcc/Common-Function-Attributes.html#Common-Function-Attributes, and gcc(1) have some information on this.
What you do is to attach
__attribute__((visibility("default")))
to the symbols to be exported (you can of course #define a macro, say EXPORT,
with this), then compile with -fvisibility=hidden in CFLAGS.
This should be cross-platform, it sounds like, but I'm not 100% sure.
--
Magnus Holmgren holmg...@debian.org
Debian Developer
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ nettle-bugs mailing list -- nettle-bugs@lists.lysator.liu.se To unsubscribe send an email to nettle-bugs-le...@lists.lysator.liu.se
