From owner-freebsd-stable@FreeBSD.ORG Tue Mar 4 12:05:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD719106566B for ; Tue, 4 Mar 2008 12:05:23 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id 629DB8FC1C for ; Tue, 4 Mar 2008 12:05:23 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so2714664uge.37 for ; Tue, 04 Mar 2008 04:05:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=tbbjeTqPYYBWenYROtmTTLf/Wj/NXJs9Ur3Q/WYG6iM=; b=M/ugpsVLawiRkK6CLAqzFfVR02W935gAcSlz1/aWnxDU0vItHEwkPCDvqPJFghSO1f+tzhlQbIN4uBr2k3eMq2erJk04hMnuE9Ii6z7uCpoaU9cnCp00ZiN9NVykukplk/NXevPV5stOK2QDiBhDB4r8SKuzolGI+/oM9DBmjwQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Gq4OMShuwiQI2aJdH5JmePNYprNhvIUBGniX1LH+qw0bgY+SoynH+QTzDNWFPY8h40KhdaQ/YqW4+U+qIenNJgFXpJfHejMzeaX/fmqmdYP+F7pmwLpR0EZBkNMbfEvLPRXDO+a3I2sO+4QSvEksBTsaavrqRrO2AG+5qOjqAKU= Received: by 10.67.98.15 with SMTP id a15mr5538193ugm.69.1204632322153; Tue, 04 Mar 2008 04:05:22 -0800 (PST) Received: by 10.66.219.18 with HTTP; Tue, 4 Mar 2008 04:05:22 -0800 (PST) Message-ID: <3aaaa3a0803040405l74135ea9va2ebfbe6ee0b5fc1@mail.gmail.com> Date: Tue, 4 Mar 2008 12:05:22 +0000 From: Chris To: "FreeBSD Stable" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: linked ssl libraries to binary X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2008 12:05:24 -0000 I have a freebsd 6.3 server and a freebsd 7.0 server, I have a binary I run of the freebsd 7 box but has recently been crashing, the binary in question is ezbounce. It was previously running for weeks no problems at all and then during the past 2 weeks or so its had problems. Like many shell programs it has a configure script and you then run make or gmake to compile the binary. On freebsd 6 it picks up /usr/local ssl libaries no problem and in fact uses them without even haveing to specify the directory it auto detects them over the base ssl. On freebsd 7 it uses the base libraries even when telling it to search in /usr/local. So I then decided to move the binary I compiled on freebsd 6 over to the freebsd 7 box and when I ran ldd on the binary to my surprise it is using the base libraries on freebsd 7. ldd on binary on freebsd 6 libssl.so.5 => /usr/local/lib/libssl.so.5 (0x48102000) libcrypto.so.5 => /usr/local/lib/libcrypto.so.5 (0x48143000) libcrypt.so.3 => /lib/libcrypt.so.3 (0x4829f000) libboost_iostreams.so => /usr/local/lib/libboost_iostreams.so (0x482b8000) libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x482c0000) libm.so.4 => /lib/libm.so.4 (0x48396000) libpthread.so.2 => /lib/libpthread.so.2 (0x483ac000) libc.so.6 => /lib/libc.so.6 (0x483d3000) libbz2.so.2 => /usr/lib/libbz2.so.2 (0x484cb000) libz.so.3 => /lib/libz.so.3 (0x484dc000) ldd on same binary on freebsd 7 libssl.so.5 => /usr/lib/libssl.so.5 (0x28101000) libcrypto.so.5 => /lib/libcrypto.so.5 (0x28142000) libcrypt.so.3 => /usr/local/lib/compat/libcrypt.so.3 (0x2829a000) libboost_iostreams.so => /usr/local/lib/libboost_iostreams.so (0x282b2000) libstdc++.so.5 => /usr/local/lib/compat/libstdc++.so.5 (0x282bd000) libm.so.4 => /usr/local/lib/compat/libm.so.4 (0x28388000) libpthread.so.2 => /usr/local/lib/compat/libpthread.so.2 (0x2839e000) libc.so.6 => /usr/local/lib/compat/libc.so.6 (0x283c3000) libc.so.7 => /lib/libc.so.7 (0x284a9000) libbz2.so.3 => /usr/lib/libbz2.so.3 (0x285a4000) libz.so.4 => /lib/libz.so.4 (0x285b4000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x285c6000) libm.so.5 => /lib/libm.so.5 (0x286ba000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x286cf000) libthr.so.3 => /lib/libthr.so.3 (0x286da000) The binary doesnt run on the freebsd 7 either it coredumps even tho I have compat6x installed, typically in the past I have had no problems at all using binaries compiled on old freebsd versions on newer versions I just had to install the appropriate compat package. Here is the ldd when compiled on the freebsd 7 box libssl.so.5 => /usr/lib/libssl.so.5 (0x2810f000) libcrypto.so.5 => /lib/libcrypto.so.5 (0x28150000) libcrypt.so.4 => /lib/libcrypt.so.4 (0x282a8000) libboost_iostreams.so => /usr/local/lib/libboost_iostreams.so (0x282c1000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x282cc000) libm.so.5 => /lib/libm.so.5 (0x283c0000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x283d5000) libthr.so.3 => /lib/libthr.so.3 (0x283e0000) libc.so.7 => /lib/libc.so.7 (0x283f3000) libbz2.so.3 => /usr/lib/libbz2.so.3 (0x284ee000) libz.so.4 => /lib/libz.so.4 (0x284fe000) Is the output for the ssl libraries skewed because both the local filenames and the base filenames are the same? as there is a /usr/local/lib/libssl.so.5 and a /usr/lib/libssl.so.5. Or does this mean that it really is linked against the base libraries as I am wondering how that is possible when the same binary is linked against different libraries on a different machine. Chris