Re: lang/ruby2* build failure on arm
On Fri, Nov 20, 2015 at 11:18:09PM +0100, Dimitry Andric wrote: > As to why GNU configure tries to call this without arguments, is beyond > me. To work around its brokenness, I would set ac_cv_func__setjmp to > yes before calling configure. Or attempt to unbreak autoconf, but that > is a truly Herculean task. :-) Tested and committed as r402110, thank you very much! -- Michael Moll signature.asc Description: PGP signature
Re: lang/ruby2* build failure on arm
Hi, On Fri, Nov 20, 2015 at 06:04:53PM +0100, Dimitry Andric wrote: > > In r384323 (ports) swills@ fixed the build of the lang/ruby2* ports, > > however, on a recent CURRENT on armv6hf I'm getting: > > checking for setjmp type... configure: error: _setjmp is not available > > Check the config.log file for further details. Why does the configure > script conclude that _setjmp is not available? The whole file is available as http://space.kvedulv.de/ruby_arm_config.log, the output from the specific test is: conftest.c:340:20: error: __builtin_longjmp is not supported for the current target void t(void) {__builtin_longjmp((void **) jb, 1);} ^~ conftest.c:341:29: error: __builtin_setjmp is not supported for the current target int jump(void) {(void)(__builtin_setjmp((void **) jb) ? 1 : 0); return 0;} ^~~~~~~~~~ Regards -- Michael Moll signature.asc Description: PGP signature
lang/ruby2* build failure on arm
Hello, first, sorry for cross-posting this to arm and toolchain, but I'm unsure in which direction this will go... please CC me, as I'm not subscribed to any of the both lists. In r384323 (ports) swills@ fixed the build of the lang/ruby2* ports, however, on a recent CURRENT on armv6hf I'm getting: checking for setjmp type... configure: error: _setjmp is not available Reverting that change leads to a working Ruby, so the question here is: Which OSVERSION did bring in that change? I'm suspecting the LLVM 3.7 import, but have no further data to back this claim. Any hints? -- Michael Moll signature.asc Description: PGP signature