From owner-freebsd-ports@FreeBSD.ORG Tue Sep 21 00:44:31 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 32AB9106564A for ; Tue, 21 Sep 2010 00:44:31 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.50.215]) by mx1.freebsd.org (Postfix) with ESMTP id 0EB958FC12 for ; Tue, 21 Sep 2010 00:44:30 +0000 (UTC) Received: by syn.atarininja.org (Postfix, from userid 1001) id C6E9B5C39; Mon, 20 Sep 2010 20:24:43 -0400 (EDT) Date: Mon, 20 Sep 2010 20:24:43 -0400 From: Wesley Shields To: olli hauer Message-ID: <20100921002443.GA25094@atarininja.org> References: <4C95ABA6.1020607@intersonic.se> <4C979C6E.3090006@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C979C6E.3090006@gmx.de> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Per olof Ljungmark , 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: Tue, 21 Sep 2010 00:44:31 -0000 On Mon, Sep 20, 2010 at 07:39:58PM +0200, 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. Shouldn't the two ports register CONFLICTS then, thus making it (normally) impossible for both to be installed on the same host? -- WXS