[SCM] GNU Libtool branch, master, updated. v2.2.6-203-g3ae7bf0

2010-05-03 Thread Peter O'Gorman
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project GNU Libtool. The branch, master has been updated via 3ae7bf0b911b9765151e9b5c51656bed2e07b01d (commit) from

[PATCH] Ranlib is required with -force_load and fat archives.

2010-05-03 Thread Peter O'Gorman
I got a report from Jeremy that -force_load with multi-architecture archives requires that the archives be ranlibbed. Pushed this. Peter From 8f76455acfbfd28d695720507f78dc533f2d7a4c Mon Sep 17 00:00:00 2001 From: Peter O'Gorman pe...@pogma.com Date: Tue, 4 May 2010 00:44:48 -0500 Subject:

Re: libtool versioning

2010-05-03 Thread Jef Driesen
On 02/05/10 03:33, Bob Friesenhahn wrote: On Sun, 2 May 2010, Jef Driesen wrote: I'm trying to understand the libtool current:revision:age versioning scheme. I think I understand how it works, but I noticed that filename of the shared library seems to get different numbers

Re: libtool versioning

2010-05-03 Thread Matěj Týč
I'm trying to understand the libtool current:revision:age versioning scheme. I think I understand how it works, but I noticed that filename of the shared library seems to get different numbers (current-age.age.revision). Is that expected? The filename generation is dependent on the OS.  It

Re: libtool versioning

2010-05-03 Thread Bob Friesenhahn
On Mon, 3 May 2010, Jef Driesen wrote: # 6. If any interfaces have been removed since the last public release, # then set age to 0. Shouldn't step #6 included changed as well as removed? If you change the interface (for example modifying function parameters), backwards compatibility is

Re: libtool versioning

2010-05-03 Thread Bob Friesenhahn
On Mon, 3 May 2010, Matěj Týč wrote: If I have understood correctly, the whole LTversion stuff has only one purpose - to inform users what have they installed. More specifically, it provides libtool with the information needed to produce a suitably numbered library to satisfy a

Re: libtool versioning

2010-05-03 Thread Gary V. Vaughan
On 3 May 2010, at 23:09, Bob Friesenhahn wrote: On Mon, 3 May 2010, Matěj Týč wrote: If I have understood correctly, the whole LTversion stuff has only one purpose - to inform users what have they installed. More specifically, it provides libtool with the information needed to

Re: libtool versioning

2010-05-03 Thread Jef Driesen
On 03/05/10 20:00, Ralf Wildenhues wrote: Hello Jef, * Jef Driesen wrote on Mon, May 03, 2010 at 09:08:14AM CEST: On 02/05/10 03:33, Bob Friesenhahn wrote: On Sun, 2 May 2010, Jef Driesen wrote: I'm trying to understand the libtool current:revision:age versioning scheme. I think I

Re: libtool versioning

2010-05-03 Thread Ralf Wildenhues
* Jef Driesen wrote on Mon, May 03, 2010 at 08:24:09PM CEST: Yes, I have read the libtool manual, but it doesn't contain much info about the resulting filename. Most of the info is about the c:r:a scheme for input, not the output. Yes, because the output file name is a per-system detail that

Re: libtool versioning

2010-05-03 Thread Michel Briand
Jef Driesen jefdrie...@hotmail.com - Mon, 03 May 2010 20:24:09 +0200 On 03/05/10 20:00, Ralf Wildenhues wrote: Hello Jef, * Jef Driesen wrote on Mon, May 03, 2010 at 09:08:14AM CEST: On 02/05/10 03:33, Bob Friesenhahn wrote: On Sun, 2 May 2010, Jef Driesen wrote: The git master version of