From owner-freebsd-gnome@FreeBSD.ORG Thu Apr 22 18:03:26 2010 Return-Path: Delivered-To: gnome@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80A35106566C for ; Thu, 22 Apr 2010 18:03:26 +0000 (UTC) (envelope-from dokas@oitsec.umn.edu) Received: from mail.oitsec.umn.edu (mail.oitsec.umn.edu [128.101.238.120]) by mx1.freebsd.org (Postfix) with ESMTP id 3F4BD8FC21 for ; Thu, 22 Apr 2010 18:03:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.oitsec.umn.edu (Postfix) with ESMTP id 898956D450 for ; Thu, 22 Apr 2010 13:03:25 -0500 (CDT) X-Virus-Scanned: amavisd-new at oitsec.umn.edu Received: from mail.oitsec.umn.edu ([127.0.0.1]) by localhost (mail.oitsec.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iq39MKMxN0P9 for ; Thu, 22 Apr 2010 13:03:24 -0500 (CDT) Received: from cdward.oitsec.umn.edu (cdward.oitsec.umn.edu [160.94.247.237]) by mail.oitsec.umn.edu (Postfix) with ESMTP id DD39B6D44E for ; Thu, 22 Apr 2010 13:03:23 -0500 (CDT) Message-ID: <4BD08F6B.7030507@oitsec.umn.edu> Date: Thu, 22 Apr 2010 13:03:23 -0500 From: Paul Dokas Organization: OIT Security & Assurance, University of Minnesota User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.9) Gecko/20100410 Thunderbird/3.0.4 MIME-Version: 1.0 To: gnome@FreeBSD.org X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: openssl problems X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Dokas List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Apr 2010 18:03:26 -0000 Is anyone else having problems with ports that depend on openssl? I'm seeing rather serious build issues that all seem to be linked back to the fact that there are two installed versions of openssl (one in the base and one from ports). The following PR is an example of what I'm seeing: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/145769 Except I'm getting this same error when attempting to build net-im/empathy. I'm also now unable to rebuild devel/subversion and database/evolution-data-server due to configure errors. Here's an example from the config.log when attempting to build subversion. The configure script attempts to find an installation of neon by attempting to compile the following program: /* confdefs.h */ #define PACKAGE_NAME "subversion" #define PACKAGE_TARNAME "subversion" #define PACKAGE_VERSION "1.6.11" #define PACKAGE_STRING "subversion 1.6.11" #define PACKAGE_BUGREPORT "http://subversion.tigris.org/" #define PACKAGE_URL "" #define SVN_NEON_0_26 1 #define SVN_NEON_0_27 1 #define SVN_NEON_0_28 1 /* end confdefs.h. */ #include #include int main() {ne_xml_create(); ne_decompress_destroy(NULL);} Here's the command line used to compile it and the resulting error: % cc -o conftest -O2 -pipe -fno-strict-aliasing -I/usr/local/include/neon -L/usr/locallib -L/usr/local/lib/db46 ./conftest.c -L/usr/local/lib -lneon -L/usr/local/lib -lintl -lz -lssl -lcrypto -lexpat -lneon /usr/local/lib/libneon.so: undefined reference to `SSL_SESSION_cmp' Given the -L options, I see that it is using /usr/local/lib/libssl.so. However, SSL_SESSION_cmp is not defined in /usr/local/lib/libssl.so, it's defined in /usr/lib/libssl.so. ldd confirms which libssl will be pulled in by libneon: % ldd /usr/local/lib/libneon.so /usr/local/lib/libneon.so: libintl.so.8 => /usr/local/lib/libintl.so.8 (0x281d1000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x28300000) libz.so.5 => /lib/libz.so.5 (0x281da000) libssl.so.7 => /usr/local/lib/libssl.so.7 (0x283f6000) libcrypto.so.7 => /usr/local/lib/libcrypto.so.7 (0x28443000) libexpat.so.6 => /usr/local/lib/libexpat.so.6 (0x285a4000) libc.so.7 => /lib/libc.so.7 (0x28091000) Now, I could rebuilt neon28 with "WITHOUT_OPENSSL", but this is hardly the only port that I'm having problems with and I don't want to pick through all of the gnome dependencies and fix the issues. How are the rest of you handling these errors? I suspect that I must have missed something like having to do portupgrade -fr openssl\* around the time that openssl-1.0.0 was imported. Or, should I just set WITH_OPENSSL_BASE=yes in /etc/make.conf and be done with it? Paul -- Paul Dokas dokas at oitsec.umn.edu ====================================================================== Don Juan Matus: "an enigma wrapped in mystery wrapped in a tortilla."