Problem with .so numbering on FreeBSD in contrast to Linux

Alexander Leidinger Alexander at
Sun Feb 22 00:35:03 PST 2009

Quoting Thomas Schmitt <scdbackup at> (from Sat, 21 Feb 2009  
11:12:51 +0100):

> Hi,
> it looks like the problem is indeed in
> of my source packages. The decisive code piece
> is not the one from my last mail but this
>         freebsd-elf)
>           major=".$current"
>           versuffix=".$current";
>           ;;
> which i replaced by this (learned from case linux)
>         freebsd-elf)
>           major=.`expr $current - $age`
>           versuffix="$major.$age"
>           ;;
> Input parameters are: current=31, age=27, revision=0.
> So this now leads to installation of
> which i believe complies to policies-shlib.html.

I think this is a little bit outdated. We only have one number after  
the .so since a long time. All libs in /lib and /usr/lib are .so.X and  
for 3rd party applications most are .so.X (those which aren't are a  
sign of bugs in the ports collection). On one of my systems 1.2% are  
not .so.X:

% ls -1 | grep .so. | wc -l
% ls -1 | grep .so. | egrep '\.so\.[0-9]\.[0-9]' | wc -l

> Next questions:
> Is  freebsd-aout  of any importance nowadays ?

No. Those FreeBSD versions which used a.out instead of ELF are not  
supported anymore since a very very long time. We still are able to  
load a.out stuff in the current releases, but the entire compiler  
toolchain is using ELF by default. You have to make some effort to  
generate a.out stuff.


Bender: "Aw, I think I got whiplash."
Leela: "You can't have whiplash, you don't have a neck."
Bender: "I meant ass whiplash."    Alexander @ PGP ID = B0063FE7       netchild @  : PGP ID = 72077137

More information about the freebsd-ports mailing list