Re: Implementing LIBTOOL on OpenVMS

2005-12-02 Thread Ralf Wildenhues
Hi John, Sorry for the delay. I had to read a bit about OpenVMS first. * John E. Malmberg wrote on Tue, Nov 29, 2005 at 12:25:56AM CET: > Ralf Wildenhues wrote: > >* John E. Malmberg wrote on Fri, Nov 18, 2005 at 09:26:14PM CET: > > >>3. For dot-n releases, in order to provide upward compatibil

Re: libtool rearranging library paths

2005-12-02 Thread Ralf Wildenhues
* Christopher Hulbert wrote on Fri, Dec 02, 2005 at 05:31:52PM CET: > > On another note, why does libtool add an entire static archive (.a) if > > it wasn't created with libtool? I did an nm on a convenience library > > and it had a .a stuck in there and nm complained that it didn't know > > what

Re: libtool rearranging library paths

2005-12-02 Thread Ralf Wildenhues
Hi Christopher, * Christopher Hulbert wrote on Fri, Dec 02, 2005 at 05:23:06PM CET: > On 12/2/05, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > * Christopher Hulbert wrote on Fri, Dec 02, 2005 at 01:29:52PM CET: > > > On 12/2/05, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > This issue is a b

Re: libtool rearranging library paths

2005-12-02 Thread Christopher Hulbert
> On another note, why does libtool add an entire static archive (.a) if > it wasn't created with libtool? I did an nm on a convenience library > and it had a .a stuck in there and nm complained that it didn't know > what file type that was. It was also missing the symbols from inside > that arch

Re: libtool rearranging library paths

2005-12-02 Thread Christopher Hulbert
On 12/2/05, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Hi Christopher, > > * Christopher Hulbert wrote on Fri, Dec 02, 2005 at 01:29:52PM CET: > > On 12/2/05, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > No I don't think it's a libtool problem. Basiclly I call the > > AC_FC_LIBRARY_LDFLAGS

Re: libtool rearranging library paths

2005-12-02 Thread Ralf Wildenhues
Hi Christopher, * Christopher Hulbert wrote on Fri, Dec 02, 2005 at 01:29:52PM CET: > On 12/2/05, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > * Christopher Hulbert wrote on Fri, Dec 02, 2005 at 12:48:13PM CET: > > > > > The other problem I have is I have to set FCFLAGS to -fpic so when > > > au

Re: libtool rearranging library paths

2005-12-02 Thread Christopher Hulbert
On 12/2/05, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: Hi Christopher,* Christopher Hulbert wrote on Fri, Dec 02, 2005 at 12:48:13PM CET:> That's what I get for not following Rule #1 (Make sure you are using the> latest version).  1.5.20 seemed to fix it. Good to know.> The other problem I have is

Re: libtool rearranging library paths

2005-12-02 Thread Ralf Wildenhues
Hi Christopher, * Christopher Hulbert wrote on Fri, Dec 02, 2005 at 12:48:13PM CET: > That's what I get for not following Rule #1 (Make sure you are using the > latest version). 1.5.20 seemed to fix it. Good to know. > The other problem I have is I > have to set FCFLAGS to -fpic so when autocon

Re: libtool rearranging library paths

2005-12-02 Thread Christopher Hulbert
That's what I get for not following Rule #1 (Make sure you are using the latest version).  1.5.20 seemed to fix it.  The other problem I have is I have to set FCFLAGS to -fpic so when autoconf gets the Fortran libraries to link with pgf90 puts the libso first.  Is there another way to do that?  per

Re: libtool rearranging library paths

2005-12-02 Thread Ralf Wildenhues
Hi Christopher, * Christopher Hulbert wrote on Fri, Dec 02, 2005 at 03:41:41AM CET: > I have a some fortran code compiled by libtool into a static (convenience > archive). Later I compile a C source file into a shared library linking > against the fortran library. Since automake/libtool have no