On Fri, Dec 06, 2002, Vinod Kutty wrote: > [...wget...] > . > Looking for SSL libraries in /usr/local/ssl > checking for includes... found > checking for RSA_new in -lcrypto... yes > checking for SSL_new in -lssl... yes > checking whether SSL libs are resolved at runtime... yes > Compiling in support for SSL in /usr/local/ssl > checking for md5_calc in -lmd5... yes > checking whether NLS is requested... no > [...] > /opt/src/openpkg/src.rpm $ ldd /opt/opkg/bin/wget > libmd5.so.1 => /lib/libmd5.so.1 > libssl.so.0.9.6 => /usr/local/ssl/lib/libssl.so.0.9.6 > libcrypto.so.0.9.6 => /usr/local/ssl/lib/libcrypto.so.0.9.6 > libdl.so.1 => /lib/libdl.so.1 > libsocket.so.1 => /lib/libsocket.so.1 > libnsl.so.1 => /lib/libnsl.so.1 > libc.so.1 => /lib/libc.so.1 > libmp.so.2 => /lib/libmp.so.2 > /usr/platform/SUNW,Sun-Fire-280R/lib/libmd5_psr.so.1 > /usr/platform/SUNW,Sun-Fire-280R/lib/libc_psr.so.1 > /opt/src/openpkg/src.rpm $ > [...]
> So, for some reason the build of wget picked up ssl libs under > /usr/local/lib, which isn't causing problems at the moment, but will in > the future. Yes, good catch. Until now we built our wget without SSL, but unfortunately its Autoconf procedure tries to be smart and searches for OpenSSL in some "standard" paths _by default_. Hence accidently it picked up your /usr/local/ stuff. This is now fixed in OpenPKG-CURRENT, see http://cvs.openpkg.org/chngview?cn=5779 > I also noticed that everything under /opt/opkg/lib > is static (i.e. no dynamically linked libs). Correct. See FAQ: http://www.openpkg.org/faq.html#no-shlib > At the moment /usr/local holds non-openpkg based apps another user had > installed, and I don't want to get rid of it because I'm trying to setup a > fully independent openpkg installation before migrating users away from > what's in /usr/local. As a last resort, I might be able to set this up on > a separate machine without /usr/local, just to do builds. > > I know I could probably tweak the wget and/or openssl installations, but > in general, I'd like to avoid spending the time examining each src.rpm > build. > > Can I rely on the src.rpm files at ftp.openpkg.org passing the correct > options to config/make process so that there are no refs to directories > outside the openpkg root? Or do I have to examine each one when I build ? In general you cannot _rely_ on anything on earth until you did it yourself ;-) We try hard to make OpenPKG and all its packages as self-contained as possible. For instance we even force a sane environment under build-time to make sure no LD_LIBRARY_PATH and PATH stuff is picked up, we force the usage of static libraries to make sure that no wrong DSOs are picked up accidently (think about two instances on the same machine), etc. But all this cannot mean that we can be sure that the result is self-contained, because as the wget example clearly shows, some vendor procedures try to be smarted than appreciated. And until this someone has catched manually we cannot do anything more technically here. > Also, in this particular case, any suggestions on the best way to proceed? > This probably involves the whole can of worms regarding static vs. dynamic > linking ... The best way to proceed is to install as usual and after all your installing, perform an "ldd" on /opt/opkg/bin/* and /opt/opkg/sbin/* and watch for those non-standard things packages have picked up. Then send us these results and we'll make sure that this is fixed for the forthcoming OpenPKG releases. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
