Date: Wed, 19 May 1999 07:34:38 +1000 (EST) From: John Birrell <jb@cimlogic.com.au> To: obrien@NUXI.com Cc: mike@smith.net.au, jkh@zippy.cdrom.com, hackers@FreeBSD.ORG Subject: Re: a.out lib placment (was: 3.2-RELEASE and netscape problem.) Message-ID: <199905182134.HAA28910@cimlogic.com.au> In-Reply-To: <19990518115818.B53888@nuxi.com> from "David O'Brien" at "May 18, 1999 11:58:18 am"
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote:
> > It breaks because compat22 is installing _everything_ in
> > /usr/lib/compat/aout. We've reproduced this locally - compat22 is
> > hosed.
>
> I *knew* this was going to bite us in the ass. I brought it up at E-day
> time... and was ignored.
"I hear what you say - I just don't agree"
> Some body please decide where bits should live. *IF* you upgrade from
> 2.2.x to 3.x, your /usr/lib a.out libs are moved to /usr/lib/aout, *AND*
> your /usr/lib/compat a.out libs are moved to /usr/lib/compat/aout. Fine.
>
> NOW if you look at the compat2{0,1} bits we shipped with 3.2, they
> install into /usr/lib/compat/. Thus we have no consistancy. So compat22
> is no more broken than ``make aout-to-elf''.
In an elf world, /usr/lib and /usr/lib/compat are for things in elf format.
/usr/lib/aout and /usr/lib/compat/aout are legacy directories for things in
aout format. I think you are abusing compat22 by adding the aout (legacy)
stuff. Why not just build a legacy library bundle and install it where it
belongs.
--
John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905182134.HAA28910>