From owner-freebsd-ports@FreeBSD.ORG Tue Feb 24 12:25:11 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D01A416A4CE; Tue, 24 Feb 2004 12:25:11 -0800 (PST) Received: from mtaw6.prodigy.net (mtaw6.prodigy.net [64.164.98.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF7BA43D2F; Tue, 24 Feb 2004 12:25:11 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (9e6449fd26ffc1764f274d038c458c7a@adsl-67-119-53-203.dsl.lsan03.pacbell.net [67.119.53.203]) by mtaw6.prodigy.net (8.12.10/8.12.10) with ESMTP id i1OKOEDO002353; Tue, 24 Feb 2004 12:24:15 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6EF8B66CAF; Tue, 24 Feb 2004 12:25:10 -0800 (PST) Date: Tue, 24 Feb 2004 12:25:10 -0800 From: Kris Kennaway To: Lev Serebryakov Message-ID: <20040224202510.GA53487@xor.obsecurity.org> References: <5744325.20040224212955@serebryakov.spb.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline In-Reply-To: <5744325.20040224212955@serebryakov.spb.ru> User-Agent: Mutt/1.4.1i cc: ports@FreeBSD.org Subject: Re: `gcc/config.gcc' and amd64? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 20:25:11 -0000 --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 24, 2004 at 09:29:55PM +0300, Lev Serebryakov wrote: > Hello, ports! How are you? >=20 > Every gcc3x port could not be build on amd64 bcause `gcc/config.gcc' > knows nothing about `amd64' platform. Ports system replaces > `config.sub', `config.guess' with new versions now. But where could > new config.gcc be taken? We should to fix this problem, IMHO... When I asked about this a few days ago I was told that it would be addressed in the gcc repository in the near future. Kris --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAO7MmWry0BWjoQKURAmqTAKD7tR1B9fiwZbQTDNq0xDdUMBghzQCg/crT USrPwgoKxZoHxGOhKu4xrtA= =n8cR -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA--