Directing to User-Installed Libraries

Lasse Kliemann <[email protected]>
Newsgroups gmane.lisp.scheme.bigloo
Message-ID <[email protected]>
Greetings, I'm having trouble directing Bigloo to use libraries
installed in non-standard locations. Say, I'd like Bigloo to use the
OpenSSL library installed in /home/snyder/openssl instead of that in
/lib64 or /usr/lib or whatever.

My first approach was using LD_RUN_PATH and LDFLAGS, the latter
containing -L/home/snyder/openssl -Xlinker -R/home/snyder/openssl.

This does the trick usually, but in Bigloo's case it wasn't enough since
some (or perhaps all, didn't check) of it's shared libraries
(libbigloo*so) were still linked against the system library. This could
be verified using ldd.

Studying the make output, I found that those libraries are linked using
Bigloo's library directory as rpath, so I put appropriate symlinks in
that place (say, if Bigloo is installed into /home/snyder/bigloo, I put
symlinks from /home/snyder/bigloo/lib to all the libraries in
/home/snyder/openssl/lib). This seems to be sufficient on some of my
systems, but on others even though libbigloo*so picks up the correct
library now, something is still wrong. Namely, my user-installed OpenSSL
does not have SSLv2 support. But it seems that when Bigloo is compiled,
it detects SSLv2 support and activates it. When I later try to build
my own Bigloo programs, I get that SSLv2_client_method is an undefined
symbol. Like I said, this happens on some systems (on Centos for
example) but not on others (Ubuntu for example), which of course may
have hundreds of different reasons.

Could anyone give me a hint how to proceed? How do you link Bigloo
against libraries in non-standard locations - and, in particular, tell
it to ignore the system-wide versions of those libraries?

Thanks a lot!

I'm using the latest stable, 4.1-a2.
signature.asc (application/pgp-signature, 835 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBAgAGBQJUx/yYAAoJEEKWo+CJA9AYTy8P/itGwqkkvIpE4EWiJ8cGzaD8
B3iIrrl/Jmai0zD3CuS6M4bY/153OAwHiPmUSQLnJScQW9pNOSp5CgIzQ3Zl3q6l
4/ADy7kMEEZGOSQHRCLQmMREsJA2uOfzU7OKMQ8lb+43BRflG6S9yqo19VpqucmH
ChQ90Qq8Xszmg5msQRUshLNcgtkxtJ4vs2u37H3ckaCm+4nWLgAg+TyQsNYkdA4B
s2gpJ4BZcyZecC5VsFUVuS8CQ6Wh3VRKY9NRmrGJj8KQMXsuQ8BeDYNFb8BYAc/t
PnIF6ti8YQql/iFW1nwFsV7/7U8lb80NFwaksdafWjLoXAhKL7UtlnA6YsMrkpMG
c7zzBDq+cUrVLR3E1PUKzOV7P7wkP3EJv70OHaaeOGVWfsn2Yjr12gxPeULrDc2h
LhapyTETdf81YA6/ZX3f6Y+/W4sBdtk9sdHepJAoUkzXS0uqOaBrDViIOkrHOMsg
V8Xv5bqh8J3RusguRc3yYlAD9nmS8aQNnZWtHnrymfeiZciPRirFESuo6YU00+BT
SOA9bu9z0fiXjzxUIA2Uq0/YZjqY+9lm7UeniBYd4pDuxaXt4HC6gsxhUC5eczmz
B7Fzu6hOTrUO98HYmm6A+SO5hcHP8E5NeD4SSpO2tAn8aUCnY7SS8u/NtJF48wva
gpcLnp0Vcv/30THvNlZh
=++C1
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.