Re: [Vala] [ANNOUNCE] Vala 0.9.6 - Compiler for the GObject type system
- From: Jan Hudec <bulb ucw cz>
- To: JM <interflug1 gmx net>
- Cc: vala-list gnome org
- Subject: Re: [Vala] [ANNOUNCE] Vala 0.9.6 - Compiler for the GObject type system
- Date: Sat, 21 Aug 2010 08:37:29 +0200
On Wed, Aug 18, 2010 at 23:11:26 +0200, JM wrote:
Is it really the solution to manually set LD_LIBRARY_PATH every time?
This is not recommended from various sources (e.g.
http://linuxmafia.com/faq/Admin/ld-lib-path.html)
It's not recommended for a reason. You really shouldn't.
Also this wasn't necessary in the past. So why now?
First, did you run ldconfig after installing vala (you have to do that as
root)? It might be that you do actually have /usr/local/lib in
/etc/ld.so.conf, but the dynamic linker does not list the directories at
start-up of every program, relying on having the listing in /etc/ld.so.cache.
Since new vala version installed new library, you have to update that file by
running ldconfig.
I have default /etc/ld.so.conf (in Debian) and it *DOES* contain
/usr/local/lib, so running ldconfig might help.
If it does not than I suppose autotools stopped generating rpath for some
reason. You can force it by adding it to LDFLAGS (at configure time). I am
not sure whether you need to pass it as "-rpath=/usr/local/lib" or
"-Wl,-rpath=/usr/local/lib" though. It is basically equivalent to defining
LD_LIBRARY_PATH, but applies to the binary rather than to a session.
--
Jan 'Bulb' Hudec <bulb ucw cz>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]