Date: Thu, 19 Feb 2004 23:45:39 +0100 (CET) From: Gerald Pfeifer <gerald@pfeifer.com> To: Kris Kennaway <kris@obsecurity.org> Cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/lang/gcc34 Makefile distinfo Message-ID: <Pine.BSF.4.58.0402192335590.47964@acrux.dbai.tuwien.ac.at> In-Reply-To: <20040219222006.GA19860@xor.obsecurity.org> References: <200402192212.i1JMCUxx092480@repoman.freebsd.org> <20040219222006.GA19860@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.58.0402192335590.47964>