Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#630411: libc6 should define /lib/ld-lsb-x86-64.so.3 on AMD64

83 views
Skip to first unread message

Aurelien Jarno

unread,
Jun 13, 2011, 4:10:02 PM6/13/11
to
On Mon, Jun 13, 2011 at 09:13:34PM +0200, francois....@bureauveritas.com wrote:
> Package: libc6
> Version: 2.11.2-10
> Severity: normal
>
> 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@masime:/tmp> lsb_release --all
> LSB Version:
> core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:
> core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.
> 0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-
> amd64:graphics-4.0-noarch
> Distributor ID: SUSE LINUX
> Description: SUSE Linux Enterprise Server 11 (x86_64)
> Release: 11
> Codename: n/a
> fp2x@masime:/tmp> ls -lApst lm*
> 509 -rw-r--r-- 1 fp2x users 516479 juin 9 20:28 lmutil_x64_lsb.tar.gz
> 464 -rw-r--r-- 1 fp2x users 471556 juin 9 20:28 lmgrd_x64_lsb.tar.gz
> 1353 -rwxr-xr-x 1 fp2x users 1384304 d├®c. 7 2010 lmgrd
> 1429 -rwxr-xr-x 1 fp2x users 1461624 d├®c. 7 2010 lmutil
> fp2x@masime:/tmp> ./lmutil lmver -help
> lmutil - Copyright (c) 1989-2010 Flexera Software, Inc. All Rights
> Reserved.
> usage: lmver flexlm_binary
>
> fp2x@drhpcm03:/tmp$ lsb_release --all
> No LSB modules are available.
> Distributor ID: Debian
> Description: Debian GNU/Linux 6.0.1 (squeeze)
> Release: 6.0.1
> Codename: squeeze
> fp2x@drhpcm03:/tmp$ ls -lApst lm*
> 1432 -rwxr-xr-x 1 fp2x fp2x 1461624 7 d├®c. 2010 lmutil
> fp2x@drhpcm03:/tmp$ ./lmutil
> -bash: ./lmutil: Aucun fichier ou dossier de ce type
> fp2x@drhpcm03:/tmp$ echo $?
> 127
>
> extract of readelf -l lmutil
> INTERP 0x0000000000000200 0x0000000000400200 0x0000000000400200
> 0x000000000000001a 0x000000000000001a R 1
> [Requesting program interpreter: /lib64/ld-lsb-x86-64.so.3]
>
> program interpreter: /lib64/ld-lsb-x86-64.so.3 is a LSB requirement. For
> instance
> http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-AMD64/LSB-Core-AMD64/requirements.html
>

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.

--
Aurelien Jarno GPG: 1024D/F1BCDB73
aure...@aurel32.net http://www.aurel32.net

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Aurelien Jarno

unread,
Jun 13, 2011, 5:20:02 PM6/13/11
to
On Mon, Jun 13, 2011 at 10:56:24PM +0200, francois....@bureauveritas.com wrote:

> Aurelien Jarno <aure...@aurel32.net> a écrit sur 13/06/2011 21:58:51 :
> >
> > On Mon, Jun 13, 2011 at 09:13:34PM +0200, francois.
> > peti...@bureauveritas.com wrote:
> > > Package: libc6
> > > Version: 2.11.2-10
> > > Severity: normal
> > > Release: 6.0.1

> > >
> > > extract of readelf -l lmutil
> > > INTERP 0x0000000000000200 0x0000000000400200
> 0x0000000000400200
> > > 0x000000000000001a 0x000000000000001a R 1
> > > [Requesting program interpreter: /lib64/ld-lsb-x86-64.so.3]
> > >
> > > program interpreter: /lib64/ld-lsb-x86-64.so.3 is a LSB requirement.
> For
> > > instance
> > > http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-AMD64/LSB-
> > Core-AMD64/requirements.html
> > >
> >
> > 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 :
> alien{a} autopoint{a} cups-bsd{a} cups-client{a} cups-common{a}
> debhelper{a} ed{a} gettext{a} git{a} html2text{a} intltool-debian{a}
> lib32z1{a} libcurl3-gnutls{a} libelf1{a} liberror-perl{a}
> libfile-copy-recursive-perl{a} liblua5.1-0{a} libmail-sendmail-perl{a}
> librpm1{a} librpmbuild1{a} librpmio1{a} libsys-hostname-long-perl{a}
> libunistring0{a} lsb-core pax{a} po-debconf{a} rpm{a} rpm-common{a}
> rpm2cpio{a} update-inetd{a}
> 0 paquets mis à jour, 30 nouvellement installés, 0 à enlever et 0 non mis
> à jour.
> 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
> Abandon.
>
> I have 7 debian servers with a minimum set of packages for computations :
> openmpi, paraview, ...
> If possible, I want to avoi unneeded packages, and 30 packages to get a
> symlink is a bit heavy.

