From owner-cvs-ports@FreeBSD.ORG Thu Feb 19 15:33:45 2004 Return-Path: Delivered-To: cvs-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F8C216A4CE; Thu, 19 Feb 2004 15:33:45 -0800 (PST) Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56B6743D1F; Thu, 19 Feb 2004 15:33:45 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adb7108f2b75ce5a1c3691f6db0bd029@adsl-63-207-60-37.dsl.lsan03.pacbell.net [63.207.60.37])i1JNXia3016722; Thu, 19 Feb 2004 17:33:44 -0600 (CST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 94B4166CAF; Thu, 19 Feb 2004 15:33:43 -0800 (PST) Date: Thu, 19 Feb 2004 15:33:43 -0800 From: Kris Kennaway To: Gerald Pfeifer Message-ID: <20040219233343.GA20167@xor.obsecurity.org> References: <200402192212.i1JMCUxx092480@repoman.freebsd.org> <20040219222006.GA19860@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: cvs-ports@FreeBSD.org cc: ports-committers@FreeBSD.org cc: Gerald Pfeifer cc: cvs-all@FreeBSD.org cc: Kris Kennaway Subject: Re: cvs commit: ports/lang/gcc34 Makefile distinfo X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2004 23:33:45 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 19, 2004 at 11:45:39PM +0100, Gerald Pfeifer wrote: > 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? >=20 > Yes. >=20 > > 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. >=20 > 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.) >=20 > 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. OK, thanks. > (In any case, shouldn't amd64-freebsd be renamed back to x86_64-freebsd, > given Intel's announcement two days ago?) We still have a freebsd-ia32 mailing list, despite the non-exclusivity of Intel in that processor architecture. Kris --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFANUfXWry0BWjoQKURAqYIAKD+YRhiA6VhW13OgNPoiBrKvo6X3QCg9yfd 3Pk8PvFf18be+EVehdGXJPc= =EXG+ -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--