Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Nov 2015 23:18:09 +0100
From:      Dimitry Andric <dim@FreeBSD.org>
To:        Michael Moll <mmoll@FreeBSD.org>
Cc:        freebsd-arm@FreeBSD.org, freebsd-toolchain@FreeBSD.org
Subject:   Re: lang/ruby2* build failure on arm
Message-ID:  <903D1E22-D3E4-4DDA-BBF3-F8DDFAE91B56@FreeBSD.org>
In-Reply-To: <20151120220210.GC48644@darkthrone.kvedulv.de>
References:  <20151120165446.GB48644@darkthrone.kvedulv.de> <963F064D-2B30-40E4-9F09-31C9121CE80A@FreeBSD.org> <20151120220210.GC48644@darkthrone.kvedulv.de>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_708D8047-CBEA-48C1-BAB2-B34E0AD72A98
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 20 Nov 2015, at 23:02, Michael Moll <mmoll@FreeBSD.org> wrote:
>=20
> 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
>>=20
>> Check the config.log file for further details.  Why does the =
configure
>> script conclude that _setjmp is not available?
>=20
> The whole file is available as =
http://space.kvedulv.de/ruby_arm_config.log, the output
> from the specific test is:
>=20
> 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;}
>                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Right, but that is not the real problem.  Earlier on, the configure
script is checking for the regular _setjmp():

configure:16921: checking for _setjmp
configure:16921: cc -o conftest -O -pipe  -fno-strict-aliasing =
-I/usr/local/include   -fstack-protector conftest.c -lcrypt -lm =
-lpthread -L/usr/local/lib >&5
conftest.c:228:6: warning: declaration of built-in function '_setjmp' =
requires inclusion of the header <setjmp.h> [-Wbuiltin-requires-header]
char _setjmp ();
     ^
conftest.c:239:17: error: too few arguments to function call, expected =
1, have 0
return _setjmp ();
       ~~~~~~~~~^
1 warning and 1 error generated.
configure:16921: $? =3D 1
configure: failed program was:

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. :-)

-Dimitry


--Apple-Mail=_708D8047-CBEA-48C1-BAB2-B34E0AD72A98
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.28

iEYEARECAAYFAlZPnCEACgkQsF6jCi4glqOOpwCeLdlgHZmDgIi9XZtNgnUIsQ20
LwYAoPqY3kVpscCXS1HDJ8JQcSDEXDmS
=pAtY
-----END PGP SIGNATURE-----

--Apple-Mail=_708D8047-CBEA-48C1-BAB2-B34E0AD72A98--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?903D1E22-D3E4-4DDA-BBF3-F8DDFAE91B56>