qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Alexander Graf" <agraf@suse.de>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [Bug 929638] Re: qemu 1.0 unable to compile on the pandaboard ES
Date: Thu, 9 Feb 2012 19:18:25 +0000	[thread overview]
Message-ID: <201202091918.26231.paul@codesourcery.com> (raw)
In-Reply-To: <7568D61C-0763-4A4A-9FB0-7F0F60D3C788@suse.de>

> > On ARM Linux glibc provides a makecontext() that always fails ENOSYS,
> > so our configure test thinks there is makecontext support but when we
> > try to use it for coroutines it will fail and we abort.
> > 
> > I have a workaround in qemu-linaro that just forces the makecontext
> > test to fail on ARM but I don't like that much. It would be better
> > to either drop our requirement for makecontext (Paolo had some patches
> > to try to do this IIRC) or to handle it failing at runtime.
> 
> Or make the configure test be an execution test and always disable it for
> cross-compile?

I'd rather not.  If at all possible we should avoid runtime tests.  Even for 
"native" systems they generally give the wrong answer as the machine you're 
building on often isn't the one you will be running on.  If we know arm hosts 
are broken then that's what we should test for in configure (with a comment 
saying why).

IMO consistency between builds for the same target environment is more 
important than opportunistically probing in a native builds.

Paul

  parent reply	other threads:[~2012-02-09 19:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 16:37 [Qemu-devel] [Bug 929638] [NEW] qemu 1.0 unable to compile on the pandaboard ES Marietto
2012-02-09 16:55 ` [Qemu-devel] [Bug 929638] " Marietto
2012-02-09 17:07 ` Peter Maydell
2012-02-09 18:23   ` Andreas Färber
2012-02-09 19:11     ` Peter Maydell
2012-02-09 19:12       ` Alexander Graf
2012-02-09 19:15         ` Peter Maydell
2012-02-09 19:17           ` Alexander Graf
2012-02-09 19:18         ` Paul Brook [this message]
2012-02-09 19:21           ` Alexander Graf
2012-02-09 23:55             ` Paul Brook
2012-02-09 22:39       ` Andreas Färber
2012-02-09 18:55 ` Marietto
2012-07-10 14:59 ` Peter Maydell
2012-08-03 17:17 ` Samuel Bronson
2012-09-06  6:23   ` Marietto

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=201202091918.26231.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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).