Hi,
I'm using libtool version 1.5.22 within a GNU autotools framework. I've
just been trying to build a library on hppa2.0-hp-hpux10.20 containing
source files in both Fortran and C and using the HP /opt/ansic/bin/cc
and /opt/fortran/bin/fort77 compilers
The configure stage works fine:
CC=/opt/a
Hello Ralf,
On Wed, 2006-08-23 at 14:04 +0200, Ralf Wildenhues wrote:
> Hello Steve,
>
> * Steve Edwards wrote on Wed, Aug 23, 2006 at 01:54:56PM CEST:
> > The configure stage works fine:
> >
> > CC=/opt/ansic/bin/cc F77=fort77 ./configure
>
> Please use
>
On Wed, 2006-08-23 at 15:29 +0200, Ralf Wildenhues wrote:
> Automake has some support for preprocessed Fortran 77. Could you try
> whether that is sufficient for you, and if not, please describe what is
> missing (I am trying to whip up Fortran support a bit at the moment...)?
> Please see the Au
Hi,
I've been using libtool quite happily for some time but have just started
looking at packaging libraries for x86_64 systems. I'm trying to find out what
the recommended method is for installation of x86_64 64bit libraries.
Most of the systems I'm targeting are Fedora which expect 64bit libr
Hi,
I just ran into a small problem using libtool to build DLLs on mingw.
A library package had just been updated to libtool 2.2.6 and DLLs were
no longer being built - only the static library.
libtool reported that:
"undefined symbols not allowed in $host shared libraries"
however I knew the
> > I fixed the problem by adding an explicit "-no-undefined" to the
> > libtool link command - is this considered to be the correct fix or
> > am I missing something obvious?
>
> This is correct.
>
> If you use AM_PROG_LIBTOOL or AC_PROG_LIBTOOL in your configure.ac
> script, add AC_LIBTOOL_WIN3
Hi,
This is just a request to find out if anyone out there has tried using
libtool to build Fortran DLLs under mingw32?
We had some Fortran code built as a shared library that could be loaded
into Matlab quite happily on Linux systems and also used as a
conventional library linked against by seve
On Thu, 8 Jan 2009 19:25:03 +0100
Ralf Wildenhues wrote:
> Hello Steve,
Hello and thanks for the reply.
> * Steve Edwards wrote on Thu, Jan 08, 2009 at 05:51:27PM CET:
> > This is just a request to find out if anyone out there has tried
> > using libtool to build Fortran
Hi,
I ran into a slight difficulty with shared libraries on IBM AIX
systems using libtool 2.2.6 (I'm not even sure if this is really
where I should be asking questions about this)
If I have a main Fortran routine containing a common block and call a
Fortran subroutine in a shared library also ref
On Sat, 9 May 2009 20:01:18 +0200
Ralf Wildenhues wrote:
> Hi Steve,
>
> * Steve Edwards wrote on Sat, May 09, 2009 at 02:11:11PM CEST:
> [ -brtl ]
> > Should libtool be adding this flag, or is this something I should
> > be manually adding via AM_LDFLAGS? Every ot
I have just run into problems trying to use libtool on a
rs6000-ibm-aix4.3.2.0 system to build a library written in Fortran with
the IBM compiler xlf/xlf90.
There is an immediate compilation failure stating:
xlf90: 1501-210 command option P contains an incorrect subargument
libtool appears to in
I'm trying to port an existing library to use libtool (version 1.4.3)
and have run into a problem with long argument lists on an
rs6000-ibm-aix4.3.2.0 system.
The limiatation is with the AIX linker.
The original method used to build the library, built individual sections
and progressively added th
Just for the information of the libtool maintainers I thought you might
be interested in a few 'features' of the hpux system.
I have just been trying libtool 1.5 on this architecture using the
native hp tools. I am using the HP ANSI C compiler and HP FORTRAN/9000.
When trying to build shared li
On 2003.08.18 06:52 Schleicher Ralph (LLI) wrote:
Steve Edwards writes:
> (Warning) At least one PA 2.0 object file (conftest.o) was detected.
> The linked output may not run on a PA 1.x system.
Add
LDOPTS='+vnocompatwarnings +s'
export LDOPTS
to your .profile file.
Thank
14 matches
Mail list logo
