Date: Fri, 24 Aug 2007 18:25:17 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Alfred Perlstein <alfred@freebsd.org> Cc: src-committers@freebsd.org, cvs-all@freebsd.org, cvs-src@freebsd.org, Yar Tikhiy <yar@comp.chem.msu.su> Subject: Re: cvs commit: src/lib/libc/gen fts-compat.c fts-compat.h Message-ID: <Pine.GSO.4.64.0708241819220.13181@sea.ntplx.net> In-Reply-To: <20070824220244.GH87451@elvis.mu.org> References: <200708230509.l7N59VCi048341@repoman.freebsd.org> <Pine.GSO.4.64.0708241057010.12450@sea.ntplx.net> <20070824183630.GA99474@comp.chem.msu.su> <20070824215515.GF16131@turion.vk2pj.dyndns.org> <20070824220244.GH87451@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 24 Aug 2007, Alfred Perlstein wrote: > Not to pick on anyone here but Yar did something that works, > why exactly are we not allowing him to use the tools provided > for this exact purpose and instead making him do convoluted > workarounds? > > I mean seriously, so we have a versioned symbol that could > possibly be avoided by a lot of hard work and magic which will > probably fail for a bunch of users.... > > ...so why not just use what works? Please, enough of this "it works, so why not?". We didn't always have symbol versioning, and we have solved these problems before without it. There seems to be an inherent problem with our build system, and the LD_LIBRARY_PATH trick seems to make sense to me, or building and installing the install tools as static to avoid problems like this. I never added symbol versioning to libc in order to solve -current upgrade problems. Sure, you're free to use it that way, but it would not make me very happy ;-) -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0708241819220.13181>