Date: Mon, 24 Nov 2003 01:29:00 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Akinori MUSHA <knu@iDaemons.org> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: ruby-1.8.1.p2 broken on amd64 Message-ID: <20031124092900.GA12109@xor.obsecurity.org> In-Reply-To: <86znemcf0m.knu@iDaemons.org> References: <20031124002433.GB6264@xor.obsecurity.org> <86znemcf0m.knu@iDaemons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 24, 2003 at 06:06:01PM +0900, Akinori MUSHA wrote: > Hi, >=20 > At Sun, 23 Nov 2003 16:24:33 -0800, > kkenn wrote: > > http://bento.freebsd.org/errorlogs/amd64-5-latest/ruby-1.8.1.p2.log > >=20 > > Can you please investigate ASAP? >=20 > Hmm, I'm a bit confused. The substitute config.guess/sub (in > ports/Template/, which came with a newer autoconf) seem to recognoze > "amd64" and replace it with "x86_64", and as we don't have such a > thing as "x86_64" available from a port, there is no other way than > hardcoding s/amd64/x86_64/ blah blah blah to make packaging > (pkg-plist) work. >=20 > Now, do you know what is the canonical architecture name for the amd64 > platform? Did we diverge from GNU by adopting amd64, or is GNU just > behind us? I checked the just released autoconf 2.58, but the > situation did not seem to have changed. I don't remember..someone on the amd64 list (peter or David) should know. Kris --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/wc9bWry0BWjoQKURAoQ6AJ4p8Vjs10SAK4J/y/cUR3EPxiAyoQCglbq6 d7yOgRq4q/PEKgLlE1omjDE= =E0vI -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031124092900.GA12109>