The x86 build linker scripts were still searching hard-coded paths on the build host for libraries. As it happens, the libraries needed for linking the failing executable are present on my build host, so the build succeeds here despite the erroneous linker paths. Consequently I had stupidly assumed the resulting QA warning was a fairly benign error until your test build in a pristine environment demonstrated otherwise.
I'm unclear as to the exact behavior shown by your log of the failed build, but since it is a linker error I am for now assuming it is precipitated somehow by the flawed library search paths. In any case with the hard-coded host paths commented out I get a clean build without the QA warning and see no similar logs in my local builds - so I hope this will also fix the build failures on your end. Regards, Gary Robertson -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
