From owner-freebsd-current@FreeBSD.ORG Fri Aug 20 16:57:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E39D516A4CE for ; Fri, 20 Aug 2004 16:57:39 +0000 (GMT) Received: from www.citello.it (host170-131.pool80117.interbusiness.it [80.117.131.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 535E143D41 for ; Fri, 20 Aug 2004 16:57:39 +0000 (GMT) (envelope-from molter@tin.it) Received: from gattaccio.codalunga (ANice-205-1-6-27.w81-53.abo.wanadoo.fr [81.53.77.27]) by www.citello.it (Postfix) with ESMTP id 38FCC15ED; Fri, 20 Aug 2004 18:57:37 +0200 (CEST) Received: by gattaccio.codalunga (Postfix, from userid 1001) id C7E23C0E9; Fri, 20 Aug 2004 18:55:56 +0200 (CEST) Date: Fri, 20 Aug 2004 18:55:56 +0200 From: Marco Molteni To: Tim Kellers Message-Id: <20040820185556.7b39c24f.molter@tin.it> In-Reply-To: <41261E61.8050003@devel.njit.edu> References: <41261E61.8050003@devel.njit.edu> X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: kmail breakage? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Aug 2004 16:57:40 -0000 On Fri, 20 Aug 2004 11:53:05 -0400 Tim Kellers wrote: [..] > When I launch kmail from KDE, the message > "KDEInit could not launch 'kmail'" is returned in a dialogue box, > when I > launch > it from xterm, I get: > > kmail > /libexec/ld-elf.so.1: /usr/local/lib/libkabc.so.3: Undefined symbol > "_ZNSt24__default_alloc_templateILb1ELi0EE12_S_free_listE" [..] > I didn't see anything in /usr/ports/UPATING about this problem, nor You sure? 20040728: System compiler has been upgraded to GCC 3.4.2-pre. As with any major compiler upgrade, there are several issues to be aware of. GCC 3.4.x has broken C++ ABI compatibility with previous releases yet again and users will have to rebuild all their C++ programs with the new compiler. A new unit-at-a-time optimization mode, which is default in this compiler release, is more aggressive in removing unused static symbols. This is the likely cause of 'make buildworld' breakages with non-default CFLAGS where optimization level is set to -O2 or higher.