-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong SONAME for alpha #96
Comments
Good catch, thanks. Unfortunately I don't think libtool supports sonames like this at all. I've got an experimental branch in which we build with meson instead, and I'll see if that can do it. (However, is it a potential problem for porters and/or new architectures if we use meson instead of autotools? You'd know better than me/) |
I have no experience at all with Meson, but since it is written in pure Python I suppose that it works on all Debian architectures. |
From the perspective of bootstrapping new architectures from scratch there shouldn't be any problems as they need to be cross-compiled, which is perfectly supported by meson, on some existing system with a working Python3 to get a basic stage-1 image/tarball anyways. |
Actually the soname is wrong only on alpha, ia64 is "standard". |
I can confirm that glibc installs $ qlist glibc | grep libcrypt.so.1
/lib/libcrypt.so.1.1
/usr/lib/libcrypt.so while libxcrypt installs $ qlist libxcrypt | grep libcrypt.so.1
/lib/libcrypt.so.1.1.0
/lib/libcrypt.so.1 On Gentoo, we rebuilt reverse dependencies of libcrypt when doing this transition, so it was not a problem for us. I believe this would have been a problem for a binary distribution that would necessitate a rebuild, since the SONAME in binaries is indeed $ readelf -a /usr/sbin/sshd |& grep libcrypt.so
0x0000000000000001 (NEEDED) Shared library: [libcrypt.so.1.1]
000000: Version: 1 File: libcrypt.so.1.1 Cnt: 1 On ia64, glibc installs $ qlist glibc | grep libcrypt.so.1
/lib/libcrypt.so.1 $ qlist libxcrypt | grep libcrypt.so.1
/lib/libcrypt.so.1.1.0
/lib/libcrypt.so.1 |
A Debian porter noticed that alpha and ia64 use
libcrypt.so.1.1
instead oflibcrypt.so.1
.I am not even sure that it is possible for libcrypt to use a SONAME like this, so for the time being I am patching libtool in the build directory:
perl -i -pe '/^(library_names_spec|soname_spec)=/ and s/major/major.1/'
The text was updated successfully, but these errors were encountered: