G. Branden Robinson wrote:
> $ find ~/_Inline/ -type f
> /home/branden/_Inline/config-x86_64-linux-gnu-thread-multi-5.032001
> /home/branden/_Inline/lib/auto/gropdf_1c9b/gropdf_1c9b.inl
> /home/branden/_Inline/lib/auto/gropdf_1c9b/gropdf_1c9b.so
> /home/branden/_Inline/.lock
>
> > Also, if different versions of groff produce shared libraries with
> > different APIs, you will need to include the groff version in the file
> > name, because the user may be running different groff versions at
> > different times (or even at the same time).
>
> This much is not the case. Apart from gnulib, with which many people
> are familiar (and which supports no DSO configuration TTBOMK), the groff
> build produces up to four libraries--libgroff, libdriver, libbib, and
> libxutil--but all are static (".a" files).
No, I'm talking about the ABI of the .so file:
$ file _Inline/lib/auto/gropdf_1c9b/gropdf_1c9b.so
_Inline/lib/auto/gropdf_1c9b/gropdf_1c9b.so: ELF 64-bit LSB shared object,
x86-64, version 1 (SYSV), dynamically linked,
BuildID[sha1]=15e061d07b4a8a9185ae3111c567c324f589752d, with debug_info, not
stripped
$ nm -D _Inline/lib/auto/gropdf_1c9b/gropdf_1c9b.so
0000000000001450 T boot_gropdf_1c9b
w __cxa_finalize
0000000000001260 T decrypt_exec_C
w __gmon_start__
w _ITM_deregisterTMCloneTable
w _ITM_registerTMCloneTable
U Perl_croak_xs_usage
U Perl_mg_set
U Perl_newXS_deffile
U Perl_sv_2iv_flags
U Perl_sv_2pv_flags
U Perl_sv_newmortal
U Perl_sv_setpv
U Perl_xs_boot_epilog
U Perl_xs_handshake
U PL_current_context
U __tls_get_addr@GLIBC_2.3
The function name 'boot_gropdf_1c9b' does not look like it depends on the
groff version.
Bruno