Bug#630411: #630411: libc6 should define /lib/ld-lsb-x86-64.so.3 on AMD64
Didier Raboud <[email protected]>
| Newsgroups | gmane.linux.debian.devel.lsb |
|---|---|
| Organization | EPFL - GR-KA |
| Message-ID | <[email protected]> |
tags 630411 +wontfix tags 630411 +help thanks > François Petitjean wrote: > >> After downloading a lsb binary for Linux on architecture amd64 (aka x_-_64) the >> program runs out of the box on a SLES11 machine, but fails on Debian wuth a cryp >> tic message : > [...] >> fp2x@drhpcm03:/tmp$ ./lmutil >> -bash: ./lmutil: Aucun fichier ou dossier de ce type > [...] >> Aurelien Jarno wrote: > >>> LSB compliance is provided through the lsb-core package. Installing this >>> package will create, among other things, the /lib64/ld-lsb-x86-64.so.3 >>> symlink. >> >> The problem lies in the "among other things" : >> fp2x@drhpcm03:/etc$ sudo aptitude install lsb-core >> Les NOUVEAUX paquets suivants vont être installés : >> [...] >> Il est nécessaire de télécharger 16,5 Mo d'archives. Après dépaquetage, >> 37,8 Mo seront utilisés. >> Voulez-vous continuer ? [Y/n/?] n > > In other words, on small (embedded?) systems it would be useful to be > able to run some LSB binaries without pulling in the entire LSB core. > Does that sound like something worth supporting to you? Perhaps we > just need some documentation somewhere like the Debian Reference or > glibc's README.Debian to explain how people can create the symlink > themselves. Hi François, and thanks for your bugreport, (Thanks to Jonathan for the triaging and summarizing, keep up the good job!) The purpose of LSB is to make a set of interfaces available, amongst which the /lib/ld-lsb.so.* linker symlinks, which don't carry much sense if seen alone. I don't think it's the role of any of the `lsb-` package else than lsb-core to provide those symlinks as they are only a tiny part of what the "LSB interface" is. Furthermore, given admin rights, creating those symlinks is straightforward. So I'm hereby tagging this bug as "wontfix" on the lsb-core package, because I don't think it's glibc's role to document that either. I'm also tagging it "help" as I wouldn't be hostile to review a patch to the packaging that would implement a lsb-core-ld that would take over the symlinks currently handled by lsb-core. Cheers, OdyX
signature.asc
(application/pgp-signature, 663 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iQGcBAEBAgAGBQJPUQFnAAoJEIvPpx7KFjRVedQL/2KoW97VR2oO0VwvSrc/NL/O vSEGAZ43E5vOhsqIvJXOGvn4V1fKjz7ILxN8syZdU6Gvlo/NEFuyzUbLpcTC8+Ut 8f53Se11YnW61jghmiqtVuzxVezDH4kz+vFsMPL8ZLJhvJ9CMxAakQG/xzenQUdn 4V6AbT9kW2/CiQpYdrIzSepsDUR8H6MuOXFK7pqpLia5iR+xU1R6ENGCKgI9wxyw Uh0X2dxcwWA8CZaMF5+ciLxJ0t86Hh7tnJ3mT2R1ysXbQu1cNdr7Hnix6DHzstzT k1qNHUUxBInwg3q5cyzS5keEo8TPF13xXmec69SDDAyqKbX5VaZCC3Tj4Un69xpx BMG8a0p6UAiz3AHzErAYFw25NEVoT/Hy9w0lsmUKOgIUhyz1zKnP9Gwr6QNxh0tj jS16LI7KQDi/i+7W2u6NzFMJLgcc8zWiRMWwIsBkr/TU6RMQRCye6oKY0/K9MH+S J87e2G9MxxDTt/mDd1XwCR/YL8M2aJM+YBPyhJ5QGQ== =eDcL -----END PGP SIGNATURE-----