MirBSD support and a question

[Benny Siegert]

Hello!

I would like to add MirBSD support to upstream libtool. MirBSD (or MirOS 
BSD) is an OS derived from OpenBSD. I want to use version_type=linux 
instead of sunos because it works much better, from several years 
experience with our own patched version of libtool 1.5.

A notable idiosyncrasy of our runtime linker is that shared libraries 
_must_ have a two-digit version (libfoo.so.0.0 for example) to be able to 
link against them. In the attached patch, I solved it like this:

library_names_spec='${libname}${release}${shared_ext}${major}.${age} 
${libname}${shared_ext}${major}.${age}'

Is this okay or should it be done differently?

However, there is one case where this breaks: When a -release is given but 
no -version-info, the $major variable is reset. In ltmain.m4sh, line 6705, 
$major is reset to an empty string:

        # Clear the version info if we defaulted, and they specified a 
release.
        if test -z "$vinfo" && test -n "$release"; then
          major=

Why is this so? Can this line be safely removed?

--Benny.

0001-Add-MirBSD-stanzas-to-m4-files.patch
Description: Text document