From: Keith Owens <kaos@ocs.com.au>
To: David Hinds <dhinds@sonic.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.19 aic7xxx breaks pcmcia
Date: Tue, 27 Mar 2001 08:20:53 +1000 [thread overview]
Message-ID: <6041.985645253@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 26 Mar 2001 08:48:09 PST." <20010326084809.A11493@sonic.net>
On Mon, 26 Mar 2001 08:48:09 -0800,
David Hinds <dhinds@sonic.net> wrote:
>On Mon, Mar 26, 2001 at 05:14:13PM +1000, Keith Owens wrote:
>What are the things you're planning that will cause trouble?
Support for building third party drivers and patch sets as separate
source trees. Base kernel in in one source tree, external patch or
driver set is in another source tree, kbuild reads from multiple source
trees and writes to a separate object directory. The multiple source
trees break the assumption that all source is in one tree, lines like
#include <../drivers/scsi/aic7xxx.h>
do not work with multiple sources.
You are right about the long compile lines though, example with three
source trees, reflowed for readability.
/usr/bin/kgcc -I /build/kaos/2.4.1-object-kdb/arch/i386/kernel/
-I /build/kaos/kdb/arch/i386/kernel/
-I /build/kaos/common/arch/i386/kernel/
-I /build/kaos/2.4.1-makefile-2.5/arch/i386/kernel/ -I-
-D__ASSEMBLY__ -D__KERNEL__ -I include -I .tmp_include/src_002
-I .tmp_include/src_001 -I .tmp_include/src_000 -traditional -c
-o arch/i386/kernel/trampoline.o
/build/kaos/2.4.1-makefile-2.5/arch/i386/kernel/trampoline.S
prev parent reply other threads:[~2001-03-26 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 7:14 2.2.19 aic7xxx breaks pcmcia Keith Owens
2001-03-26 16:48 ` David Hinds
2001-03-26 22:20 ` Keith Owens [this message]
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=6041.985645253@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=dhinds@sonic.net \
--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