Hi,
On 1/2/2017 8:46 AM, c...@roberthairgrove.com wrote:
Makefile.am in the root directory looks like this:
ACLOCAL_AMFLAGS = -I m4
SUBDIRS = src
(not much can go wrong there). Here is the Makefile.am in the src
subdirectory:
lib_LTLIBRARIES = libargpp.la
libargpp_la_SOURCES =
On 02/06/2015 02:12 PM, Bob Friesenhahn wrote:
It is curious that there is more impact for the optimized builds.
Well, it's a constant 5s impact for both optimized and non-optimized -
except for v2.4.3 which looks odd.
Cheers,
--
Peter Johansson
On 05/26/2014 05:07 PM, Peter Johansson wrote:
Hm, there is nothing in my 'Makefile.in' that mentions --mode=finish.
Is there any reason for that or is it a automake bug?
I investigated this a bit further. 'libtool --mode=finish' is indeed
called and it calls 'ldconfig -n /usr/local/lib
) $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS)
--mode=install $(INSTALL) $(INSTALL_STRIP_FLAG) $$list2
'$(DESTDIR)$(libdir)'; \
$(LIBTOOL) $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=install
$(INSTALL) $(INSTALL_STRIP_FLAG) $$list2 $(DESTDIR)$(libdir); \
}
Cheers,
--
Peter Johansson
'/usr/local/lib' to make
the runtime linker aware of '/usr/local/lib'. Yet I need to do a
ldconfig manually every time I install something. Am I missing something
or doing something wrong? This is on RHEL6.
Cheers,
Peter
This is on RHEL6 and I've added
--
Peter Johansson
Hi libtoolers,
I'm trying to write a macro to test whether libfoo is available as a
shared library or only as a static `libfoo.a'. It seems like a thing
libtool is using all the time, so thought I could let libtool do the
heavy lifting here, but cannot figure out the correct syntax. Anyone
On 07/18/2013 02:54 AM, Dennis Clarke wrote:
CDPATH=${ZSH_VERSION+.}: cd . /usr/local/bin/bash
/usr/local/build/libtool-2.4.2_SunOS5.8_sparcv9.001/libltdl/config/missing --run aclocal-1.11 -I
libltdl/m4
/usr/local/build/libtool-2.4.2_SunOS5.8_sparcv9.001/libltdl/config/missing:
line 52:
On 07/18/2013 01:59 PM, Dennis Clarke wrote:
from the source tarball .. here is try number five :
mimas$ sx ../src/libtool-2.4.2.tar.gz
star: 1165 blocks + 0 bytes (total of 11929600 bytes = 11650.00k).
mimas$ mv libtool-2.4.2 libtool-2.4.2_SunOS5.8_sparcv9.005
mimas$ cd
;;
esac
--
Peter Johansson
___
https://lists.gnu.org/mailman/listinfo/libtool
On 3/18/13 4:03 PM, Satz Klauer wrote:
It is not a libtool-specific thingy, you have to use these linking options:
-Wl,-whole-archive -lyourlib.a -lyourlib2.a -Wl,-no-whole-archive
This includes your static libraries libyourlib1.a and libyourlib2.a
into the shared library. Please do not forget
../foo/libfoo.a -Wl,-no-whole-archive
/usr/bin/ld: unknown flag: -no-whole-archive
Cheers,
Peter
--
Peter Johansson
___
https://lists.gnu.org/mailman/listinfo/libtool
Hi Bob,
Thanks for your quick reply.
On 03/18/2013 04:41 AM, Bob Friesenhahn wrote:
It is not portable, safe, or advisable to link a shared library with a
static library. Due to this, libtool does not apply .a files while it
is linking a shared library. Usually it warns and provides advice
it into a solution. I'm aware this is
unlikely a libtool issue and apologize if anyone would consider this noise.
Any hint or suggestion for further investigation would be most appreciated.
Thanks,
--
Peter Johansson
link_test.sh
Description: Bourne shell script
Hello libtoolers,
I have a question how inter-library dependency is normally handled when
creating libraries (with libtool).
We use libtool to create a library yat. This library depends on several
other libraries: libbam, libz, libgsl, libgslcblas, and libm. We check
for these libraries
Hi libtoolers,
This patch fixes so help output is formatted similar with other macros
using AS_HELP_STRING. Also it outputs '[DIR]' as I suspect intended
rather than 'DIR'.
Attached diff is against libtool 2.4.2.
Cheers,
Peter
--- libltdl/m4/libtool.m4.orig 2011-10-17 20:17:05.0
On 1/8/12 2:27 AM, Werner LEMBERG wrote:
And another ping!
Werner
I've found this interesting mail:
http://lists.gnu.org/archive/html/libtool-patches/2011-08/msg0.html
Interestingly, there was no comment at all. So my question: Is this
the `right' approach? Will libtool
[adding automake @; replies can drop libtool @]
On 9/13/10 6:31 AM, Elvis Dowson wrote:
Elvis Dowson wrote:
I'm unable to build libtool as binary that includes both 32-bit and 64-bit
intel architecture on Mac OS X 10.6.4 using gcc-4.0.1, and get the
following error:
gcc-4.0: -E, -S,
Hello,
We use libtool to create a library and in the test suite we are trying
to link against this library statically. The problem is that this test
will obviously fail when no static library was created, i.e., only
shared library was created. IIUC, this might happen on some platforms
but
On 1/31/10 6:10 AM, Joakim Tjernlund wrote:
Ralf Wildenhuesralf.wildenh...@gmx.de wrote on 2010/01/31 08:38:38:
My problem with that change is that, the relinking and finish
really are information that some users need to know about.
If you don't --finish, then your libraries won't
19 matches
Mail list logo
