Date: Tue, 11 Aug 1998 10:58:59 +0200 (CEST) From: Søren Schmidt <sos@FreeBSD.org> To: nik@iii.co.uk Cc: hasty@rah.star-gate.com, garbanzo@hooked.net, doconnor@gsoft.com.au, jkh@time.cdrom.com, jkoshy@FreeBSD.org, committers@FreeBSD.org Subject: Re: 3.0 Schedule, ELF and CAM Message-ID: <199808110858.KAA06754@sos.freebsd.dk> In-Reply-To: <19980811093846.A11516@iii.co.uk> from "nik@iii.co.uk" at "Aug 11, 98 09:38:46 am"
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to nik@iii.co.uk who wrote:
> On Mon, Aug 10, 1998 at 11:02:48PM -0700, Amancio Hasty wrote:
> > If not "/usr/lib", where would you like your elf libs to go to?
>
> /usr/lib.elf and /usr/lib.aout, with /usr/lib being a symlink to whichever
> one is the current default on the system.
>
> This is probably a frighteningly bad idea, but every time I've mentioned
> it on -hackers or -current, no one's stood up to say so.
OK, I'll say this, a.out libs are in /usr/lib/aout, and is only
there for backwards compat during the transition. After that the
shared aout libs can be moved to /usr/lib/compat, the *.a's are
no longer needed.
How long they stay in /usr/lib/aout, is only a matter of when we
decide to cut aout compilation away on a "standard" system. At any
rate it will soon be impossible to build BOTH aout and ELF libraries
from the same sources, so the aout libs will not be updated anyways.
ELF libs go in /usr/lib (where they are supposed to be).
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
Even more code to hack -- will it ever end?
..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808110858.KAA06754>