All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: linux-kernel@vger.kernel.org
Subject: Moving zlib so that others may use it
Date: Wed, 09 Jan 2002 17:32:20 -0600	[thread overview]
Message-ID: <3C3CD304.9070704@acm.org> (raw)

I'm working on a function that uses zlib in the kernel, and I know of 
other places zlib is used (ppp_deflate, jffs2, mcore).  I would expect 
more users to come along.

I would like to propose putting zlib in the lib directory and making it 
optionally compile if it is needed.  It's pretty easy to move the files 
around and make a few small changes to the code.  However, how do I 
configure such a thing?  I could add something like:

   if [ "$CONFIG_PPP_DEFLATE" = "y" ]; then
      define_tristate CONFIG_ZLIB y
   fi
   if [ "$CONFIG_PPP_DEFLATE" = "m" ]; then
      if [ "$CONFIG_ZLIB" != "y" ]; then
         define_tristate CONFIG_ZLIB m
      fi
   fi

to every place that uses it, or I could put something like:

   if [ "$CONFIG_JFFS2_FS" = "y" \
        -o "$CONFIG_PPP_DEFLATE" = "y" ]; then
      define_tristate CONFIG_ZLIB y
   else
      if [ "$CONFIG_JFFS2_FS" = "m" \
          -o "$CONFIG_PPP_DEFLATE" = "m" ]; then
         define_tristate CONFIG_ZLIB m
      fi
   fi

at the end of the config.  I would prefer the latter, but there is not 
an "end of config" place, you would have to put it at the end of every 
config.in (about 15 architectures right now).  I propose to add a 
Config.in to the lib directory that is sourced at the end of every 
config.in for the architectures.  I'll do the work if it's willing to be 
accepted into the kernel.

-Corey



             reply	other threads:[~2002-01-09 23:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09 23:32 Corey Minyard [this message]
2002-01-09 23:36 ` Moving zlib so that others may use it H. Peter Anvin
2002-01-10  1:52 ` Keith Owens
2002-01-10  4:23   ` Corey Minyard
2002-01-10  4:44     ` Keith Owens
2002-01-10  5:13       ` Corey Minyard
2002-01-10  5:40         ` Keith Owens
2002-01-10 10:55           ` Thomas Capricelli
2002-01-10 14:40             ` Corey Minyard
2002-01-10 15:22             ` Corey Minyard
2002-01-10  9:37         ` Zygo Blaxell
2002-01-10 15:30           ` Tom Rini
2002-01-10 15:36       ` Tom Rini
2002-01-10 16:20         ` Corey Minyard
2002-01-10 16:35           ` Tom Rini
2002-01-10  4:33   ` Corey Minyard
2002-01-10  6:08     ` H. Peter Anvin
2002-01-10 14:13   ` David Woodhouse

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=3C3CD304.9070704@acm.org \
    --to=minyard@acm.org \
    --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.