Date: Thu, 4 Sep 2003 10:41:00 -0700 From: Gordon Tetlow <gordont@gnf.org> To: "David O'Brien" <obrien@FreeBSD.org> Cc: Peter Wemm <peter@FreeBSD.org> Subject: Re: cvs commit: src/share/mk bsd.lib.mk Message-ID: <20030904174100.GY695@roark.gnf.org> In-Reply-To: <20030904162656.GA396@dragon.nuxi.com> References: <200309040429.h844TBhD058678@repoman.freebsd.org> <20030904083617.GA56261@dragon.nuxi.com> <20030904092755.GD45051@sunbay.com> <20030904140129.GA61909@dragon.nuxi.com> <20030904155659.GC97732@sunbay.com> <20030904162656.GA396@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--JZV+hE4cb0ibQYPB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 04, 2003 at 09:26:56AM -0700, David O'Brien wrote: > On Thu, Sep 04, 2003 at 06:56:59PM +0300, Ruslan Ermilov wrote: > > Sure. The fix is to make ``cc --print-search-dirs'' output include > > the /lib directory too. =20 >=20 > That is trival. >=20 > > I'm currently testing some patches with bsd.lib.mk,v 1.152. >=20 > We should all agree on where the symlink for things like libc.so.X live. > I'm 99% sure Peter will argue /usr/lib, and I personally don't care -- I > just want one of them. Before commiting yet something else to > bsd.lib.mk, what direction are you going in? It is much more appealing to me to put everything that is needed for a build into /usr/lib. /lib should only have enough to get us up and running, not enough to get us compiling, that's what /usr/lib is for. I have a patch that will do what we want, I'll see if I can dig it up. -gordon --JZV+hE4cb0ibQYPB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/V3ksRu2t9DV9ZfsRAsD+AKCzAlj9MpqCp2Gwnii6SSgWM790igCfSmSQ OlaViQ8dSjqCiOty11hAAxA= =3Szz -----END PGP SIGNATURE----- --JZV+hE4cb0ibQYPB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030904174100.GY695>