Re: development packages and multilib

[Chris Adams <cmadams hiwaay net>]

Once upon a time, Callum Lerwick <seg haxxed com> said:
> But _I_ _do_ _not_ _have_ _to_ _do_ _this_ _for_ _Win32_ _or_ _mipsel_.
> Why is i386 special?

When you compile for Win32, you are using a cross-compiler environment.
Everything about it is different; different includes, compilers,
libraries, etc.

Now, Linux/i386 could be set up that way on Linux/x86_64, but that would
require rebuilding the development stack for cross-compilation
(different compilers, development packages, etc.).  This is not the same
as multilib (which allows i386 and x86_64 binaries to co-exist).

Nobody is interested in putting that much work into that setup,
especially when you can just use mock (since i386 binaries can run
natively on x86_64).

What is wrong with using mock?  It takes a little more disk space, and
you have the one-time hit of creating the root, but then it runs just
fine.  Mock isn't just for building RPMs; with copyin, copyout, and
shell, you can use it for all kinds of work.

-- 
Chris Adams <cmadams hiwaay net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.