public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Mazur <mmazur@kernel.pl>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Rahul Karnik <deathdruid@gmail.com>,
	Andrew Walrond <andrew@walrond.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.10.0
Date: Thu, 13 Jan 2005 17:29:58 +0100	[thread overview]
Message-ID: <200501131729.58803.mmazur@kernel.pl> (raw)
In-Reply-To: <20050113115154.GW10340@devserv.devel.redhat.com>

On czwartek 13 styczeń 2005 12:51, Jakub Jelinek wrote:
> For kernel modules you should never use /usr/include headers though.
> /lib/modules/`uname -r`/build/include headers should be used for them
> instead.

Exactly (more or less - I don't always need to build against the kernel I'm 
running - especially when building distro rpms).

*Any* sane userland application should avoid static dependencies on current 
kernel config *at* *all* *cost*.


-- 
In the year eighty five ten
God is gonna shake his mighty head
He'll either say,
"I'm pleased where man has been"
Or tear it down, and start again

  parent reply	other threads:[~2005-01-13 16:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 15:13 [ANNOUNCE] linux-libc-headers 2.6.10.0 Mariusz Mazur
2005-01-10 15:16 ` Randy.Dunlap
2005-01-12 10:49 ` Andrew Walrond
2005-01-12 11:11   ` Mariusz Mazur
2005-01-12 12:04     ` Andrew Walrond
2005-01-13  8:13     ` Andrew Walrond
2005-01-13  9:42       ` Mariusz Mazur
2005-01-13 11:00         ` Andrew Walrond
2005-01-13 11:46           ` Rahul Karnik
2005-01-13 11:51             ` Jakub Jelinek
2005-01-13 16:14               ` Rahul Karnik
2005-01-13 16:29               ` Mariusz Mazur [this message]
2005-01-13 12:18             ` Andrew Walrond

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=200501131729.58803.mmazur@kernel.pl \
    --to=mmazur@kernel.pl \
    --cc=andrew@walrond.org \
    --cc=deathdruid@gmail.com \
    --cc=jakub@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox