From: bernd@petrovitsch.priv.at (Bernd Petrovitsch)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [uml-user] Questions about User Mode Linux
Date: Fri, 14 Oct 2011 12:08:37 +0200 [thread overview]
Message-ID: <1318586918.32705.5.camel@thorin> (raw)
In-Reply-To: <4E98061A.1040704@nod.at>
Ooops, sorry, forget the full CC:
On Fre, 2011-10-14 at 11:51 +0200, Richard Weinberger wrote:
> Am 14.10.2011 07:29, schrieb michi1 at michaelblizek.twilightparadox.com:
> > I have attached the trace below, if you are interested. It happened
> > during/after /sbin/init was executed. Version is
> > f2c0d0266cc5eb36a4aa44944b4096ec121490aa of linus'es git tree. However,
> > everything is running now. It was caused by uncleaned files. I am just
> > reporting, because this was suprising to me.
[....]
> >> "make clean ARCH=um" works fine on my system.
> >
> > Yes, the point is "ARCH=um". I do not really understand why it is needed for
> > clean operations?
>
> Otherwise kbuild will use x86 as arch.
The question is IMHO more in the direction of:
Shouldn't `make mrproper` delete *all* generated files from all
architectures (and not only the current one) to get the tree in a (or
actually the) pristine state?
Hmm, how are other arches handling that?
Bernd
--
Bernd Petrovitsch Email : bernd at petrovitsch.priv.at
LUGA : http://www.luga.at
next prev parent reply other threads:[~2011-10-14 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 11:15 Questions about User Mode Linux jiangtao.jit
2011-10-12 15:25 ` michi1 at michaelblizek.twilightparadox.com
2011-10-12 17:32 ` michi1 at michaelblizek.twilightparadox.com
2011-10-12 18:04 ` Jonathan Neuschäfer
2011-10-13 18:10 ` michi1 at michaelblizek.twilightparadox.com
[not found] ` <4E973255.90402@nod.at>
2011-10-14 5:29 ` michi1 at michaelblizek.twilightparadox.com
[not found] ` <4E98061A.1040704@nod.at>
2011-10-14 10:08 ` Bernd Petrovitsch [this message]
2011-10-13 10:53 ` tao jiang
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=1318586918.32705.5.camel@thorin \
--to=bernd@petrovitsch.priv.at \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).