From: David Woodhouse <dwmw2@infradead.org>
To: Alessandro Amici <alexamici@tiscali.it>
Cc: linux-kernel@vger.kernel.org, James.Bottomley@HansenPartnership.com
Subject: Re: 2.5.37+ i386 arch split broke external module builds
Date: Wed, 02 Oct 2002 12:28:03 +0100 [thread overview]
Message-ID: <4631.1033558083@passion.cambridge.redhat.com> (raw)
In-Reply-To: <20021002103932.C35A21EA74@alan.localdomain>
alexamici@tiscali.it said:
> in order to access the kernel interfaces, modules that live outside
> the kernel sources were used to only need: CFLAG += -I$(TOPDIR)/
> include
That was broken anyway -- you always got the CFLAGS wrong if you just did
that. The only way that I only of to get the CFLAGS to match the kernel
build reliably is to do something like:
make -C /lib/modules/`uname -r`/build SUBDIRS=`pwd` modules
--
dwmw2
next prev parent reply other threads:[~2002-10-02 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 10:39 2.5.37+ i386 arch split broke external module builds Alessandro Amici
2002-10-02 11:28 ` David Woodhouse [this message]
2002-10-02 21:06 ` Alessandro Amici
2002-10-02 21:13 ` David Woodhouse
2002-10-02 22:09 ` James Bottomley
2002-10-02 23:49 ` Alessandro Amici
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=4631.1033558083@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alexamici@tiscali.it \
--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