Date: Mon, 24 Nov 2003 04:50:43 -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: <20031124125043.GA16016@xor.obsecurity.org> In-Reply-To: <86wu9qc4t1.knu@iDaemons.org> References: <20031124002433.GB6264@xor.obsecurity.org> <86znemcf0m.knu@iDaemons.org> <20031124092900.GA12109@xor.obsecurity.org> <20031124114750.GA60860@dragon.nuxi.com> <86wu9qc4t1.knu@iDaemons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--AhhlLboLdkugWU4S
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Nov 24, 2003 at 09:46:34PM +0900, Akinori MUSHA wrote:
> At Mon, 24 Nov 2003 03:47:50 -0800,
> o`brien wrote:
> > The bug is in Mk/bsd.ruby.mk. It is bogusly clearing CONFIGURE_TARGET.
> > At least for passing the --target GNU tuple to GNU autoconf. GNU
> > software has always used a 3-TUPPLE: cpu, vender, OS. While <cpu>-<os>
> > might be the proper tuple for Ruby itself, it isn't for GNU autoconf.
> > Modern versions of GNU autoconf are a lot more strict about demanding a
> > 3-tuple vs. 2-tuple than older versions.
> >=20
> > Setting RUBY_ARCH?=3D${ARCH}-portbld-freebsd${OSREL:C/\..*//}${RUBY_R} =
gets
> > GNU autoconf to configure properly. The "-pc-" in "x86_64-pc-freebsd5" =
is
> > a big warning GNU configure isn't being run correctly.
>=20
> Thanks for the hint. I remembered why I cleared CONFIGURE_TARGET and
> just fixed the problem.
Thanks!
Kris
--AhhlLboLdkugWU4S
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE/wf6iWry0BWjoQKURAmskAJ9U3yaqQHlV8diVy/zREj+cl6jekgCbB/nf
0pImS0SOIM0IwF/qC6uXRzY=
=5bdZ
-----END PGP SIGNATURE-----
--AhhlLboLdkugWU4S--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031124125043.GA16016>