Date: Mon, 16 Feb 2004 22:28:41 +0100 (MET) From: Adriaan de Groot <adridg@sci.kun.nl> To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> Cc: amd64@FreeBSD.org Subject: Re: AMD64 and lang/gcc3x on -CURRENT Message-ID: <Pine.GSO.4.44.0402162226320.14531-100000@wn4.sci.kun.nl> In-Reply-To: <Pine.BSF.4.58.0402162037021.63111@acrux.dbai.tuwien.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Feb 2004, Gerald Pfeifer wrote: > *** Configuration amd64-portbld-freebsd5.2 not supported > Configure in /tmp/a/ports/lang/gcc33/work/build/gcc failed, exiting. > > and my gut tells me someone renamed x86_64 to amd64 somewhere without > making proper adjustment in upstream packages or something like that. >From things David and/or Peter have written I've gathered the following: 1) AMD didn't give the platform an official name till fairly late 2) Some folks chose amd64 3) Later the muttonheads at the FSF chose x86_64 > This is a heads up that I will shortly mark all affected GCC ports BROKEN, > unless someone steps forward and fixes this (not by hacking the port, but > by submitting proper patches upstream, if needed). I think hacking the port is the only way, since there's such a fundamental disagreement in what the platform is called (this same problem shows up in lots of software packages, BTW, like OpenAFS).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.44.0402162226320.14531-100000>