Poudriere failing on some 10-STABLE ports --- "uses VFP register arguments"

[Paul Mather]

On Jul 3, 2016, at 12:47 AM, bob prohaska <fbsd at www.zefox.net> wrote:

> On Thu, Jun 30, 2016 at 09:04:41AM -0400, Paul Mather wrote:
>> 
>> 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... :-)
>> 
> 
> Moving to 11-CURRENT might not help much. An RPI2 at r302244 with ports at 417951 stops in
> portmaster -af 
> with: 
> 
> .....
> Build a threading Perl? [y]  
> Use which C compiler? [cc]  
> 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]  
> What is the file extension used for shared libraries? [so]  
> Make shared library basenames unique? [n]  
> Build Perl for SOCKS? [n]  
> Try to use long doubles if available? [n]  
> Checking for optional libraries...
> What libraries to use? [-lpthread -lgdbm -lm -lcrypt -lutil]  
> What optimizer/debugger flag should be used? [-g]  
> Any additional cc flags?
> [-DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -DDEBUGGING -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include]  
> Let me guess what the preprocessor flags are...
> Any additional ld flags (NOT including libraries)?
> [-lpthread -Wl,-E  -fstack-protector -L/usr/local/lib]  
> Checking your choice of C compiler and flags for coherency...
> I've tried to compile and run the following simple program:
> 
> #include <stdio.h>
> int main() { printf("Ok\n"); return(0); }
> 
> I used the command:
> 
> 	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
> 
> and I got the following output:
> 
> /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]  
> Ok.  Stopping Configure.
> ===>  Script "Configure" failed unexpectedly.
> 
> 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. 
> 
> Thanks for reading, any advice appreciated!
> 
> 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:

====>> 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 at 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.