From: Sam Ravnborg <sam@ravnborg.org>
To: Philipp Marek <philipp@marek.priv.at>
Cc: Jeff Dike <jdike@addtoit.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: UML dead with current -git?
Date: Thu, 20 Sep 2007 10:26:52 +0200 [thread overview]
Message-ID: <20070920082652.GA9121@uranus.ravnborg.org> (raw)
In-Reply-To: <60355.193.171.152.61.1190273138.squirrel@webmail.marek.priv.at>
On Thu, Sep 20, 2007 at 09:25:38AM +0200, Philipp Marek wrote:
>
> >> > It doesn't handle O= directories...
> >> Sorry, I don't understand you. What are "0=" directories?
> >
> > When building a kernel you can specify an other output directory
> > so you do not mix up your source tree with generated files.
> > To do so do like this:
> >
> > Prepare the stuff:
> > mkdir ~/kernel
> > cp .config ~/kernel
> > make mrproper
> >
> > And then build the kernel:
> > make O=~/kernel
> Oh yes ... thats the character 'o', not the number zero ...
> Sorry, changing the font shows that :-)
>
>
> Yes, that's right. Wouldn't $(srctree) help? That's defined just above, so
> should be fine.
We want a solution that:
- Always use the same ARCH as before
- Error out if user specify another ARCH
- Tell what ARCH is used to user
I will inspired by yprs and other patches try to cook up something.
Hopefully my make-foo suffice.
Sam
next prev parent reply other threads:[~2007-09-20 8:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 15:14 UML dead with current -git? Philipp Marek
2007-09-18 17:13 ` Jeff Dike
2007-09-18 17:55 ` Sam Ravnborg
2007-09-19 1:35 ` Jeff Dike
2007-09-19 12:43 ` Philipp Marek
2007-09-19 15:50 ` Randy Dunlap
2007-09-19 16:17 ` Philipp Marek
2007-09-19 17:47 ` Randy Dunlap
2007-09-20 5:42 ` Ph. Marek
2007-09-20 16:35 ` Randy Dunlap
2007-09-19 18:05 ` Jeff Dike
2007-09-20 5:44 ` Ph. Marek
2007-09-20 7:01 ` Sam Ravnborg
2007-09-20 7:25 ` Philipp Marek
2007-09-20 8:26 ` Sam Ravnborg [this message]
2007-09-18 18:09 ` Philipp Marek
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=20070920082652.GA9121@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp@marek.priv.at \
--cc=randy.dunlap@oracle.com \
/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.