From owner-freebsd-arm@freebsd.org Tue Jul 5 19:25:28 2016 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 62022B2157F for ; Tue, 5 Jul 2016 19:25:28 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 203AA1735; Tue, 5 Jul 2016 19:25:27 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 9D3F8150; Tue, 5 Jul 2016 15:25:20 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Poudriere failing on some 10-STABLE ports --- "uses VFP register arguments" From: Paul Mather In-Reply-To: <20160703044730.GG3406@www.zefox.net> Date: Tue, 5 Jul 2016 15:25:19 -0400 Cc: Ian Lepore , "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <5D3A3A05-27B2-4680-9711-D02696D4ABE5@gromit.dlib.vt.edu> References: <854D8FF8-CE45-44C1-B371-79AA6DD782FB@gromit.dlib.vt.edu> <1466799055.72182.50.camel@freebsd.org> <20160703044730.GG3406@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 19:25:28 -0000 On Jul 3, 2016, at 12:47 AM, bob prohaska wrote: > On Thu, Jun 30, 2016 at 09:04:41AM -0400, Paul Mather wrote: >>=20 >> I think this package building issue is probably a gentle hint that I = should also upgrade my 10-STABLE armv6 systems (Raspberry Pi) to = 11-CURRENT, like my BeagleBone Black. It's probably better in the long = run than trying to figure out how to build 10-STABLE packages, as = 11-CURRENT appears to be where all the focus and TLC is in the = FreeBSD/arm world nowadays. Plus, I'd only have to maintain one local = FreeBSD/arm package repository... :-) >>=20 >=20 > Moving to 11-CURRENT might not help much. An RPI2 at r302244 with = ports at 417951 stops in > portmaster -af=20 > with:=20 >=20 > ..... > Build a threading Perl? [y] =20 > Use which C compiler? [cc] =20 > Checking for GNU cc in disguise and/or its version number... > Now, how can we feed standard input to your C preprocessor... > Directories to use for library searches? > [/usr/lib /usr/local/lib /usr/bin/../lib/clang/3.8.0/lib /usr/lib] =20 > What is the file extension used for shared libraries? [so] =20 > Make shared library basenames unique? [n] =20 > Build Perl for SOCKS? [n] =20 > Try to use long doubles if available? [n] =20 > Checking for optional libraries... > What libraries to use? [-lpthread -lgdbm -lm -lcrypt -lutil] =20 > What optimizer/debugger flag should be used? [-g] =20 > Any additional cc flags? > [-DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -DDEBUGGING = -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include] =20 > Let me guess what the preprocessor flags are... > Any additional ld flags (NOT including libraries)? > [-lpthread -Wl,-E -fstack-protector -L/usr/local/lib] =20 > Checking your choice of C compiler and flags for coherency... > I've tried to compile and run the following simple program: >=20 > #include > int main() { printf("Ok\n"); return(0); } >=20 > I used the command: >=20 > cc -o try -g -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -DDEBUGGING = -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include = -lpthread -Wl,-E -fstack-protector -L/usr/local/lib try.c -lpthread = -lgdbm -lm -lcrypt -lutil > ./try >=20 > and I got the following output: >=20 > /usr/bin/ld: ERROR: try uses VFP register arguments, = /usr/local/lib/libgdbm.so does not > /usr/bin/ld: failed to merge target specific data of file = /usr/local/lib/libgdbm.so > cc: error: linker command failed with exit code 1 (use -v to see = invocation) > I can't compile the test program. > You have a BIG problem. Shall I abort Configure [y] =20 > Ok. Stopping Configure. > =3D=3D=3D> Script "Configure" failed unexpectedly. >=20 > It appears that a mismatch has developed between the base system and = the ports which > hasn't been resolved by building world. I'll try again but am not = optimistic.=20 >=20 > Thanks for reading, any advice appreciated! >=20 > bob prohaska I'm not having any problems building FreeBSD/arm 11-CURRENT ports under = FreeBSD/amd64 11-CURRENT via Poudriere. My last successful build of lang/perl5.20 was on 2016-06-30: =3D=3D=3D=3D>> Building lang/perl5.20 build started at Thu Jun 30 16:40:27 EDT 2016 port directory: /usr/ports/lang/perl5.20 building for: FreeBSD armv6_current-default-job-02 11.0-ALPHA5 FreeBSD = 11.0-ALPHA5 r302298 arm maintained by: perl@FreeBSD.org Makefile ident: $FreeBSD: head/lang/perl5.20/Makefile 414862 = 2016-05-09 16:03:40Z mat $ Poudriere version: 3.1.14 Host OSVERSION: 1100120 Jail OSVERSION: 1100120 The revision of the FreeBSD/arm 11-CURRENT jail is later than yours = above: r302298 vs. r302244. I don't know whether that is significant. I've not tried to build ports natively under FreeBSD/arm because it's = much easier for me to build them on a build machine using Poudriere = along with the other architectures for which I build local repositories. Cheers, Paul.=