Skip to contentSkip to conversation

Wolverine RPMs

Linux-ia64 Don Dugger 5 participants 5 messages Sep 5, 2001 – Sep 10, 2001

lore
Share & tools
lore

Don Dugger

author
#0 lore raw

Bill raises an interesting problem. I'd like to suggest a solution and see what everyone thinks. Since all of the shared objects are loaded by code in `ld-linux.so' I can modify the IA32 version of that library to first try an absolute path and, if that fails, because it's missing or has the wrong architecture, to then tack on a unique prefix, either something like /usr/ia32' or the contents of an environment variable like LD_IA32_PATH'.

This is a little ugly since all of the distro's would have to install s special version of `ld-linux.so' but at least this is just one library so that cuts the pain down a little bit.

Does anyone have a better idea?

Quoted 16 lines · Bill Nottingham

The biggest problem I've seen is with programs that have hardcoded paths for shared objects they dlopen(). Obviously this fails pretty badly when the ia32 binary trys to dlopen() an ia64 library.

Notably, this affects GTK+ when trying to use themes, and anything that uses PAM.

Bill

_______________________________________________
ia64-list mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/ia64-list

Signature · 4 lines
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
[email protected]
Ph: 303/938-9838
#1 lore raw

Don and others:

Let's not forget what might need to be considered to allow LSB 32 bit compliant apps on IA64. Even though no one may ever certify for this, it would be nice to find out and follow a convention that would benefit all.

Doug

Quoted 42 lines · Don Dugger

Bill raises an interesting problem. I'd like to suggest a solution and see what everyone thinks. Since all of the shared objects are loaded by code in `ld-linux.so' I can modify the IA32 version of that library to first try an absolute path and, if that fails, because it's missing or has the wrong architecture, to then tack on a unique prefix, either something like /usr/ia32' or the contents of an environment variable like LD_IA32_PATH'.

This is a little ugly since all of the distro's would have to install s special version of `ld-linux.so' but at least this is just one library so that cuts the pain down a little bit.

Does anyone have a better idea?

Quoted 8 lines · Bill Nottingham

The biggest problem I've seen is with programs that have hardcoded paths for shared objects they dlopen(). Obviously this fails pretty badly when the ia32 binary trys to dlopen() an ia64 library.

Notably, this affects GTK+ when trying to use themes, and anything that uses PAM.

Quoted 8 lines

Bill

_______________________________________________
ia64-list mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/ia64-list

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale [email protected]
Ph: 303/938-9838

_______________________________________________
Linux-IA64 mailing list
[email protected]
http://lists.linuxia64.org/lists/listinfo/linux-ia64

Signature · 4 lines
Douglas B. Beattie
------------------
Linux Test Architect - Caldera, Inc.
[email protected]
#2 lore raw
In reply to Don Dugger

Have you folks looked at the "UNIX System V Application Binary Interface" at
http://developer.intel.com/design/IA-64/ ? Section 5.3.1 suggests locations for the libraries.

Thanks
Sunil

-----Original Message-----
From: Doug Beattie [mailto:[email protected]]
Sent: Wednesday, September 05, 2001 10:57 AM
To: Don Dugger
Cc: Bill Nottingham; [email protected]; [email protected]
Subject: Re: [Linux-ia64] Re: Wolverine RPMs

Don and others:

Let's not forget what might need to be considered to allow LSB 32 bit compliant apps on IA64. Even though no one may ever certify for this, it would be nice to find out and follow a convention that would benefit all.

Doug

Quoted 2 lines · Don Dugger

Bill raises an interesting problem. I'd like to suggest a solution and

see

Quoted 2 lines

what everyone thinks. Since all of the shared objects are loaded by code in `ld-linux.so' I can modify the IA32 version of that library to first

try

Quoted 3 lines

an absolute path and, if that fails, because it's missing or has the wrong architecture, to then tack on a unique prefix, either something like `/usr/ia32' or the contents of an environment variable like

`LD_IA32_PATH'.

Quoted 35 lines

This is a little ugly since all of the distro's would have to install s special version of `ld-linux.so' but at least this is just one library so that cuts the pain down a little bit.

Does anyone have a better idea?

Quoted 8 lines · Bill Nottingham

The biggest problem I've seen is with programs that have hardcoded paths for shared objects they dlopen(). Obviously this fails pretty badly when the ia32 binary trys to dlopen() an ia64 library.

Notably, this affects GTK+ when trying to use themes, and anything that uses PAM.

Quoted 8 lines

Bill

_______________________________________________
ia64-list mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/ia64-list

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale [email protected]
Ph: 303/938-9838

_______________________________________________
Linux-IA64 mailing list
[email protected]
http://lists.linuxia64.org/lists/listinfo/linux-ia64

Signature · 9 lines
Douglas B. Beattie
------------------
Linux Test Architect - Caldera, Inc.
[email protected]

_______________________________________________
Linux-IA64 mailing list
[email protected]
http://lists.linuxia64.org/lists/listinfo/linux-ia64
#3 lore raw
In reply to Don Dugger
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Doug" = Doug Beattie <[email protected]> writes:

Doug> Don and others: Let's not forget what might need to be Doug> considered to allow LSB 32 bit compliant apps on IA64. Even Doug> though no one may ever certify for this, it would be nice to Doug> find out and follow a convention that would benefit all.

I thought we had settled on this years ago, there will be no LP32 Linux/ia64 support. It's just a waste of effort on maintenance, ie. I don't fancy maintaining two copies of glibc.

Jes

#4 lore raw
In reply to Don Dugger
Quoted 10 lines · Jes Sorensen
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Doug" = Doug Beattie <[email protected]> writes:

Doug> Don and others: Let's not forget what might need to be Doug> considered to allow LSB 32 bit compliant apps on IA64. Even Doug> though no one may ever certify for this, it would be nice to Doug> find out and follow a convention that would benefit all.

I thought we had settled on this years ago, there will be no LP32 Linux/ia64 support. It's just a waste of effort on maintenance, ie. I don't fancy maintaining two copies of glibc.

In this context 32Bit = IA32.

Christoph

Signature · 1 line
Whip me.  Beat me.  Make me maintain AIX.