From: Keith Owens <kaos@ocs.com.au>
To: Mark Mokryn <mark@sangate.com>
Cc: Rafael Herrera <raffo@neuronet.pitt.edu>, linux-kernel@vger.kernel.org
Subject: Re: SMP module compilation on UP?
Date: Thu, 14 Jun 2001 02:50:35 +1000 [thread overview]
Message-ID: <19041.992451035@ocs4.ocs-net> (raw)
In-Reply-To: Your message of "Wed, 13 Jun 2001 17:43:54 +0300." <3B277C2A.B2CC3FCF@sangate.com>
On Wed, 13 Jun 2001 17:43:54 +0300,
Mark Mokryn <mark@sangate.com> wrote:
>Is this the only way - to keep two separately configured kernel source
>trees? No way to do it via some flag?
With 2.4, yes. You need a complete set of kernel source for every set
of config files you use because the object code is written to the
source directory. With 2.5 you can have a single source tree and
multiple object trees, one for each config that you are working on.
In either case you must keep separate sets of objects for each config,
mixing objects from different configs in a single tree is a recipe for
disaster.
next prev parent reply other threads:[~2001-06-13 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 13:42 SMP module compilation on UP? Mark Mokryn
2001-06-13 15:25 ` Rafael Herrera
2001-06-13 14:43 ` Mark Mokryn
2001-06-13 16:50 ` Keith Owens [this message]
2001-06-14 17:27 ` Kurt Garloff
2001-06-13 16:42 ` Keith Owens
2001-06-13 21:14 ` Khalid Aziz
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=19041.992451035@ocs4.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@sangate.com \
--cc=raffo@neuronet.pitt.edu \
/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;
as well as URLs for NNTP newsgroup(s).