Date: Fri, 18 Sep 2020 13:27:23 -0600 From: Ian Lepore <ian@freebsd.org> To: Mark Johnston <markj@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r365889 - head/share/mk Message-ID: <311b50c504a5dc1e54a1442aa4f759b14f263b67.camel@freebsd.org> In-Reply-To: <202009181903.08IJ3YTM014958@repo.freebsd.org> References: <202009181903.08IJ3YTM014958@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2020-09-18 at 19:03 +0000, Mark Johnston wrote: > Author: markj > Date: Fri Sep 18 19:03:34 2020 > New Revision: 365889 > URL: https://svnweb.freebsd.org/changeset/base/365889 > > Log: > Install library symlinks atomically. > > As we do for shared library binaries, pass -S to install(1) when > installing symlinks. Doing so helps avoid transient failures when > libraries are being reinstalled, which seems to be the root cause > of > spurious libgcc_s.so link failures during CI builds. > Actually, I believe this will just paper over the real problem, which is the fact that we're building and installing the same library multiple times during early build steps. Nobody has yet been able to explain why we do that, and I haven't been able to figure out why by analyzing any differences in the generated files, but I'm not done trying. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?311b50c504a5dc1e54a1442aa4f759b14f263b67.camel>