Re: Alternate SONAME values

2005-08-09 Thread Ralf Wildenhues
Hi Keith, others, Sorry for the response latency. This is a status update for the -sobase patch: http://lists.gnu.org/archive/html/libtool/2005-07/msg00093.html. * Keith Packard wrote on Mon, Jul 11, 2005 at 09:55:47PM CEST: On Mon, 2005-07-11 at 13:58 +0200, Ralf Wildenhues wrote:

Re: Alternate SONAME values

2005-08-09 Thread Keith Packard
On Tue, 2005-08-09 at 15:13 +0200, Ralf Wildenhues wrote: Hi Keith, others, Sorry for the response latency. This is a status update for the -sobase patch: http://lists.gnu.org/archive/html/libtool/2005-07/msg00093.html. Thanks for your response and your work on this matter. Your patch

Re: Alternate SONAME values

2005-07-11 Thread Ralf Wildenhues
Hi Keith, * Keith Packard wrote on Fri, Jul 08, 2005 at 11:42:57PM CEST: On Fri, 2005-07-08 at 11:23 +0200, Simon Richter wrote: Now I'm wondering whether it would make sense to add a switch to libtool that makes it not install those two things, such as -old-abi. I have to support two

Re: Alternate SONAME values

2005-07-11 Thread Keith Packard
On Mon, 2005-07-11 at 13:58 +0200, Ralf Wildenhues wrote: Re-reading this thread, I would be inclined to accept a patch which implements your original proposal, given that a way can be found how it degrades gracefully on the different/not-so-flexible shared library systems mentioned. That

Re: Alternate SONAME values

2005-07-08 Thread Ralf Wildenhues
Hi Keith, * Keith Packard wrote on Fri, Jul 08, 2005 at 06:59:10AM CEST: On Fri, 2005-07-08 at 09:24 +0530, Ganesan Rajagopal wrote: But libXaw.so.major_number is the default behaviour for libtool. Are you using -release instead of -version-info or -version-number? I think

Re: Alternate SONAME values

2005-07-08 Thread Ganesan Rajagopal
Keith == Keith Packard [EMAIL PROTECTED] writes: On Fri, 2005-07-08 at 09:24 +0530, Ganesan Rajagopal wrote: But libXaw.so.major_number is the default behaviour for libtool. Are you using -release instead of -version-info or -version-number? I think -version-number will give you exactly

Re: Alternate SONAME values

2005-07-08 Thread Keith Packard
On Fri, 2005-07-08 at 08:31 +0200, Ralf Wildenhues wrote: First, to stay with your GNU/Linux example, unless you also have libXaw.so.6 as symlink, how will ld.so find your library (as installed library; or alternatively as user-installed test version below $HOME)? The current ELF shared

Re: Alternate SONAME values

2005-07-08 Thread Ganesan Rajagopal
Russ == Russ Allbery [EMAIL PROTECTED] writes: Ganesan Rajagopal [EMAIL PROTECTED] writes: I didn't know this. But trying to make -version-info get the SONAME you need is an abuse of libtool in any case. I think -version-number option available in recent versions of libtool is perfect for

Re: Alternate SONAME values

2005-07-08 Thread Ganesan Rajagopal
Keith == Keith Packard [EMAIL PROTECTED] writes: No, I haven't. I have little experience with these systems, so I don't even know if this scheme will work. Hence my question to this list where I imagine there are people with experience on those systems. The key question is whether the system

Re: Alternate SONAME values

2005-07-08 Thread Simon Richter
Hi, Keith Packard wrote: I want the SONAME to be libXaw.so.6, but the filename to be libXaw6.la, libXaw6.so.6.0.1, libXaw6.so.6 and libXaw6.so There is no need to name the real file libXaw6.so.6.0.1, as the 6 is mentioned twice this way (libXaw.so.6.0.1 suffices). The unversioned symlink and

Re: Alternate SONAME values

