All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eli Carter <eli.carter@inet.com>
To: Dana Lacoste <dana.lacoste@peregrine.com>
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>, linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: Linus's include file strategy redux
Date: Fri, 15 Dec 2000 10:16:02 -0600	[thread overview]
Message-ID: <3A3A43C2.8F045738@inet.com> (raw)
In-Reply-To: <FBF96516CD5@vcnet.vc.cvut.cz> <02c501c066b0$2ae67f00$890216ac@ottawa.loran.com>

Dana Lacoste wrote:
> 
> > Maybe you did not notice, but for months we have
> > /lib/modules/`uname -r`/build/include, which points to kernel headers,
> > and which should be used for compiling out-of-tree kernel modules
> > (i.e. latest vmware uses this).
> 
> What about the case where I'm compiling for a kernel that I'm
> not running (yet)?
> 
> lm_sensors, for example, told me yesterday when I compiled it
> that I was running 2.2.17, but it was compiling for 2.2.18
> (because I moved the symlink in /usr/src/linux to point to
> /usr/src/linux-2.2.18)
> 
> I personally wouldn't like some programs to do a `uname -r`
> check because it won't do what I want it to :)

And don't forget cross-compiling...  (No, I don't know how all that is
supposed to work.  *sigh*)

^C-ya,

Eli
--------------------. "To the systems programmer, users and applications
Eli Carter          | serve only to provide a test load."
eli.carter@inet.com `---------------------------------- (random fortune)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-15 16:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-15 16:56 [OT] Re: Linus's include file strategy redux Petr Vandrovec
2000-12-15 16:00 ` Dana Lacoste
2000-12-15 16:16   ` Eli Carter [this message]
2000-12-15 17:31 ` ferret
2000-12-15 18:56   ` Ingo Oeser
2000-12-16  3:37     ` ferret
2000-12-16  6:57       ` Keith Owens
2000-12-16 16:40         ` ferret
2000-12-16 23:43       ` Peter Samuelson
2000-12-17  3:05         ` ferret
2000-12-17  8:08           ` Peter Samuelson
2000-12-17 20:08             ` ferret
2000-12-18  3:58               ` Peter Samuelson
2000-12-18 19:21                 ` ferret
  -- strict thread matches above, loose matches on Subject: below --
2000-12-15 17:09 Petr Vandrovec

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=3A3A43C2.8F045738@inet.com \
    --to=eli.carter@inet.com \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=dana.lacoste@peregrine.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.