From owner-freebsd-current@FreeBSD.ORG Thu Aug 5 05:56:30 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 DF99F16A4CE for ; Thu, 5 Aug 2004 05:56:30 +0000 (GMT) Received: from users.altadena.net (users.altadena.net [207.151.161.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCE7843D41 for ; Thu, 5 Aug 2004 05:56:30 +0000 (GMT) (envelope-from pete@users.altadena.net) Received: from pete by users.altadena.net with local (Exim 4.40) id 1BsbEs-000Bxn-Gn for current@freebsd.org; Wed, 04 Aug 2004 22:56:30 -0700 Date: Wed, 4 Aug 2004 22:56:30 -0700 From: Pete Carah To: current@freebsd.org Message-ID: <20040805055630.GA45424@users.altadena.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: Pete Carah Subject: Ports broken by compiler upgrade 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: Thu, 05 Aug 2004 05:56:31 -0000 Many ports that compile in C++ are broken by the recent compiler upgrade; the packages distribution hasn't caught up *at all* either. I know part of the reason is that some of the affected ports don't compile at all with the new compiler (by trying). I presume that the converse probably holds too; once the ports are fixed then the resulting packages probably won't work on a current dated before last week. It might be a good idea to keep an older package directory around for a while for those not-quite- so-adventurous types... Two examples, artsd and aspell both abort instantly with undefined symbols; either the name-mangling has changed or one or another library has changed, or both. Aspell is needed for pan2 to work and artsd is obvious to those who like sound in kde. Neither compiles completely as-is (artsd itself actually does but several needed "extension" modules don't, leaving things less than useful). This may be old news but... It is not quite enough to make sure that the main tree compiles with a newly-committed compiler - some of the ports are so widely used (e.g. XFree86) that they could be considered to be fairly essential. I don't need any replies to this; it is just a note to whomever it may concern (lots of port-maintainers, and the compiler folk(s))... It does leave my laptop less than useful; I can back up to last week easily enough but that is lots of trouble (and don't say to use 4.x in the laptop since it (like many modern laptops) depends on several drivers that are only in current, like cardbus.) -- Pete