All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-kernel-headers-2.6.19-rc1.tar.gz
Date: Mon, 9 Oct 2006 11:42:06 -0600	[thread overview]
Message-ID: <20061009174205.GA24502@codepoet.org> (raw)
In-Reply-To: <1160032160.26064.17.camel@pmac.infradead.org>

On Thu Oct 05, 2006 at 08:09:20AM +0100, David Woodhouse wrote:
> A full set of user-visible kernel headers for all supported
> architectures, exported from the 2.6.19-rc1 kernel, has been uploaded
> to
> ftp://ftp.kernel.org/pub/linux/kernel/people/dwmw2/kernel-headers/snapshot/
> 
> I had planned to do this for 2.6.18 but it wasn't quite in good enough
> shape by then. This one should be fine -- you can build your C library
> against it and ship it in /usr/include. And tell me what breaks...

I'm curious how you produced this for all architectures?  Did you
write up a script to so something trivial like

    for i in $LINUX_DIR/arch/*; do
	make ARCH=$(basename $i) INSTALL_HDR_PATH=/tmp/foo headers_install;
    done

or did you do something more complicated and interesting?  If so,
would you mind sharing?

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

  reply	other threads:[~2006-10-09 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05  7:09 [ANNOUNCE] linux-kernel-headers-2.6.19-rc1.tar.gz David Woodhouse
2006-10-09 17:42 ` Erik Andersen [this message]
2006-10-09 19:50   ` David Woodhouse
2006-10-09 19:57     ` Erik Andersen

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=20061009174205.GA24502@codepoet.org \
    --to=andersen@codepoet.org \
    --cc=dwmw2@infradead.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.