Date: Fri, 24 Aug 2007 16:37:09 -0400 From: John Baldwin <jhb@freebsd.org> To: Daniel Eischen <deischen@freebsd.org> Cc: Yar Tikhiy <yar@comp.chem.msu.su>, src-committers@freebsd.org, cvs-all@freebsd.org, cvs-src@freebsd.org Subject: Re: cvs commit: src/lib/libc/gen fts-compat.c fts-compat.h Message-ID: <200708241637.09962.jhb@freebsd.org> In-Reply-To: <Pine.GSO.4.64.0708241511440.13181@sea.ntplx.net> References: <200708230509.l7N59VCi048341@repoman.freebsd.org> <20070824183630.GA99474@comp.chem.msu.su> <Pine.GSO.4.64.0708241511440.13181@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 24 August 2007 03:14:53 pm Daniel Eischen wrote: > On Fri, 24 Aug 2007, Yar Tikhiy wrote: > > The reason for exercising symbol versions right now is that "make > > installworld" is sensitive to the fts(3) ABI. If the ABI is just > > broken w/o special measures, "make installworld" will fail in the > > middle and leave you with a botched system. It goes as follows: > > > > - "make installworld" copies the old /usr/bin/find and some other > > tools to /tmp/install.xxx for use during the install > > - libc is overwritten by its new instance, with new fts(3) ABI > > - the old find(1) is run by installworld and dumps core immediately. > > Why don't you make find and the install tools static. Because they aren't built during buildworld, these are the existing binaries on the existing system that are used just before they are overwritten. However, per my other e-mail, I think -current users should just deal, or use a temporary hack to get over the hurdle. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200708241637.09962.jhb>