Date: Thu, 4 Sep 2003 09:26:56 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: Ruslan Ermilov <ru@FreeBSD.org> Cc: Peter Wemm <peter@FreeBSD.org> Subject: Re: cvs commit: src/share/mk bsd.lib.mk Message-ID: <20030904162656.GA396@dragon.nuxi.com> In-Reply-To: <20030904155659.GC97732@sunbay.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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 04, 2003 at 06:56:59PM +0300, Ruslan Ermilov wrote: > On Thu, Sep 04, 2003 at 07:01:29AM -0700, David O'Brien wrote: > > On Thu, Sep 04, 2003 at 12:27:55PM +0300, Ruslan Ermilov wrote: > [...] > > > > GCC should have additional changes then. It is going to confuse other > > > > things to have the symlink in one directory and the real libs in another. > > > > > > > I will look into what else is needed in our toolchain to get rid of these > > > symlinks, and get back to you, David. > > > > Keep which ever symlinks you want /lib or /usr/lib -- but we should be > > totally unambigious as to which are the "real" ones, and don't install > > the other. Installing two sets of symlinks isn't the way to go. > > > Sure. The fix is to make ``cc --print-search-dirs'' output include > the /lib directory too. That is trival. > I'm currently testing some patches with bsd.lib.mk,v 1.152. 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030904162656.GA396>