I'm working on a library which may need to link with the standard libraries (I
assume since -nostdlib would seem to indicate that it's *not to* link with
standard libraries). I say this because of discussions I've come across making
mention that using "-nostdlib" has adverse side effects with p
> -Original Message-
> From: Bob Friesenhahn [mailto:bfrie...@simple.dallas.tx.us]
> Sent: Tuesday, April 07, 2015 7:26 AM
> To: Andy Falanga (afalanga)
> Cc: libtool@gnu.org
> Subject: Re: libtool is not wanting to play nicely with cross compiler
>
> On Mon,
I'm working on compiling some code for an ARM processor on a Xilinx board. I
did not do the work of configuring the cross compiler and so am ignorant about
some parts of this process.
I've finally gotten my configure script to complete and was running the main
compilation when I ran into this
HI,
I receive much of the mail from libtool in the form of "bounces". Ordinarily,
I wouldn't worry but this caused the daemon/management process for
autom...@gnu.org get irritated. I'm wondering, however, why I'm having this
type of trouble. The e-mail address I provided is very much legit.
> -Original Message-
> From: Peter Johansson [mailto:troj...@gmail.com]
> Sent: Thursday, March 05, 2015 6:46 PM
> To: Andy Falanga (afalanga); libtool@gnu.org
> Subject: Re: how to make libtool link with static system libraries
> instead of dynamic
>
> On 0
I am wondering how I would make libtool link with static versions of already
installed libraries instead of the dynamic ones. I have something like this in
Makefile.am
pyexec_LTLIBRARIES = mylib.la
mylib_la_LDFLAGS = -Wl,-Bstatic
mylib_la_LIBADD = -lz -lrt -lboost_python
The problem is, a
I'm working on converting a home-grown makefile mess to using the autotools
(the GNU build system) for building and deploying our shared library. The
shared library exists in two forms: a traditional C++ *.so and a python module
which is also a *.so but is, obviously, consumable by python only.