2005-07-08 Thread Ralf Wildenhues
Hi Keith, * Keith Packard wrote on Fri, Jul 08, 2005 at 08:47:37AM CEST: On Fri, 2005-07-08 at 08:31 +0200, Ralf Wildenhues wrote: First, to stay with your GNU/Linux example, unless you also have libXaw.so.6 as symlink, how will ld.so find your library (as installed library; or

Re: Alternate SONAME values

2005-07-08 Thread Ralf Wildenhues
* Ralf Wildenhues wrote on Fri, Jul 08, 2005 at 04:15:53PM CEST: Keith, could you confirm that this would be enough for your needs, when given as install mode switch? Current idea would be to have it install the first name from library_names only, do not delete the symlinks nor s/the first

Re: Alternate SONAME values

2005-07-08 Thread Keith Packard
On Fri, 2005-07-08 at 14:10 +0530, Ganesan Rajagopal wrote: Keith == Keith Packard [EMAIL PROTECTED] writes: No, I haven't. I have little experience with these systems, so I don't even know if this scheme will work. Hence my question to this list where I imagine there are people with

Re: Alternate SONAME values

2005-07-08 Thread Keith Packard
to make sure I create the links at install time. Of course, if we do hack libtool to support alternate SONAME values, we could also hack it to manage these symlinks for us. -keith signature.asc Description: This is a digitally signed message part ___ http

Re: Alternate SONAME values

2005-07-08 Thread Keith Packard
On Fri, 2005-07-08 at 16:15 +0200, Ralf Wildenhues wrote: Keith, could you confirm that this would be enough for your needs, when given as install mode switch? Current idea would be to have it install the first name from library_names only, do not delete the symlinks nor create new ones, do

Re: Alternate SONAME values

2005-07-08 Thread Keith Packard
On Fri, 2005-07-08 at 11:23 +0200, Simon Richter wrote: Now I'm wondering whether it would make sense to add a switch to libtool that makes it not install those two things, such as -old-abi. I have to support two of these library versions as 'current' for other reasons, so applications need to

Alternate SONAME values

2005-07-07 Thread Keith Packard
I'm building a weird set of libraries and would like libtool to help out a bit by providing some mechanism to modify the SONAME placed into the .so file. X has three versions of the Xaw library; version 6, 7 and 8 (cooresponding to the .so major version numbers, which are the same across all

Re: Alternate SONAME values

2005-07-07 Thread Ganesan Rajagopal
Keith == Keith Packard [EMAIL PROTECTED] writes: There is another way to solve the problem; we can change the SONAME in the versioned filename varients: Version 6 Xaw - libXaw6.so.6.0.1 SONAME=libXaw.so.6 Version 7 Xaw - libXaw7.so.7.0.0 SONAME=libXaw.so.7 Version 8 Xaw - libXaw8.so.8.0.0

Re: Alternate SONAME values

2005-07-07 Thread Albert Chin
On Thu, Jul 07, 2005 at 03:53:17PM +0530, Ganesan Rajagopal wrote: Keith == Keith Packard [EMAIL PROTECTED] writes: There is another way to solve the problem; we can change the SONAME in the versioned filename varients: Version 6 Xaw - libXaw6.so.6.0.1 SONAME=libXaw.so.6

Re: Alternate SONAME values

2005-07-07 Thread Keith Packard
On Thu, 2005-07-07 at 15:53 +0530, Ganesan Rajagopal wrote: Keith == Keith Packard [EMAIL PROTECTED] writes: There is another way to solve the problem; we can change the SONAME in the versioned filename varients: Version 6 Xaw - libXaw6.so.6.0.1 SONAME=libXaw.so.6 Version 7 Xaw

Re: Alternate SONAME values

2005-07-07 Thread Ganesan Rajagopal
Keith == Keith Packard [EMAIL PROTECTED] writes: On Thu, 2005-07-07 at 15:53 +0530, Ganesan Rajagopal wrote: Keith == Keith Packard [EMAIL PROTECTED] writes: There is another way to solve the problem; we can change the SONAME in the versioned filename varients: Version 6 Xaw -

Re: Alternate SONAME values

2005-07-07 Thread Ganesan Rajagopal
Albert == Albert Chin [EMAIL PROTECTED] writes: On Thu, Jul 07, 2005 at 03:53:17PM +0530, Ganesan Rajagopal wrote: Keith == Keith Packard [EMAIL PROTECTED] writes: There is another way to solve the problem; we can change the SONAME in the versioned filename varients: Version 6 Xaw

Re: Alternate SONAME values

2005-07-07 Thread Keith Packard
On Fri, 2005-07-08 at 09:24 +0530, Ganesan Rajagopal wrote: But libXaw.so.major_number is the default behaviour for libtool. Are you using -release instead of -version-info or -version-number? I think -version-number will give you exactly what you need. I want the SONAME to be libXaw.so.6,

Re: Alternate SONAME values

2005-07-07 Thread Russ Allbery
Ganesan Rajagopal [EMAIL PROTECTED] writes: I didn't know this. But trying to make -version-info get the SONAME you need is an abuse of libtool in any case. I think -version-number option available in recent versions of libtool is perfect for this. When introducing libtool with a libraries