From owner-freebsd-arm@freebsd.org Fri Nov 20 16:54:53 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0662A33034; Fri, 20 Nov 2015 16:54:53 +0000 (UTC) (envelope-from mmoll@darkthrone.kvedulv.de) Received: from darkthrone.kvedulv.de (darkthrone.kvedulv.de [IPv6:2001:1578:400:101::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darkthrone.kvedulv.de", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C5011576; Fri, 20 Nov 2015 16:54:50 +0000 (UTC) (envelope-from mmoll@darkthrone.kvedulv.de) Received: by darkthrone.kvedulv.de (Postfix, from userid 666) id 9228ADB5; Fri, 20 Nov 2015 17:54:46 +0100 (CET) Date: Fri, 20 Nov 2015 17:54:46 +0100 From: Michael Moll To: freebsd-arm@FreeBSD.org, freebsd-toolchain@FreeBSD.org Subject: lang/ruby2* build failure on arm Message-ID: <20151120165446.GB48644@darkthrone.kvedulv.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 16:54:54 -0000 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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? --=20 Michael Moll --zhXaljGHf11kAtnf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJWT1BVAAoJEHSbfGivsRbHM8IQAIPkoKtIyW7FOH9CAyNsSGL8 dhWQxgtXDeAaKEj+MXeS8fP9vngVGvsKaPpVnfly7EcoZLxAYssJAWDw0DHeZaq8 9AbAeDXdueB317XctlugidOL5hsF8b08imKsiR0dFMuX/i0+XY646sdVwLMKkMMh REPtoB2YWcbXoc/wyg1+igNa9bbK2JJ3qun4DUKqOepAZ5oG9ToJX/X6idZBW1TV AfBdPnPncewLXeXtWI2IPVR2KcFd3mINRTAbGg0ugLejQwoDIoi/8r2LGBzNsw7n yn2AoytgB7LKDR2KFpFrvEhP55+N7u8ddJCMWZnIzDv9fUukdWgKJQu2l201z3xH JkCFAF2NfXa1LKNT3dFh6fPvtF4OQb0LRlhxQVsqVtNZM7b/HcUbGiuztwPnh6SV HkKiv2hl1SdrAYYyomSUCq2LO89rvKzBrdSZNHNqORKS+DdvZQxG5psRycU6GbBJ Xazly71rS3OjykBJHkauG6clUsjmLXNWYEj9ulCCqPgeFRHxoC69qH2iNxhBKFs+ aowyBHuhDJ/N2FhZqnnTb0m3EnxEBeaDQJcemjYoy6QVBe40TmjoQ7mfShEHBHY9 Qmx74kk/m9b+Lb+zosK+xPIPxVY9D0UJx+CfPp2Isz+8hqGjg1xdqkjsOGajCjVK Q38KTsr7JZJAy/dtXdk3 =bBdv -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf--