From owner-freebsd-arm@FreeBSD.ORG Thu Jan 17 05:24:35 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 22D2B3A4 for ; Thu, 17 Jan 2013 05:24:35 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [88.198.91.248]) by mx1.freebsd.org (Postfix) with ESMTP id C8DBA3DA for ; Thu, 17 Jan 2013 05:24:34 +0000 (UTC) Received: from [207.6.254.8] (helo=[192.168.1.67]) by id.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1Tvhxn-000Df9-2L; Wed, 16 Jan 2013 21:24:33 -0800 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Nginx Build Fails on Compiling pcre From: Oleksandr Tymoshenko In-Reply-To: <50F74150.1080600@tummy.com> Date: Wed, 16 Jan 2013 21:24:12 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <0C39E32B-32D2-4FE6-A8D4-168C83F18AF0@bluezbox.com> References: <50F74150.1080600@tummy.com> To: Jesse Griffin X-Mailer: Apple Mail (2.1499) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 2013-01-16, at 4:09 PM, Jesse Griffin wrote: > Hello, > > I'm not sure if this is the correct list, but the only reason why I did the > following was to test FreeBSD on the Pi. > > I setup http://www.peach.ne.jp/archives/rpi/freebsd-pi-clang-20130115.img.gz on > my Pi and I tried building several ports to see what I got. Most of them > completed okay, but the Nginx build fails when it tries to compile > /usr/ports/devel/pcre. > > Building Nginx on an i386 FreeBSD 10 CURRENT works. > > Below is the output: > > root@raspberry-pi:/usr/ports/www/nginx # make install clean > ===> nginx-1.2.6, 1 depends on shared library: pcre - not found > ===> Verifying install for pcre in /usr/ports/devel/pcre > ===> Building for pcre-8.32 > make all-am > CCLD pcretest > ./.libs/libpcre.so: undefined reference to `__clear_cache' > cc: error: linker command failed with exit code 1 (use -v to see invocation) [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2013 05:24:35 -0000 On 2013-01-16, at 4:09 PM, Jesse Griffin wrote: > Hello, >=20 > I'm not sure if this is the correct list, but the only reason why I = did the > following was to test FreeBSD on the Pi. >=20 > I setup = http://www.peach.ne.jp/archives/rpi/freebsd-pi-clang-20130115.img.gz on > my Pi and I tried building several ports to see what I got. Most of = them > completed okay, but the Nginx build fails when it tries to compile > /usr/ports/devel/pcre. >=20 > Building Nginx on an i386 FreeBSD 10 CURRENT works. >=20 > Below is the output: >=20 > root@raspberry-pi:/usr/ports/www/nginx # make install clean > =3D=3D=3D> nginx-1.2.6,1 depends on shared library: pcre - not found > =3D=3D=3D> Verifying install for pcre in /usr/ports/devel/pcre > =3D=3D=3D> Building for pcre-8.32 > make all-am > CCLD pcretest > ./.libs/libpcre.so: undefined reference to `__clear_cache' > cc: error: linker command failed with exit code 1 (use -v to see = invocation) I believe it might be clang/ARM issue. gcc compiles test application = with=20 __clear_cache just fine on my ARM. Both clang and gcc compile the same application on x86_64. So some bits might be missing in clang's std = library=20 for ARM. =20