[I replied to Werner without copying the list by mistake. Here is the
reply.]
On 03/23/2012 09:50 AM, Werner LEMBERG wrote:
I get this link command together with the error message.
/bin/sh ../libtool \
--tag=CXX \
--mode=link \
g++ -pipe -O2
Please add a --debug after the ../libt
>> I get this link command together with the error message.
>>
>> /bin/sh ../libtool \
>>--tag=CXX \
>>--mode=link \
>>g++ -pipe -O2
>
> Please add a --debug after the ../libtool and send me the log of
> stderr and stdout.
Attached.
> There are no static versions of any of the system
On 03/23/2012 06:40 AM, Christian Egli wrote:
libtool --mode=execute -dlopen ../liblouis/liblouis.la -n python $(TEST_SCRIPT)
What is the drawback of just setting LD_LIBRARY_PATH in
TESTS_ENVIRONMENT?
Not all systems use LD_LIBRARY_PATH. You can find the variable that
libtool sets by checkin
Hi,
On 03/23/2012 07:58 AM, Werner LEMBERG wrote:
I have a problem with libtool on Mac OS X Lion, trying to link
statically to (a statically compiled version of) Qt. Saying
make LDFLAGS="-all-static" V=1
I get this link command together with the error message.
/bin/sh ../libtool \
--t
[libtool 2.4.2]
Folks,
I have a problem with libtool on Mac OS X Lion, trying to link
statically to (a statically compiled version of) Qt. Saying
make LDFLAGS="-all-static" V=1
I get this link command together with the error message.
/bin/sh ../libtool \
--tag=CXX \
--mode=link \
g+
Hi all
I co-maintain a project where we build a library, a bunch of auxiliary
tools based on that library and language bindings to this library. The
test suite runs a bunch of shell scripts and Python code (using the
bindings).
Now when running the test suite the shell scripts just invoke one of