From owner-freebsd-questions@FreeBSD.ORG Thu Jun 25 23:12:53 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 354ED1065673 for ; Thu, 25 Jun 2009 23:12:53 +0000 (UTC) (envelope-from markus.hoenicka@mhoenicka.de) Received: from smtprelay08.ispgateway.de (smtprelay08.ispgateway.de [80.67.29.8]) by mx1.freebsd.org (Postfix) with ESMTP id E73688FC08 for ; Thu, 25 Jun 2009 23:12:52 +0000 (UTC) (envelope-from markus.hoenicka@mhoenicka.de) Received: from [93.135.207.242] (helo=yeti.mininet) by smtprelay08.ispgateway.de with esmtpa (Exim 4.68) (envelope-from ) id 1MJxoS-0003m7-LV for freebsd-questions@freebsd.org; Fri, 26 Jun 2009 00:53:00 +0200 X-Mailer: emacs 22.3.1 (via feedmail 8 I); VM 7.19 under Emacs 22.3.1 From: "Markus Hoenicka" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19012.105.500949.723890@yeti.mininet> Date: Fri, 26 Jun 2009 00:55:37 +0200 To: freebsd-questions@freebsd.org X-Df-Sender: 472582 Subject: xfburn fails with 'Undefined symbol "__malloc_lock"' X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2009 23:12:53 -0000 Hi, I've upgraded my laptop from 6.4 to 7.2-RELEASE. Essentially everything went fine, except that for some reason xfburn no longer works. If I install a package using "portupgrade -f -PP", I see the following at runtime: markus@yeti:/usr/home/markus# xfburn & [1] 47214 markus@yeti:/usr/home/markus# /libexec/ld-elf.so.1: /lib/libpthread.so.2: Undefined symbol "__malloc_lock" If I build xfburn in the ports tree, I get the following error at compile time: /usr/bin/ld: warning: libcam.so.3, needed by /usr/local/lib/libburn.so, may conflict with libcam.so.4 /lib/libpthread.so.2: undefined reference to `__malloc_lock' I assume that I somehow managed to botch the 6->7 upgrade, but would anyone know how to fix this particular problem? regards, Markus -- Markus Hoenicka markus.hoenicka@cats.de (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de