From: Jon Masters <jonathan@jonmasters.org>
To: Jeff Dike <jdike@addtoit.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
Blaisorblade <blaisorblade_spam@yahoo.it>,
Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [PATCH] UML - SYSEMU fixes
Date: Sun, 05 Dec 2004 13:30:19 +0000 [thread overview]
Message-ID: <41B30D6B.3060506@jonmasters.org> (raw)
In-Reply-To: <200412050819.iB58Jlhj006511@ccure.user-mode-linux.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeff Dike wrote:
| jonmasters@gmail.com said:
|
|>That's great, but do any of these patches address various undefines in
|>arch/um/kernel/process.c:check_sysemu when built without skas?
|
|
| Apparently they did. I just checked with skas turned off and got a
successful
| build.
Good. I've got a working build on an Intel box but it's being more
stubburn building for ppc in 2.6.9 - I'll post an update when I've
actually looked at it.
|>Also, on 2.6.9, I get dud CFLAGS defined when CONFIG_PROF is set *and*
|>CONFIG_FRAME_POINTER is also set - gcc complains about use of "-gp"
|>and "-fomit-frame-pointer" but surely it should be building with frame
|>pointers anyway if I've asked it to do so?
|
|
| I just checked with that config, and it builds fine.
Oh good. Then it works now.
Cheers,
Jon.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBsw1reTyyexZHHxERAs34AJ9yXOHe84a73sy81zC3hfSApH67NwCfZPlq
xWiHY1jlmBPftJeIfgtbur4=
=NxJe
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-12-05 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 21:45 [PATCH] UML - SYSEMU fixes Jeff Dike
2004-12-04 11:28 ` Jon Masters
2004-12-04 11:35 ` Jon Masters
2004-12-05 8:19 ` Jeff Dike
2004-12-05 13:30 ` Jon Masters [this message]
2004-12-06 19:17 ` Blaisorblade
2004-12-06 23:56 ` Jon Masters
2004-12-07 0:36 ` Blaisorblade
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=41B30D6B.3060506@jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=jdike@addtoit.com \
--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 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.