Re: Fortran libraries on the Blue Gene with mpi

Hi Ralf, Ralf Wildenhues wrote: Hello John, OK. That's fairly easy to support in Libtool then: the only thing we need to get right is to turn off shared library support completely for BG/L. I gave the wrong impression. This is a BG/P. My previous reference to the compilers was bec

Re: version and release number

On Thu, 16 Apr 2009, Lorenzo Bettini wrote: so would you suggest to use only version info and no release info, am I right? I was only concerned about the fact that the release number of the library is not visible anywhere and that it would force the use to specify a name together with the nu

Re: version and release number

* Lorenzo Bettini wrote on Thu, Apr 16, 2009 at 09:30:43PM CEST: > Bob Friesenhahn wrote: >> The -release option specifies part of the base naming for your library >> so that it becomes part of the base library name. For example, >> libfoo-1.0.so and libfoo-2.0.so. To the operating system the

Re: version and release number

Bob Friesenhahn wrote: On Thu, 16 Apr 2009, Lorenzo Bettini wrote: Never try to set the interface numbers so that they correspond to the release number of your package. This is an abuse that only fosters misunderstanding of the purpose of library versions. Instead, use the -release flag (see

Re: Fortran libraries on the Blue Gene with mpi

* Christian Rössel wrote on Thu, Apr 16, 2009 at 10:41:38AM CEST: > Ralf Wildenhues gmx.de> writes: > > > What do > > path/to/config.guess > > > > and > > CC=/opt/ibmcmp/xlc/bg/9.0/bin/bgcc path/to/config.guess > > > > output for the system triplets? Please download the latest config.guess

Re: libtool 1.5.2* problem

On Thu, 16 Apr 2009, Ralf Wildenhues wrote: Hello Vincent, * Vincent Torri wrote on Thu, Apr 16, 2009 at 01:04:00PM CEST: I know that libtool 1.5.2* is a very old version, not maintained anymore, but i would like to know if the problem that I have is related to that version or not. I cross c

Re: libtool 1.5.2* problem

Hello Vincent, * Vincent Torri wrote on Thu, Apr 16, 2009 at 01:04:00PM CEST: > I know that libtool 1.5.2* is a very old version, not maintained anymore, > but i would like to know if the problem that I have is related to that > version or not. I cross compile to have a Windows dll (in case it

Re: libtool 1.5.2* problem

On Thu, 16 Apr 2009, Vincent Torri wrote: I know that libtool 1.5.2* is a very old version, not maintained anymore, but i would like to know if the problem that I have is related to that version or not. I cross compile to have a Windows dll (in case it matters) I link a lib named 'toto' agains

Re: version and release number

On Thu, 16 Apr 2009, Lorenzo Bettini wrote: Never try to set the interface numbers so that they correspond to the release number of your package. This is an abuse that only fosters misunderstanding of the purpose of library versions. Instead, use the -release flag (see Release numbers), but be

libtool 1.5.2* problem

Hey, I know that libtool 1.5.2* is a very old version, not maintained anymore, but i would like to know if the problem that I have is related to that version or not. I cross compile to have a Windows dll (in case it matters) I link a lib named 'toto' against libfoo.la. In libfoo.la, in the

version and release number

Hi I've just started using libtool and in the manual you read: Never try to set the interface numbers so that they correspond to the release number of your package. This is an abuse that only fosters misunderstanding of the purpose of library versions. Instead, use the -release flag (see Rele

Re: Fortran libraries on the Blue Gene with mpi

Ralf Wildenhues gmx.de> writes: > What do > path/to/config.guess > > and > CC=/opt/ibmcmp/xlc/bg/9.0/bin/bgcc path/to/config.guess > > output for the system triplets? Please download the latest config.guess > and config.sub files from for > this te