All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org, klibc@zytor.com
Subject: Re: [klibc 12/43] Enable CONFIG_KLIBC_ZLIB (now required to build kinit)
Date: Sun, 25 Jun 2006 20:22:39 -0700	[thread overview]
Message-ID: <449F52FF.7000300@zytor.com> (raw)
In-Reply-To: <449F511C.6020303@garzik.org>

Jeff Garzik wrote:
> H. Peter Anvin wrote:
>> After removing the private copy of zlib in kinit, we need
>> CONFIG_KLIBC_ZLIB in order to build klibc.  zlib is required in order
>> to decompress classical ramdisks.
>>
>> In the future this should maybe be made conditional on 
>> CONFIG_BLK_DEV_RAM.
> 
>> +config KLIBC_ZLIB
>> +    bool
>> +    default y
> 
> 
> Dumb question, then:  why not make it conditional on rd now?
> 

Mostly because I haven't yet broken down kinit in configurable chunks; 
it's somewhat messy to do as long as I'm maintaining a standalone 
distribution as well as the out-of-mainline kernel tree.  Not difficult 
by any means, but I've wanted to avoid combinatorics and code churn as 
long as I have a limited testing base (although -mm has vastly increased 
it.)

It's also unclear to me if it's the right thing to omit it from the 
library, ever; the only users that are affected are the ones that are 
using the shared klibc and don't have any use of zlib.

	-hpa



      reply	other threads:[~2006-06-26  3:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26  0:58 [klibc 12/43] Enable CONFIG_KLIBC_ZLIB (now required to build kinit) H. Peter Anvin
2006-06-26  3:14 ` Jeff Garzik
2006-06-26  3:22   ` H. Peter Anvin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=449F52FF.7000300@zytor.com \
    --to=hpa@zytor.com \
    --cc=jeff@garzik.org \
    --cc=klibc@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.