From: Josh Huber <huber@mclx.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: problems about __cli()
Date: Mon, 24 Jul 2000 08:19:59 -0400 [thread overview]
Message-ID: <20000724081959.B263@mclx.com> (raw)
In-Reply-To: <3979E3BB.1B23FE2@wanadoo.fr>; from costabel@wanadoo.fr on Sat, Jul 22, 2000 at 08:11:07PM +0200
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
On Sat, Jul 22, 2000 at 08:11:07PM +0200, Martin Costabel wrote:
> There *are* situations where you need /usr/src/linux to point to your
> current kernel sources. This is when you compile modules for the current
> kernel, a prominent example being MOL.
Actually, I prefer to add a -I/path/to/kernel/include to the module
makefiles rather than the /usr/src/linux symlink. I suppose it's
personal preference, but I find that having to explicitly specify
where the kernel source is reduces the posibility of a screwed
compile.
--
Josh
6B21489A | GnuPG ID/Fingerprint | huber@mclx.com |
61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
next prev parent reply other threads:[~2000-07-24 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 13:45 problems about __cli() Iain Sandoe
2000-07-20 15:44 ` Josh Huber
2000-07-22 14:10 ` Geert Uytterhoeven
2000-07-22 18:11 ` Martin Costabel
2000-07-24 12:19 ` Josh Huber [this message]
2000-07-24 15:01 ` Jeff Garzik
2000-07-21 14:15 ` Michel Dänzer
-- strict thread matches above, loose matches on Subject: below --
2000-07-21 14:37 Iain Sandoe
2000-07-20 9:19 Iain Sandoe
2000-07-20 12:55 ` Josh Huber
2000-07-20 13:36 ` Michael Schmitz
2000-07-20 7:29 Rolf Liu
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=20000724081959.B263@mclx.com \
--to=huber@mclx.com \
--cc=linuxppc-dev@lists.linuxppc.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.