Subject: Re: [ecasound] Gteca errors
From: Kai Vehmanen (k_AT_eca.cx)
Date: Mon Oct 15 2001 - 00:29:24 EEST
On Sun, 14 Oct 2001, Kai Vehmanen wrote:
> You can get around this by explicitly specifying -rpath when compiling the
> binaries. This is why this problem doesn't appear with ecasound itself,
> ecaplay, etc... But for some reason automake/autoconf/libtool system adds
> rpath only in some circumstances. I still haven't figured out what
> the exact logic is behind it. Of course one could hack the makefiles and
> bypass libtool, but this would without doubt break compiling on some
I investigated this a bit further and for pyecasound the situation seems
hopeless. Libtool just won't accept the -rpath even if manually given on
the command-line. This means that pyecasound only works if...
a) both libecasound and libkvutils are in a directory
listed in /etc/ld.so.conf
b) there are no newer versions of libecasound or libkvutils
with the same major number in any directory mentioned
earlier in /etc/ld.so.conf ...
Why do I again have the feeling that I've wasted few good hours of my life
to these stupid tools that should be helping me. ArrrghgHHh1! Oh well, I
guess it's time to rewrite ecasound/pyecasound/Makefile.am - this time
For ecawave and ecamegapedal I managed to fix this by adding
an explicit -rpath entry to their Makefiles...
PS -rpath is a linker option, which is needed when you need to
compile programs against libraries not specified /etc/ld.so.conf.
As only root has access to /etc/ld.so.conf (and for many
other reasons), -rpath has many uses.
-- http://www.eca.cx Audio software for Linux!
-- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request_AT_wakkanet.fi>.
This archive was generated by hypermail 2b28 : Mon Oct 15 2001 - 00:26:20 EEST