From: Olaf Hering <olh@suse.de>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: chandrasekhar.nagaraj@patni.com, linux-kernel@vger.kernel.org
Subject: Re: Read Hat 7.3 and 8.0 compilation problems
Date: Tue, 18 Mar 2003 21:39:27 +0100 [thread overview]
Message-ID: <20030318203927.GA23822@suse.de> (raw)
In-Reply-To: <1047904177.1596.1.camel@laptop.fenrus.com>
On Mon, Mar 17, Arjan van de Ven wrote:
> > But if we compile the driver using the include souces
> > /usr/src/linux-2.4/include we do not get any compilation errors.
>
> the "standardized between all distros and Linus" place to get headers is
> /lib/modules/`uname -r`/build/include
What moron declared that as 'standard'?
uname -r is as reliable as /etc/mtab
--
USB is for mice, FireWire is for men!
next prev parent reply other threads:[~2003-03-18 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 12:47 Read Hat 7.3 and 8.0 compilation problems chandrasekhar.nagaraj
2003-03-17 12:29 ` Arjan van de Ven
2003-03-18 20:39 ` Olaf Hering [this message]
2003-03-17 12:32 ` Heinz Ulrich Stille
2003-03-17 13:46 ` Dave Jones
2003-03-17 13:51 ` John Bradford
[not found] ` <mailman.1047904680.20757.linux-kernel2news@redhat.com>
2003-03-17 20:00 ` Pete Zaitcev
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=20030318203927.GA23822@suse.de \
--to=olh@suse.de \
--cc=arjanv@redhat.com \
--cc=chandrasekhar.nagaraj@patni.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