32 bit libraries - build hack

[Marcel Moolenaar]

On Mon, Mar 22, 2004 at 10:16:18AM -0800, David O'Brien wrote:
> On Mon, Mar 22, 2004 at 09:41:28AM -0800, Marcel Moolenaar wrote:
> > On Sun, Mar 21, 2004 at 11:53:28PM -0800, David O'Brien wrote:
> > > On Sun, Mar 21, 2004 at 08:12:29PM -0800, Peter Wemm wrote:
> > > > mkdir /lib32
> > > > mkdir /usr/lib32
> > > > mkdir /usr/local/lib32
> > > > mkdir /usr/X11R6/lib32
> > > 
> > > "lib32" should be reserved for 32-bit libs that are specific to AMD64
> > > (and either won't run on i386, or will run very sub-optimally).  These
> > > libs should live in lib/i386.
> > 
> > Agreed. A better place for FreeBSD/i386 libraries is under /compat.
> 
> Not quite what I said. :-)  I disagree with /compat unless we start
> putting releng4 libs in /compat/freebsd4-ia32 on 5-current.

We probably need to shuffle things around anyway. With linux compat
bits for the native runtime and for i386 besides FreeBSD compat bits
for the native runtime, backward versions of the native runtime and
likewise for non-native runtimes, things quickly become woody (read:
a forest with lots of trees in front of it :-)

A good and consistent naming scheme is very likely needed, as well
as a good and consistent hierarchy.

The same applies to the FREEBSD4_COMPAT kernel option. It's doubling
for both the native code as well as any FreeBSD compat code. This makes
it impossible to say: I don't want FreeBSD4/amd64 support, but I do
want FreeBSD4/i386 compatibility. This is not a problem because there's
no FreeBSD4/amd64, but all we have to do is sit and wait. I think you
can actually see the problem grow if you look closely enough :-)

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel at xcllnt.net