qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Leon Alrae <leon.alrae@imgtec.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH 1/3] target-mips: Add n32/n64 configuration files
Date: Wed, 10 Dec 2014 23:25:05 +0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1412102321190.19155@tp.orcam.me.uk> (raw)
In-Reply-To: <CAFEAcA-8wDjTGMQEfE=AqkbR2F=N1JfafffOfxbwP_=EB2vQVw@mail.gmail.com>

On Wed, 10 Dec 2014, Peter Maydell wrote:

> >  Except that apart from coming to an agreement someone has to make it
> > happen yet. ;)
> 
> Ah, but I'm happy with the current state of the codebase...

 Ack.

> >  Fair enough, I want to move forward though.  Would it make you happy if I
> > dropped the new -softmmu configs and made mipsn32|mipsn32el and
> > mipsn64|mipsn64el only accept -user configs instead (failing gracefully
> > rather than abruptly as mipsn32|mipsn32el do now)?
> 
> Er, I'm not sure what you mean there. Trying a softmmu config for
> mipsn32 or mipsn32el fails gracefully already:
> 
> manooth$ (cd build/mips && ../../configure --target-list=mipsn32-softmmu)
> 
> ERROR: Unknown target name 'mipsn32-softmmu'

 It looks like the issue I had in mind has been fixed in a generic way 
then since I last checked.  Previously a build error happened sometime 
along the process.  Apologies for not double-checking with current trunk.  
I'll send updates.

  Maciej

  reply	other threads:[~2014-12-10 23:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 18:53 [Qemu-devel] [PATCH 0/3] MIPS: GDB register width fix / ABI configuration rework Maciej W. Rozycki
2014-12-10 18:53 ` [Qemu-devel] [PATCH 1/3] target-mips: Add n32/n64 configuration files Maciej W. Rozycki
2014-12-10 19:41   ` Peter Maydell
2014-12-10 20:29     ` Maciej W. Rozycki
2014-12-10 21:30       ` Peter Maydell
2014-12-10 22:14         ` Maciej W. Rozycki
2014-12-10 22:54           ` Peter Maydell
2014-12-10 23:25             ` Maciej W. Rozycki [this message]
2014-12-11  9:41               ` Peter Maydell
2014-12-11 14:52                 ` Maciej W. Rozycki
2014-12-10 18:53 ` [Qemu-devel] [PATCH 2/3] target-mips: Rework ABIs to allow all required configurations Maciej W. Rozycki
2014-12-10 18:54 ` [Qemu-devel] [PATCH 3/3] target-mips: Set GDB register widths correctly Maciej W. Rozycki
2014-12-11  0:21 ` [Qemu-devel] [PATCH v2 1/2] target-mips: Rework ABIs to allow all required configurations Maciej W. Rozycki
2014-12-12 18:27   ` [Qemu-devel] [PATCH v3 " Maciej W. Rozycki
2015-02-09 11:30   ` [Qemu-devel] [PATCH v2 " Leon Alrae
2015-02-09 14:09     ` Maciej W. Rozycki
2015-02-09 14:36       ` Peter Maydell
2015-02-11 13:28         ` Maciej W. Rozycki
2014-12-11  0:22 ` [Qemu-devel] [PATCH v2 2/2] target-mips: Set GDB register widths correctly Maciej W. Rozycki

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=alpine.DEB.1.10.1412102321190.19155@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=aurelien@aurel32.net \
    --cc=leon.alrae@imgtec.com \
    --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).