Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Feb 2004 15:33:43 -0800
From:      Kris Kennaway <kris@obsecurity.org>
To:        Gerald Pfeifer <gerald@pfeifer.com>
Cc:        Kris Kennaway <kris@obsecurity.org>
Subject:   Re: cvs commit: ports/lang/gcc34 Makefile distinfo
Message-ID:  <20040219233343.GA20167@xor.obsecurity.org>
In-Reply-To: <Pine.BSF.4.58.0402192335590.47964@acrux.dbai.tuwien.ac.at>
References:  <200402192212.i1JMCUxx092480@repoman.freebsd.org> <20040219222006.GA19860@xor.obsecurity.org> <Pine.BSF.4.58.0402192335590.47964@acrux.dbai.tuwien.ac.at>

next in thread | previous in thread | raw e-mail | index | archive | help

--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--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040219233343.GA20167>