[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: PROPOSAL: lsb lib and lsb loader location

What if anything are we doing to handle cases, as there will be on
IA64, where we will have the native lsb lib directories, and
additional ones to allow for IA32 binary execution on IA64?

Do we say IA32 LSB compliant apps that could possibly run on IA64
platforms loose their compliance if not native?

Currently, IA64 distro's need to provide a /usr/lib/ia32 or some such
area with /etc/ld.so.conf modified to also look for these additional
libs and the loader is smart enough to know what to do with the apps.
Do or should we have /ia32liblsb and /opt/lsb/ia32lib's too?

Does anyone feel strongly or is the spec detailed to handle lsb
compliance for IA32 apps trying to run in an IA64 environment, or is
this not even something to worry about?

Don Dugger of VA has implemented IA32 on IA64 so I have also included
him in this mailing. (Sorry Don :( )

Thanks for your comments,

gk4@us.ibm.com wrote:
> Correct me if I'm wrong; however, to be more inline with the FHS v2.2 I
> would have thought:
> runtime  libraries  ->      /liblsb/  # no slash between lib and lsb
> Stub       libraries    ->      /opt/lsb/lib/      # not required for
> runtime systems,
> # but needed for link testing of LSB compliant applications
> PS: sorry for the delayed response.  I'm reading email while enroute to
> Tokyo.
> Johannes, since I'm out of the office and my responses are delayed.  Please
> feel free to take the lead on this and correct the spec and sample
> implementation to match with your conclusion.
> George Kraft IV
> gk4@austin.ibm.com
> IBM Linux Technology Center
> FSG's Linux Standard Base
> Johannes Poehlmann <jhp@caldera.de> on 05/30/2001 10:54:13 AM
> Please respond to Johannes Poehlmann <jhp@caldera.de>
> To:   George Kraft/Austin/IBM@IBMUS
> cc:   lsb-spec@lists.linuxbase.org
> Subject:  PROPOSAL: lsb lib and lsb loader location
> There has been confusion on the place where lsb libs should be stored
> and there are contradiction between lsbdev, sample implementation and spec.
> 1. lsb libs location.
> /usr/lsb has been objected as violation FHS (Which it does)
> I discussed the topic with Stuart and we agreed, that stub libraries
> and lsb runtime libraries should be in different locations.
> So my proposal is:
> runtime  libraries    ->      /lib/lsb
> Stub       libraries    ->      /usr/lib/lsb-stub.
> I decided against /lib-lsb and /usr/lib-lsbstub beacuse of esthetics.
> Runtime libs can not live in /usr, because they could be needed
> before /usr is mounted at system startup.
> 2. loader location:
>  Putting the loader in a different directory then the dir where glibc
>  puts its library files is only possible by moving the loader by hand.
>  glibc experts told me.
>  So the loader should be /lib/lsb/ld-linux.
> 3. This changes must become part of
>  o The spec
>  o libcheck (search /lib-lsb)
>  o The lsb loader /lib/lsb/ld-linux
>  o Ralf Flaxas  xdevel package
>  o Ralfs Flaxas minimal runtime.
> --
>      ______   ___
>     /  ___/__/  /                 Caldera (Deutschland) GmbH
>    /  /_/ _  / /__        Naegelsbachstr. 49c, 91052 Erlangen, Germany
>   /_____/_/ /____/            software developer / lsb project
>  ==== /____/ =====   Dipl. Inf. Johannes Poehlmann, mail: jhp@caldera.de
> Caldera OpenLinux    phone: ++49 9131 7192 335, fax: ++49 9131 7192 399
> --
> To UNSUBSCRIBE, email to lsb-spec-request@lists.linuxbase.org
> with subject of "unsubscribe". Trouble? Email
> listmaster@lists.linuxbase.org
> --
> To UNSUBSCRIBE, email to lsb-spec-request@lists.linuxbase.org
> with subject of "unsubscribe". Trouble? Email listmaster@lists.linuxbase.org

Douglas B. Beattie
Linux Test Architect - Caldera, Inc.

Reply to: