Date: Tue, 28 Aug 2007 07:27:22 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: "M. Warner Losh" <imp@bsdimp.com> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/lib/libc/gen fts-compat.c fts-compat.h Message-ID: <20070828042722.GQ2332@deviant.kiev.zoral.com.ua> In-Reply-To: <20070827.203029.-432838018.imp@bsdimp.com> References: <Pine.GSO.4.64.0708242252520.15344@sea.ntplx.net> <20070824.213615.146406398.imp@bsdimp.com> <20070828005654.GA50401@dragon.NUXI.org> <20070827.203029.-432838018.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--6wUvnnXCCq76soZt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 27, 2007 at 08:30:29PM -0600, M. Warner Losh wrote: > In message: <20070828005654.GA50401@dragon.NUXI.org> > "David O'Brien" <obrien@freebsd.org> writes: > : On Fri, Aug 24, 2007 at 09:36:15PM -0600, M. Warner Losh wrote: > : > In message: <Pine.GSO.4.64.0708242252520.15344@sea.ntplx.net> > : > Daniel Eischen <deischen@freebsd.org> writes: > : > : I guess the build system should be more tolerant of this, but > : > : there are bound to be problems regardless. I don't see why > : > : the install tools can't also either have their own set of > : > : libraries (utilizing LD_LIBRARY_PATH) or be built static. > : >=20 > : > There's much resistance to building everything that the build system > : > might be used being build static. It adds too much time and > : > complexity to the build system, the opponents say. > :=20 > : I've never heard an argument against building these bits static. > : What's the issue? >=20 > I thought you were one of the folks making this argument when we last > changed the FILE structure and related hangers on. >=20 > None of the binaries is built static by default, so we'd need to build It seems that toolchain is built static. Even binaries that go into the DESTDIR are static: % file /usr/bin/ld /usr/bin/ld: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), s= tatically linked, stripped The same is true for as, cc, libexec/cc1, make. The list is definitely not exhaustive. > new versions of them static to make this scheme work. We cannot count > on them being static in the release that we're upgrading from. > However, if we do build new versions static, then they would depend on > the new version of the kernel rather than the current version of the > kernel. >=20 > Warner --6wUvnnXCCq76soZt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFG06QqC3+MBN1Mb4gRAplCAJwLH5ElJZZxM50H5KnDAbu3LlPMHACgrIuo VglV+Bp3oHxuaykEWtj6GxU= =Jz6Z -----END PGP SIGNATURE----- --6wUvnnXCCq76soZt--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070828042722.GQ2332>