Re: AM_FCFLAGS not working as I expect...

On Tue, Nov 08, 2005 at 06:43:43AM -0700, Ed Hartnett wrote: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > I forgot one thing: If you're trying to use libtool with the FC (Fortran > > 90/95) interface, you are likely to have to go through hoops with > > libtool-1.5.x, since it doesn't suppor

Re: AM_FCFLAGS not working as I expect...

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > If you use both $F77 and $FC in your package (which I believe you do), > the right thing would be to wait for Libtool-2.0 which has proper FC > support and is due pretty soon (I hope). Ah ha. But I believe that the only reason I am using both is th

Re: AM_FCFLAGS not working as I expect...

Hi Ed, * Ed Hartnett wrote on Tue, Nov 08, 2005 at 02:43:43PM CET: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > I forgot one thing: If you're trying to use libtool with the FC (Fortran > > 90/95) interface, you are likely to have to go through hoops with > > libtool-1.5.x, since it doesn't

Re: Problems with linking modules

It is not portable for modules to depend on each other. A better approach is to introduce a third shared library and have the two modules depend on that shared library. Any common code can live in the shared library. Bob On Tue, 8 Nov 2005, Jacob Kroon wrote: Hi, I'm using autoconf/automak

no TEXI2DVIFLAGS?

Howdy all! I am generating some documentation, and I am trying to get texi2dvi to shut up, as it produces a lot of output. The following works, but causes automake to generate a warning: # Get texi2dvi to shut the hell up! TEXI2DVI = texi2dvi -s Is there a better way to provide a flag for texi2

make dvi expected during make distcheck?

Howdy all! I have make distcheck working with my library, and I love it! Very cool! I notice that after it does a make all, it does a make dvi in every directory. Is this expected? Making all in man make[3]: Entering directory `/shecky/netcdf-3/netcdf-4.0-alpha10/_build/man' m4 -B1 -DAPI=C

Problems with linking modules

Hi, I'm using autoconf/automake to build 2 modules (xxx_la_LDFLAGS = -avoid-version -module), lets call them foo.la and bar.la. The problem I'm having is that bar.la uses symbols from foo.la, so I need to link bar.la with foo.la, but this is not portable according to libtool. If I do run "make"

Re: AM_FCFLAGS not working as I expect...

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > I forgot one thing: If you're trying to use libtool with the FC (Fortran > 90/95) interface, you are likely to have to go through hoops with > libtool-1.5.x, since it doesn't support it. Current CVS Libtool, which > will hopefully soon be Libtool-2.0,

Re: building 32bit and 64bit libs with the same name

On Tue, 2005-11-08 at 14:10 +0100, Harald Dunkel wrote: > Hi Ralf, > > Ralf Corsepius wrote: > > On Tue, 2005-11-08 at 08:15 +0100, Harald Dunkel wrote: > > > >>Hi folks, > >> > >>I would like to build 32bit and 64bit libraries within the > >>same Makefile.am. In the install directory tree the l

Re: building 32bit and 64bit libs with the same name

Hi Ralf, Ralf Corsepius wrote: > On Tue, 2005-11-08 at 08:15 +0100, Harald Dunkel wrote: > >>Hi folks, >> >>I would like to build 32bit and 64bit libraries within the >>same Makefile.am. In the install directory tree the libs >>should get the same name, but the 64bit library is supposed >>to be

Re: building 32bit and 64bit libs with the same name

On Tue, 2005-11-08 at 08:15 +0100, Harald Dunkel wrote: > Hi folks, > > I would like to build 32bit and 64bit libraries within the > same Makefile.am. In the install directory tree the libs > should get the same name, but the 64bit library is supposed > to be installed in ${exec_prefix}/lib64, of