From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/7] support/scripts/qemu-boot: gitlab tests for Qemu
Date: Tue, 30 Apr 2019 21:40:33 +0200 [thread overview]
Message-ID: <20190430194033.GE27252@scaer> (raw)
In-Reply-To: <4368e67d-3b86-9566-2fac-28c247dce4b6@mind.be>
Arnout, All,
On 2019-04-30 13:20 +0200, Arnout Vandecappelle spake thusly:
> On 30/04/2019 10:54, Jugurtha BELKALEM wrote:
> > Thank you for you comments Arnout, I have corrected the indentation, timeout
> > and? function declaration issues.
> >
> > However; I think that duplicating the content of readme.txt of each qemu
> > architecture would be difficult to maintain (even if it is more convenient to
> > use), this is why a project like toolchain builder :
> > https://github.com/bootlin/toolchains-builder/blob/master/build.sh is reading
> > directly from readme.txt.
>
> The idea would not be to duplicate it, but to move it. I.e., readme.txt just
> says "launch with board/qemu/x86_64/launch.sh", and the actual command is in
> that shell script.
>
> But maybe we should see what other Buildroot maintainers have to say about it.
> Thomas, Peter, Yann, Romain?
Ideally, I'd go without the readme.txt altogether, or if we want to keep
"backward compatibility", we'd make it a symlink to launch.sh.
Snf then, launch.sh would be an actual shell script that also contains
the readme (possibly as -h).
> > > > +? elif [ $device_name == "xtensa-lx60" ] || [ $device_name ==
> > "xtensa-lx60-nommu" ]; then
> > > > +? ? echo "xtensa cannot be tested"
> > >? If that is the case, why do we even have these qemu defconfigs? Max?
> > Tested both configurations just now, with the current buildroot tip
> > (2019.02-959-gd54b0e22aef3) and QEMU-4.0. Both build and boot for me
> > with QEMU command line from the readme.
> Is this with the system-intalled qemu? I guess so, because Buildroot still has
> 3.1.0... That might be the issue :-)
I've started a test-build ehre, to check.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-04-30 19:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 16:32 [Buildroot] [PATCH 0/7] gitlab Qemu runtime testing Jugurtha BELKALEM
2019-04-29 16:32 ` [Buildroot] [PATCH 1/7] support/docker/Dockerfile: new package expect Jugurtha BELKALEM
2019-04-29 20:49 ` Arnout Vandecappelle
2019-04-29 16:32 ` [Buildroot] [PATCH 2/7] package/qemu: enable nios2 support for host-qemu Jugurtha BELKALEM
2019-04-29 16:32 ` [Buildroot] [PATCH 3/7] package/qemu: enable sparc64 " Jugurtha BELKALEM
2019-04-29 16:32 ` [Buildroot] [PATCH 4/7] package/qemu: remove comment about sh64 Jugurtha BELKALEM
2019-04-29 16:32 ` [Buildroot] [PATCH 5/7] configs/qemu-*: add host-qemu-system Jugurtha BELKALEM
2019-04-29 16:32 ` [Buildroot] [PATCH 6/7] support/scripts/qemu-boot: gitlab tests for Qemu Jugurtha BELKALEM
2019-04-29 22:31 ` Arnout Vandecappelle
2019-04-29 23:38 ` Max Filippov
2019-04-30 8:54 ` Jugurtha BELKALEM
2019-04-30 11:20 ` Arnout Vandecappelle
2019-04-30 15:40 ` Max Filippov
2019-04-30 19:40 ` Yann E. MORIN [this message]
2019-04-30 19:56 ` Yann E. MORIN
2019-04-30 20:09 ` Max Filippov
2019-04-30 20:23 ` Max Filippov
2019-04-30 20:31 ` Yann E. MORIN
2019-05-01 9:35 ` Arnout Vandecappelle
2019-04-29 16:32 ` [Buildroot] [PATCH 7/7] gitlab.yml.in: enable Qemu gitlab testing Jugurtha BELKALEM
2019-04-29 22:34 ` 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=20190430194033.GE27252@scaer \
--to=yann.morin.1998@free.fr \
--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