Re: Moving zlib so that others may use it

[uixjjji1@umail.furryterror.org (Zygo Blaxell)]

In article <3C3D22F8.1080201@acm.org>, Corey Minyard  <minyard@acm.org> wrote:
>Keith Owens wrote:
>
>>On Wed, 09 Jan 2002 22:23:31 -0600, 
>>Corey Minyard <minyard@acm.org> wrote:
>>>Keith Owens wrote:
[...]
>Building zlib as a
>>module guarantees that you cannot use it in a boot loader, forcing you
>>to maintain multiple versions of zlib.c.  If you are going to use one
>>version of zlib then you should try to handle bootloaders as well.
[...]
>I don't know about the bootloaders.  I'm not sure you can make the 
>requirement
>to have them compiled the same as the kernel, since they may have different
>compilation requirements in the boot loader.

Ummm, you can't use an in-kernel anything in a bootloader.  How do you
uncompress an in-kernel zlib.o without an out-of-kernel zlib.o lying
around somewhere?

The closest thing to a zlib.o shared between bootloader and kernel would
be to build one zlib.o and then perhaps copy the compiled binary from the
kernel to the bootloader (thus having only one zlib.c but two zlib.o) or
link it from the bootloader to the kernel once the kernel is uncompressed.

-- 
Zygo Blaxell (Laptop) <zblaxell@feedme.hungrycats.org>
GPG = D13D 6651 F446 9787 600B AD1E CCF3 6F93 2823 44AD