From: Corey Minyard <minyard@acm.org>
To: Thomas Capricelli <tcaprice@logatique.fr>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: Moving zlib so that others may use it
Date: Thu, 10 Jan 2002 08:40:32 -0600 [thread overview]
Message-ID: <3C3DA7E0.3050106@acm.org> (raw)
In-Reply-To: <24675.1010641200@kao2.melbourne.sgi.com> <20020110105313.3ED7023CBB@persephone.dmz.logatique.fr>
I'll do it, since I already have most of it, unless Keith already has or
wants to.
-Corey
Thomas Capricelli wrote:
>On Thursday 10 January 2002 06:40, Keith Owens wrote:
>
>>On Wed, 09 Jan 2002 23:13:28 -0600,
>>
>>Corey Minyard <minyard@acm.org> wrote:
>>
>>>Hmm. It worked fine for me. I made it a module, and it put it into
>>>kernel/lib in
>>>/lib/modules/2.4.17 and it did not put it in lib/lib.a I make it a
>>>non-module, and
>>>it gets included in lib/lib.a. My diff was the same as yours for the
>>>Makefile.
>>>
>>Worked for me this time as well. I had a typo the first time then did
>>an ugly fix to a non-existent problem :(
>>
>
>
> Could you give a patch for all of this ? either Keith or Corey ?
>
>
>Thomas
>
next prev parent reply other threads:[~2002-01-10 14:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 23:32 Moving zlib so that others may use it Corey Minyard
2002-01-09 23:36 ` 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 [this message]
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=3C3DA7E0.3050106@acm.org \
--to=minyard@acm.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tcaprice@logatique.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox