From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] locate the qemu binary in the grub-shell test
Date: Thu, 25 Feb 2010 20:41:15 +0100 [thread overview]
Message-ID: <4B86D25B.8040700@gmail.com> (raw)
In-Reply-To: <1266676133.2348.30.camel@x200>
[-- Attachment #1: Type: text/plain, Size: 2444 bytes --]
Dustin Kirkland wrote:
> The grub-shell test assumes that qemu-system-i386 will be the binary
> used, and that it's available on the system. Actually, on amd64/x86_64
> systems, the appropriate binary is qemu-system-x86_64.
Currently grub-shell supports only i386-pc target and the right qemu
architecture to test it with is system-i386. qemu-system-x86_64 is
appropriate only for amd64-specific tests (you can have a look at my
bootchecks branch). Architecture of build has nothing to do with
architecture of target: you can very well cross-compile for i386-pc from
mips. It's not any different than cross-compiling to i386-pc from x86_64
(the only difference is that you use biarch compiler)
> Furthermore, an
> appropriate error should be thrown if neither executable is found.
>
> 2010-02-20 Dustin Kirkland <kirkland@canonical.com>
>
> * tests/util/grub-shell.in: locate the appropriate qemu system
> binary, and exit non-zero, with an error message, if none are
> found
>
> diff -Nur -x '*.orig' -x '*~' lucid/tests/util/grub-shell.in lucid.new/tests/util/grub-shell.in
> --- lucid/tests/util/grub-shell.in 2010-02-20 07:58:35.062756000 -0600
> +++ lucid.new/tests/util/grub-shell.in 2010-02-20 08:22:07.797858157 -0600
> @@ -92,6 +92,18 @@
> esac
> done
>
> +qemu=
> +for i in qemu-system-i386 qemu-system-x86_64; do
> + if which ${i} >/dev/null; then
> + qemu=${i}
> + break
> + fi
> +done
> +if [ "x${qemu}" = x ]; then
> + echo "qemu is not installed" 1>&2
> + exit 1
> +fi
> +
> if [ "x${source}" = x ] ; then
> tmpfile=`mktemp`
> while read; do
> @@ -135,8 +147,7 @@
> cp ${isofile} ${fdafile}
>
> outfile=`mktemp`
> -qemu-system-i386 ${qemuopts} -nographic -serial stdio -hda ${hdafile} -fda ${fdafile} -cdrom ${isofile} -boot ${bootdev} | tr -d "\r" >${outfile}
> -
> +${qemu} ${qemuopts} -nographic -serial stdio -hda ${hdafile} -fda ${fdafile} -cdrom ${isofile} -boot ${bootdev} | tr -d "\r" >${outfile}
> cat $outfile
>
> rm -f ${tmpfile} ${outfile} ${cfgfile} ${isofile} ${hdafile} ${fdafile}
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2010-02-25 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 14:28 [PATCH] locate the qemu binary in the grub-shell test Dustin Kirkland
2010-02-25 19:41 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-02-25 22:43 ` Anthony Liguori
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=4B86D25B.8040700@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.