From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] qemu-system: new host package
Date: Fri, 06 Dec 2013 16:58:42 +0100 [thread overview]
Message-ID: <52A1F432.3010904@mind.be> (raw)
In-Reply-To: <CA+-urNQEcvSey5BhuK0dJhGe07YWk65pmq2Ar4212UMq=ockdQ@mail.gmail.com>
On 06/12/13 02:14, Frank Hunleth wrote:
> On Thu, Dec 5, 2013 at 5:31 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Dear Arnout Vandecappelle,
>>
>> On Thu, 05 Dec 2013 18:49:48 +0100, Arnout Vandecappelle wrote:
>>
>>>>> Yes, I agree, the user mode emulation should probably be removed. It
>>>>> simply cannot work properly, because we have no way of guaranteeing
>>>>> that the kernel headers used for the target toolchain are older than
>>>>> the kernel running on the system.
>>>
>>> It's not possible to do it in Config.in, but it's easy to do during the
>>> build: compare /usr/include/linux/version.h with
>>> $(STAGING_DIR)/usr/include/linux/version.h
>>
>> And then you fail the build if
>> $(STAGING_DIR)/usr/include/linux/version.h gives a newer version
>> of /usr/include/linux/version.h ? Could be possible, even if not really
>> nice. But Fran?ois is proposing to remove cpanminus, which was the only
>> reason to have qemu-user support. So do we care?
>
> I care a little (for as much as that counts), but not enough to argue
> for keeping it if it is becoming a pain. We use qemu-user in a
> post-build step to run a battery of regression tests on algorithmic
> code. It has been convenient since the regression test data is too
> large to run in one pass on the target hardware. It's also faster to
> run on our PCs. I don't think that the regression tests exercise any
> of the issues above.
That seems to me like a valuable use case. But you would need a
Config.in.host for it so it actually becomes visible, right? Care to
contribute that?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-12-06 15:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 0:40 [Buildroot] [RFC PATCH 0/2] host-qemu-system Gustavo Zacarias
2013-12-04 0:40 ` [Buildroot] [PATCH 1/2] qemu-system: new host package Gustavo Zacarias
2013-12-04 8:44 ` Thomas Petazzoni
2013-12-04 10:06 ` Gustavo Zacarias
2013-12-04 12:33 ` Thomas Petazzoni
2013-12-04 12:48 ` Gustavo Zacarias
2013-12-05 17:49 ` Arnout Vandecappelle
2013-12-05 22:31 ` Thomas Petazzoni
2013-12-06 1:14 ` Frank Hunleth
2013-12-06 15:58 ` Arnout Vandecappelle [this message]
2013-12-09 12:15 ` Frank Hunleth
2013-12-09 12:18 ` [Buildroot] [UNSURE]Re: " François Perrad
2013-12-04 0:40 ` [Buildroot] [PATCH 2/2] configs/qemu: update for host-qemu-system goodness Gustavo Zacarias
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=52A1F432.3010904@mind.be \
--to=arnout@mind.be \
--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