[yocto] Build Errors with new recipe for pjproject (autotools/pkgconfig)

[Chris Trobridge]

Aside from the issues I mentioned previously, pjproject is detecting cross-compilation and this causes it to append '-x86_64-poky-linux-gnu' to all its library names.
This is then breaking autotools configuration in other recipes that are testing for the base name.
Is it common for a build process to differentiate cross compiled libraries like this?  Is there a preferred way to deal with it?
I'm not confident about changing the pjproject build but I can link the base name to the extended name in do_install_append() so both names are present. pkgconfig picks up the extended names so these are also used in other recipes too (both forms of name in the same command line...).
Regards,Chris

From: christrobridge at hotmail.com
To: yocto at yoctoproject.org
Date: Tue, 26 Apr 2016 10:15:34 +0100
Subject: [yocto] Build Errors with new recipe for pjproject	(autotools/pkgconfig)




I have been trying to formulate a new recipe for pjproject (pjsip) - there was one but it seems too old and isn't part of any layer now.
The library seems to require a fairly straightforward autotools/pkgconfig recipe but I get two errors, both of which I can see have come up before but haven't been answered satisfactorily.
The first is that the link stage fails with "x86_64-poky-linux-ld: unrecognized option '-Wl,-O1'".
I've found this answered as "tools being too old" but '-Wl,' is a gcc prefix to pass an option to the linker but the linker is being invoked directly and so this is really a configuration mismatch.  I can fix this with "LD=$CXX" in do_configure_prepend() but I am puzzled as to why autotools would get confused this way in the first place?
The second problem is possibly more recent: ERROR: pjproject-2.4.5-r0 do_populate_sysroot: QA Issue: libpjproject.pc failed sanity test (tmpdir) in path /home/chris/yocto/build/tmp/work/corei7-64-poky-linux/pjproject/2.4.5-r0/sysroot-destdir/usr/lib/pkgconfig [pkgconfig]
I think this is benign other than leaking my dev environment but there was an oe gcc patch earlier this year that addressed this (http://lists.openembedded.org/pipermail/openembedded-core/2016-January/116468.html).
Apparently there was QA change the broke a lot of recipes but it's not clear how to fix this recipe - from what I could tell the fix should have applied to all recipes.  Adding '-gno-record-debug-prefix-map' should fix this but the compiler option is not recognised.
Any ideas on how to solve the QA error?
I am using the poky commit for 2.1_M4.rc1.
Thanks,Chris
 		 	   		  

-- 
_______________________________________________
yocto mailing list
yocto at yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160427/66dba522/attachment.html>