Below is the result of your form. It was submitted by
([EMAIL PROTECTED]) on Wednesday, May 22, 2002 at 04:09:33
---
:: FREE Entry! FREE Membership! Don't know how long this GREAT offer will last, but
:don't miss your cha
Don Anderson <[EMAIL PROTECTED]> writes:
> I was of a libtool option:
>
>--moduleext=.jnilib
Hi,
I second that. I'm experimenting building Matlab MEX-files using
Libtool and run into the same problem. At present, my Makefile.am
looks as follows:
-
Dear all,
I had the following Makefile.am running generating a proper Makefile.in
with automake 1.4a and libtool 1.3c
UTILSRC = parser.cpp integrate.cpp
MUDSRC = init.cpp linear_solver.cpp mudfas.cpp nonlinear_solver.cpp \
poisson_boltzmann.cpp poisson.cpp prolon.cpp restrict.cpp
lib_LTLIBRAR
[EMAIL PROTECTED] wrote on May 16:
>
> Today's Topics:
>
>1. MacOSX and autoconf/automake/libtool (Erik de Castro Lopo)
>
> --__--__--
>
> Message: 1
> Date: Thu, 16 May 2002 14:27:26 +1000
> From: Erik de Castro Lopo <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: MacOS
ltmain.sh (GNU libtool) 1.4.2 (1.922.2.54 2001/09/11 03:33:37)
Hi,
I encountered a problem with Libtool libraries on HP-UX.
Consider the following (simplified) Makefile.am:
lib_LTLIBRARIES = libfoo.la libbar.la
libfoo_la_SOURCES = foo.c
libbar_la_SOURCES = bar.c
libbar_la_LDF
Ralph,
I would expect Libtool to translate "libfoo.la" to "libfoo.${ext}"
and to translate -lfoo into -lfoo, perhaps you should put "-lfoo"
in _LDFLAGS instead of libfoo.la.
IIRC, -lfoo -> -lfoo and libfoo.la -> libfoo.sl because sometimes
users one -lfoo, and sometimes users want libfoo.sl.
But
"Boehne, Robert" <[EMAIL PROTECTED]> writes:
Hi Robert,
> I would expect Libtool to translate "libfoo.la" to "libfoo.${ext}"
> and to translate -lfoo into -lfoo, perhaps you should put "-lfoo"
> in _LDFLAGS instead of libfoo.la.
But "-lfoo" is not sufficient when linking against a non-installed
