From owner-freebsd-current@FreeBSD.ORG Mon Aug 17 14:51:17 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A2232106568B; Mon, 17 Aug 2009 14:51:17 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 835158FC41; Mon, 17 Aug 2009 14:51:17 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id DFD898C078; Mon, 17 Aug 2009 09:36:02 -0500 (CDT) Date: Mon, 17 Aug 2009 09:36:02 -0500 From: Mark Linimon To: Anton Shterenlikht Message-ID: <20090817143602.GB2365@lonesome.com> References: <20090817135752.GA73485@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090817135752.GA73485@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.18 (2008-05-17) X-Mailman-Approved-At: Mon, 17 Aug 2009 15:14:53 +0000 Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org, freebsd-ia64@FreeBSD.org Subject: Re: ports lang/gcc4x fail to build on ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 17 Aug 2009 14:51:17 -0000 On Mon, Aug 17, 2009 at 02:57:52PM +0100, Anton Shterenlikht wrote: > Ports lang/gcc43, 44 and 45 fail to build on 8.0-beta2 ia64: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40959 > > I know they build fine on 6.4-stable alpha, but what about sparc64? > amd64? mips? You can check things like this using the Ports Monitoring tool: http://portsmon.freebsd.org/portoverview.py?category=lang&portname=gcc4&wildcard=yes According to that, for 8.0: - gcc4* are set to "not for ia64". From a commit log for gcc43/Makefile: Add ia64 to NOT_FOR_ARCHS. This has been broken for ages, it is not clear whether it is our kernel/userland, the hardware, or something else at fault and nobody on our side nor upstream seems to have any interest. - previous versions of gcc43 built everywhere; the latest version has not yet been tried on amd64 or sparc64, but builds on i386. - previous versions of gcc44 built everywhere; the latest version has not yet been tried on amd64 or sparc64, but builds on i386. - previous versions of gcc45 built everywhere; the latest version has not yet been tried on amd64 or sparc64, but builds on i386. The package building cluster is currently only set up to try builds on amd64, i386, and sparc64. Although we have some ia64 machines, the last time I tried to upgrade them I had trouble. We do not yet have any arm, mips, or powerpc machines. Our alphas have been deinstalled (sorry), after the alpha src code had fallen too far behind the main 3 archs, and no one was keeping it up. Unless a developer with specific interest in ia64 steps up to help, you may be out of luck. Sorry. mcl * yes, I know that portsmon is throwing 'database not connected' errors, but don't have a fix for it yet. It only seems to affect the query for 'show me uploaded packages', and even then not all the time.