Re: Difference on shared lib installation on NetBSD vs. Linux and others (trying to update openblas packages)

Am Sun, 22 Feb 2026 22:28:12 +0100
schrieb "Dr. Thomas Orgis" <[email protected]>:

> I wonder if I should try to fix things for Darwin, too. Actually, I may
> have forgotten. Will PLIST with
> 
> lib/lib${OPENBLAS_VARIANT}.so
> lib/lib${OPENBLAS_VARIANT}.so.0

May anyone enlighten me on this one? I see some PLIST files with .so,
some with .dylib, some with ${SHEXT} … I see no reference to this in
the pkgsrc guide or in pkgsrc/doc/.

I know that .la files stand in for the shared libs mentioned in them,
so work as portable PLIST entries. But what is the case with naked .so
or .dylib (or .dll, $DEITY forbid)?

I can dig around and try to interpret what some script in mk/ does …
but I think it would be nice if this was spelled out in human language
and included in the reference documentation. What are you supposed to
put into a PLIST and what magic works on that file? Did I miss the
correct place where this is documented? The make help queries?

I find mk/plist/sh-dylib. It says:

#
# This awk script is a filter that reads PLIST entries and transforms
# and expands entries that match ELF library into the appropriate Mach-O
# dylib names.
#

I guess it makes it 'just work' to have .so files in PLIST and
translate them to the matching .dylib. But a quick glance at the awk
(I'm used to Perl, but not old enough for awk) doesn't immediately tell
me if so.0 would be translated to 0.dylib (I am cargo-assuming that the
soversion numbering is swapped around like that on Darwin).

Especially if the person writing that script in 2006 is not with us
anymore, it would be nice to have the transformations documented
plainly. Anyone got the full picture?


Alrighty then,

Thomas

-- 
Dr. Thomas Orgis
HPC @ Universität Hamburg