Date: Mon, 24 Nov 2003 03:47:50 -0800 From: "David O'Brien" <obrien@freebsd.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: <20031124114750.GA60860@dragon.nuxi.com> In-Reply-To: <20031124092900.GA12109@xor.obsecurity.org> References: <20031124002433.GB6264@xor.obsecurity.org> <86znemcf0m.knu@iDaemons.org> <20031124092900.GA12109@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 24, 2003 at 01:29:00AM -0800, Kris Kennaway wrote: > On Mon, Nov 24, 2003 at 06:06:01PM +0900, Akinori MUSHA wrote: > > > http://bento.freebsd.org/errorlogs/amd64-5-latest/ruby-1.8.1.p2.log > > > Can you please investigate ASAP? > > > > 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. 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. Setting RUBY_ARCH?=${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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031124114750.GA60860>