From owner-freebsd-ports@FreeBSD.ORG Mon Sep 20 20:58:18 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C6791065670 for ; Mon, 20 Sep 2010 20:58:18 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id C6EC88FC15 for ; Mon, 20 Sep 2010 20:58:17 +0000 (UTC) X-Virus-Scanned: amavisd-new at BSDLabs AB Message-ID: <4C97CAE4.2060108@intersonic.se> Date: Mon, 20 Sep 2010 22:58:12 +0200 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.8) Gecko/20100818 Thunderbird/3.1.2 MIME-Version: 1.0 To: olli hauer References: <4C95ABA6.1020607@intersonic.se> <4C979C6E.3090006@gmx.de> In-Reply-To: <4C979C6E.3090006@gmx.de> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: update bacula-server 5.0.2 -> 5.0.3, Undefined symbol "ASN1_INTEGER_it X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 20:58:18 -0000 On 09/20/10 19:39, olli hauer wrote: > On 2010-09-19 08:20, Per olof Ljungmark wrote: >> FreeBSD 7.3-STABLE #0: Tue Sep 7 22:46:59 CEST 2010 >> peo@candyman.i.inter-sonic.com:/usr/obj/usr/src/sys/GENERIC amd64 >> >> Portupgrade of bacula-server 5.0.2 -> 5.0.3 >> >> Starting bacula_fd. >> /libexec/ld-elf.so.1: /usr/local/lib/libbac.so.5: Undefined symbol >> "ASN1_INTEGER_it" >> Starting bacula_sd. >> Starting bacula_dir. >> >> If one deselects "OPENSSL" and recompile bacula-fd will start without >> complaints. >> >> Is this a known issue with 5.0.3? > > No, can you provide me some more details. > > First make sure if you have both bacula-server and bacula-client installed > on the same machine both are build with(out) ssl support. > > Both ports install libs with the same name to the same place, but if the > client is build/installed first "with SSL support", and then the server > without SSL support you can see exact the described issue. > A-ha. That must be it. I cannot recall why or when but this is what I must have done. Sorry for the noise. -- per