cvs commit: ports/lang/gcc34 Makefile distinfo

[Kris Kennaway]

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

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-all/attachments/20040219/a4364fca/attachment.bin