All these packages are needed for LSB compliance, either you want LSB
compliance or not.

> How to check which of the 30 packages installs the symlink ? A symlink do
> not seem to be listed in the files installed by lsb-core.

The symlinks is created in the post-install script of lsb-core, that's
why you don't see it in the list of files.

francois....@bureauveritas.com

unread,
Jun 13, 2011, 5:20:02 PM6/13/11
to
Aurelien Jarno <aure...@aurel32.net> a écrit sur 13/06/2011 21:58:51 :
>
> On Mon, Jun 13, 2011 at 09:13:34PM +0200, francois.
> peti...@bureauveritas.com wrote:
> > Package: libc6
> > Version: 2.11.2-10
> > Severity: normal
> > Release:        6.0.1

> >
> > extract of readelf -l lmutil
> >   INTERP         0x0000000000000200 0x0000000000400200 0x0000000000400200
> >                  0x000000000000001a 0x000000000000001a  R      1
> >       [Requesting program interpreter: /lib64/ld-lsb-x86-64.so.3]
> >
> > program interpreter: /lib64/ld-lsb-x86-64.so.3 is a LSB requirement. For
> > instance
> > http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-AMD64/LSB-
> Core-AMD64/requirements.html
> >
>
> 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 :
  alien{a} autopoint{a} cups-bsd{a} cups-client{a} cups-common{a}
  debhelper{a} ed{a} gettext{a} git{a} html2text{a} intltool-debian{a}
  lib32z1{a} libcurl3-gnutls{a} libelf1{a} liberror-perl{a}
  libfile-copy-recursive-perl{a} liblua5.1-0{a} libmail-sendmail-perl{a}
  librpm1{a} librpmbuild1{a} librpmio1{a} libsys-hostname-long-perl{a}
  libunistring0{a} lsb-core pax{a} po-debconf{a} rpm{a} rpm-common{a}
  rpm2cpio{a} update-inetd{a}
0 paquets mis à jour, 30 nouvellement installés, 0 à enlever et 0 non mis à jour.
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
Abandon.

I have 7 debian servers with a minimum set of packages for computations : openmpi, paraview, ...
If possible, I want to avoi unneeded packages, and 30 packages to get a symlink is a bit heavy.

How to check which of the 30 packages installs the symlink ? A symlink do not seem to be listed in the files installed by lsb-core.
>
> --
> Aurelien Jarno                           GPG: 1024D/F1BCDB73
> aure...@aurel32.net                 http://www.aurel32.net



Regards
F. Petitjean

Jonathan Nieder

unread,
Jun 14, 2011, 5:40:03 PM6/14/11
to
reassign 630411 lsb-core 3.2-27
retitle 630411 please provide /lib64/ld-lsb-x86-64.so.3 in a smaller package
severity 630411 wishlist
quit

Hi Chris et al,

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.

Anyway, I pass the report to you. :) Thoughts of all kinds welcome.

Regards,
Jonathan

Didier Raboud

unread,
Mar 2, 2012, 12:30:02 PM3/2/12
to
tags 630411 +wontfix
tags 630411 +help
thanks
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

Jeff Licquia

unread,
Mar 2, 2012, 1:40:02 PM3/2/12
to
On 03/02/2012 12:20 PM, Didier Raboud wrote:
>> François Petitjean wrote:
>> 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.

A few points of interest:

- the requirements for the dynamic linker symlink are documented in the
LSB specification (see refspecs.linuxbase.org for those)

- upstream LSB will be working on a solution for pulling in parts of
the LSB as part of the 5.0 development effort
0 new messages