On Fri, Jan 15, 2016 at 03:00:00PM -0800, Bryan Drewery wrote: > ... > >>>> World build started on Fri Jan 15 04:28:48 PST 2016 > > ... > >>>> stage 5.1: building 32 bit shim libraries > > ... > > --- lib/libldns__L --- > > --- libprivateldns.so.5 --- > > /usr/obj/usr/src/tmp/usr/bin/ld: skipping incompatible > > /usr/obj/usr/src/tmp/usr/lib/libgcc_s.so when searching for -lgcc_s > > This is odd...
Agreed; that's largely why I posted. Well, that, and the apparently lack of consistent behavior between the 2 machines. > > --- secure/lib/libssl__L --- > > --- libssl.a --- > > --- kerberos5/lib/libhx509__L --- > > --- keyset.po --- > > --- secure/lib/libssl__L --- > > building static ssl library > > --- lib/libldns__L --- > > /usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lgcc_s > > By this point (lib/libldns__L) libgcc should be built and installed. I > assume it says 'cannot find' since it is incompatible. Apparently, yes. > I don't think this is a build race or FAST_DEPEND issue. > > It could be a -DNO_CLEAN issue. Nothing is standing out as an issue in > the commit range given, except if you were building for arm. In each case, it was a native build on amd64. > ... > > cc: error: linker command failed with exit code 1 (use -v to see invocation) > > *** [libprivateldns.so.5] Error code 1 > > > > make: stopped in /usr/src/lib/libldns > > > > > > from which that process didn't recover at all well... though a > > re-start without "-DNO_CLEAN" completed successfully. > ... > > One other (possibly-salient) point is that the build machine's disk > > drive is an SSD. (And yes, that does tend to help make it faster.) > .... Well, I suppose I'll take some small comfort in knowing that I'm not the only one perplexed by the behavior. :-} Thanks for looking at it. Peace, david -- David H. Wolfskill da...@catwhisker.org Those who would murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
Description: PGP signature