Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] QEMU: Enable package for MIPS targets
Date: Mon, 27 Apr 2015 08:50:43 +0100	[thread overview]
Message-ID: <553DEA53.7070803@imgtec.com> (raw)
In-Reply-To: <20150425101806.382e8c2b@free-electrons.com>

On 04/25/2015 09:18 AM, Thomas Petazzoni wrote:
> Dear Markos Chandras,
> 
> On Thu, 23 Apr 2015 10:50:57 +0100, Markos Chandras wrote:
> 
>> diff --git a/package/qemu/Config.in b/package/qemu/Config.in
>> index fff786d3f11f..f537ce67181c 100644
>> --- a/package/qemu/Config.in
>> +++ b/package/qemu/Config.in
>> @@ -1,11 +1,16 @@
>> +config BR2_PACKAGE_QEMU_ARCH_SUPPORTS_TARGET
>> +	bool
>> +	# Only tested in these architectures
>> +	default y if BR2_i386 || BR2_mips || BR2_mipsel || BR2_x86_64
> 
> So not on mips64/mips64el...

No because it does not seem to (cross-)build for mips64.

> 
>> -#       mips64          ?
>> -#       mips64el        ?
>> +#       mips64          mips64
>> +#       mips64el        mips64el
> 
> but you update the mips64* information, which would probably indicate
> that it works, no?

I was not sure what that list is for. I just added the missing targets
there. You can still get a mips64(el) targets on a mips host though.

> 
> Anyway, I've applied the patch as is, feel free to send a follow-up
> patch adding mips64* as well if that works.

Yes we will eventually fix the build problems upstream. Thanks!

-- 
markos

  reply	other threads:[~2015-04-27  7:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23  9:50 [Buildroot] [PATCH 1/2] QEMU: bump to 2.2.1 Markos Chandras
2015-04-23  9:50 ` [Buildroot] [PATCH 2/2] QEMU: Enable package for MIPS targets Markos Chandras
2015-04-25  8:18   ` Thomas Petazzoni
2015-04-27  7:50     ` Markos Chandras [this message]
2015-04-23 15:43 ` [Buildroot] [PATCH 1/2] QEMU: bump to 2.2.1 Thomas Petazzoni

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=553DEA53.7070803@imgtec.com \
    --to=markos.chandras@imgtec.com \
    --cc=buildroot@busybox.net \
    /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