mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Jeff Dike <jdike@addtoit.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [PATCH] UML - SYSEMU fixes
Date: Mon, 6 Dec 2004 20:17:28 +0100	[thread overview]
Message-ID: <200412062017.29011.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <41B30D6B.3060506@jonmasters.org>

On Sunday 05 December 2004 14:30, Jon Masters wrote:
> 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.

They don't - check_sysemu is used also in TT mode.

> 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.

PPC port is not maintained at the moment - there are some rumors of somebody 
reviving it, but nothing is certain.

> |>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 saw that from someone else - I don't remember what was the problem, but it 
seemed to be some strange kind of .config. Make sure that CONFIG_DEBUG_INFO 
and CONFIG_FRAME_POINTER are both set (the second is the needed one, the 
first implies the second for UML).

"make oldconfig ARCH=um" should fix such problems.

> | I just checked with that config, and it builds fine.

> Oh good. Then it works now.

> Cheers,

> Jon.

-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade

  reply	other threads:[~2004-12-06 19:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 21:45 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
2004-12-06 19:17       ` Blaisorblade [this message]
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=200412062017.29011.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=akpm@osdl.org \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=jdike@addtoit.com \
    --cc=jonathan@jonmasters.org \
    --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

all inboxes | Powered by JetHome®