From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 15 15:06:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04A4316A4CE for ; Mon, 15 Mar 2004 15:06:06 -0800 (PST) Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9E0C43D2D for ; Mon, 15 Mar 2004 15:06:05 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (e3469efe6a175463096dc58ea27525ea@adsl-67-119-53-203.dsl.lsan03.pacbell.net [67.119.53.203])i2FN62uW013648; Mon, 15 Mar 2004 17:06:03 -0600 (CST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1569951BFB; Mon, 15 Mar 2004 15:06:02 -0800 (PST) Date: Mon, 15 Mar 2004 15:06:01 -0800 From: Kris Kennaway To: "James R. Van Artsalen" Message-ID: <20040315230601.GA31834@xor.obsecurity.org> References: <20040315212058.C63058@uriah.heep.sax.de> <40563051.3010209@jrv.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: <40563051.3010209@jrv.org> User-Agent: Mutt/1.4.2.1i cc: Joerg Wunsch cc: freebsd-amd64@freebsd.org cc: kris@obsecurity.org Subject: Re: [kris@obsecurity.org: [ports-amd64@FreeBSD.org: avr-gcc-3.3.2 failed on amd64 5]] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2004 23:06:06 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 15, 2004 at 04:38:09PM -0600, James R. Van Artsalen wrote: > >Since this is a stock GCC 3.3.2 where AMD64 is only used as the host > >system (--target=3Davr), and I can't imagine AMD64 is not yet supported > >by GCC, is there already any experience about what would be needed to > >configure a GCC on this arch? > > > >Kris' guess was it might require to be called x86_64, but perhaps some > >other maintainer already solved that problem, so I'm just trying to > >not reinvent the wheel. > >=20 > > > GCC needs to know what the host is in order to know how to calculate=20 > constant folding, and how to do other optimizations (think about=20 > cross-compiling on a 32-bit platform for a 64-target, doing constant=20 > folding etc). >=20 > The bug is in GCC's config.guess: this file doesn't recognize FreeBSD=20 > right. See this message for patch to config.guess: > http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2004-February/000722= .html >=20 > This may not be the only bug but it is a necessary start. config.{guess,sub} should be patched to recognize amd64 if you define GNU_CONFIGURE. Kris --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAVjbZWry0BWjoQKURAmeDAJ4uiQufDzZHq0w3B9LUwRyQNxYpBQCdG0GS IF6oGEw0YE8fvXnK4LfCyEM= =62ix -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1--