Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] qemu-system: new package
Date: Thu, 16 Oct 2014 10:53:26 -0300	[thread overview]
Message-ID: <543FCDD6.9070104@zacarias.com.ar> (raw)
In-Reply-To: <543EA87A.2050204@mind.be>

On 10/15/2014 02:01 PM, Arnout Vandecappelle wrote:

>  Can you explain why not?
> 
>  You cannot use different versions for qemu-user and qemu-system in a clean way
> if they're not different packages. But host and target versions don't need to be
> the same. At least, I see code in pkg-generic.mk to handle that.

Well, not really, for example try modifying package/e2fsprogs.mk:
HOST_E2FSPROGS_VERSION = 1.42.13

And build both, see what happens.
Even try a make source with that.

>  And I do think we want to keep qemu-user and qemu-system at the same version,
> right? Or does it happen that you need different versions for these as well?
> 
>  The real question is how to make the version depend on the values in
> BR2_PACKAGE_QEMU_CUSTOM_TARGETS. But that is not the concern of your patch.

No, that's a wrong assumption.
For example qemu_mpc8544ds_defconfig doesn't work with the latest 2.1.2
qemu, however other qemu ppc sample defconfigs do (in fact no 2.1.x
version).
And the qemu config should dictate what's the best version for each -
not necessarily the latest, you can't make host-qemu-user depend on that
since it's a platform decision, not an arch one.
If you want to stick with "the one that works for everything" you
potentially miss the opportunity for new arch and/or platform support.
So even if target != host version is fixed/possible you'll still clash
on host-qemu (user) vs. host-qemu (system) versions since you might want
to do the perl module dance (original purpose of host-qemu) vs. platform
emulation.
It's nice to keep everything in one package, but it's not feasible to do
so in a coherent way for this case in particular.
If you can't get the leash out of the qemu version there's no point in
building so for the emulation, sometimes you'll ship every single qemu
config working, sometimes you wont - and that's my quarrel, everyone is
perfect-this perfect-that but all of the sudden this would be acceptable?
Like i said it would be the same as $RANDOM distro qemu.
Regards.

  reply	other threads:[~2014-10-16 13:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-03 20:20 [Buildroot] [PATCH 1/3] qemu-system: new package Gustavo Zacarias
2014-05-03 20:20 ` [Buildroot] [PATCH 2/3] configs/qemu: update for host-qemu-system Gustavo Zacarias
2014-05-03 20:20 ` [Buildroot] [PATCH 3/3] configs/qemu: bump relevant kernel/header versions Gustavo Zacarias
2014-10-12 15:17 ` [Buildroot] [PATCH 1/3] qemu-system: new package Thomas Petazzoni
2014-10-12 19:03   ` Gustavo Zacarias
2014-10-15 17:01     ` Arnout Vandecappelle
2014-10-16 13:53       ` Gustavo Zacarias [this message]
2014-10-17 22:47         ` Arnout Vandecappelle
2014-10-18  1:14           ` Gustavo Zacarias
2014-10-19 20:27             ` Arnout Vandecappelle
2014-10-19 20:54               ` Thomas Petazzoni
2014-10-20  1:53                 ` Gustavo Zacarias
2014-10-20 19:41                   ` Arnout Vandecappelle
2014-10-20 21:16                     ` Thomas Petazzoni
2014-10-20 22:45                       ` Gustavo Zacarias
2014-10-21  7:16                         ` Thomas Petazzoni
2014-10-21 18:20                           ` Yann E. MORIN
2014-10-22 10:23                             ` Peter Korsgaard
2014-10-21 19:45                           ` Arnout Vandecappelle

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=543FCDD6.9070104@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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