From owner-cvs-all@FreeBSD.ORG Thu Feb 19 14:45:34 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD0F716A4CE; Thu, 19 Feb 2004 14:45:34 -0800 (PST) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.131.111.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E19F43D1D; Thu, 19 Feb 2004 14:45:34 -0800 (PST) (envelope-from gerald@pfeifer.com) Received: from [128.131.111.60] (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id E9A1C13787; Thu, 19 Feb 2004 23:45:32 +0100 (CET) Date: Thu, 19 Feb 2004 23:45:39 +0100 (CET) From: Gerald Pfeifer To: Kris Kennaway In-Reply-To: <20040219222006.GA19860@xor.obsecurity.org> Message-ID: References: <200402192212.i1JMCUxx092480@repoman.freebsd.org> <20040219222006.GA19860@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-ports@FreeBSD.org cc: Gerald Pfeifer cc: cvs-all@FreeBSD.org cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/lang/gcc34 Makefile distinfo X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2004 22:45:34 -0000 On Thu, 19 Feb 2004, Kris Kennaway wrote: > Hmm, why is this port unbuildable on amd64? Is it because the > configure script expects FreeBSD/amd64 to identify itself as x86_64? Yes. > If so, this problem was solved last year by making GNU_CONFIGURE ports > use an up-to-date version of config.{guess,sub} from > /usr/ports/Templates, which correctly identify a FreeBSD/amd64 system. I believe this won't be sufficient, for GCC also has gcc/config.gcc. (Both bento and my tests on panther confirmed that the GCC port really does not build on x86_64.) In case of GCC, as soon as someone (and I had asked obrien twice already) fixes that upstream, the gcc33 and gcc34 ports will be fixed within a couple of days by my next update. This is also much better, because it allows developers to build CVS GCC without any FreeBSD-specific hacks. (In any case, shouldn't amd64-freebsd be renamed back to x86_64-freebsd, given Intel's announcement two days ago?) Gerald -- Gerald Pfeifer (Jerry) gerald@pfeifer.com http://www.pfeifer.com/gerald/