Am Thu, 15 Jun 2017 13:11:52 -0700 Jason Evans <jas...@canonware.com> schrieb:
> On Thu, 15 Jun 2017 08:04:57 -0700 > Jason Evans <jas...@canonware.com> wrote: > > > On Thu, 15 Jun 2017 10:31:57 +0200 > > "O. Hartmann" <ohartm...@walstatt.org> wrote: > > > > > On Thu, 15 Jun 2017 07:15:06 +0000 (UTC) > > > Jason Evans <jas...@freebsd.org> wrote: > > > > > > > Author: jasone > > > > Date: Thu Jun 15 07:15:05 2017 > > > > New Revision: 319971 > > > > URL: https://svnweb.freebsd.org/changeset/base/319971 > > > > > > > > Log: > > > > Update jemalloc to 5.0.0. > > > > > > On all hosts (running CURRENT: FreeBSD 12.0-CURRENT #15 r319965: Thu Jun > > > 15 > > > 05:56:12 CEST 2017 amd64 AND FreeBSD 12.0-CURRENT #20 r319934: Wed Jun 14 > > > 06:18:46 CEST 2017 amd64) > > > > > > buildworld fails on > > > > > > [...] > > > Building /usr/obj/usr/src/lib/libgcc_s/_libinstall > > > --- secure/lib/libcrypto__L --- > > > --- all_subdir_secure/lib/libcrypto/engines/libaep --- > > > /usr/obj/usr/src/tmp/usr/bin/ld: error: unable to find library -lgcc_s > > > /usr/obj/usr/src/tmp/usr/bin/ld: error: unable to find library -lgcc_s > > > cc: error: linker command failed with exit code 1 (use -v to see > > > invocation) > > > *** [libaep.so] Error code 1 > > > > > > make[6]: stopped in /usr/src/secure/lib/libcrypto/engines/libaep > > > .ERROR_TARGET='libaep.so' > > > > I tested this commit based on r319490. I'm in the process of updating to > > r319971, > > and will see if the issue reproduces. > > I updated from r319490 (with jemalloc update integrated) to r319971, then > rebuilt > r319971 without issues. Is it possible that the issue you hit isn't directly > related > to r319971? > > Thanks, > Jason > _______________________________________________ > svn-src-head@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/svn-src-head > To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org" Sorry for the late response. The problem vanished after removing /usr/obj and restarting the buildworld process. I did so consequently on all systems after this incident and had no problems so far. And: yes, it (the initial problem reported) could probably be related to something else, but it occured immediately after the update of this SVN index has been committed. But I think that doesn't matter anymore. Kind regards, Oliver -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
pgpfpTdbRW66A.pgp
Description: OpenPGP digital signature
