From: Eric Blake <eblake@redhat.com>
To: Leonid Bloch <lbloch@janustech.com>,
Markus Armbruster <armbru@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Kevin Wolf" <kwolf@redhat.com>,
"Alberto Garcia" <berto@igalia.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"Stefan Weil" <sw@weilnetz.de>, "Max Reitz" <mreitz@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/1] include: Auto-generate the sizes lookup table
Date: Thu, 10 Jan 2019 07:33:45 -0600 [thread overview]
Message-ID: <1551373d-91fa-1345-1757-7299b073d157@redhat.com> (raw)
In-Reply-To: <d0736347-867d-49f5-5615-dfe5f9b82412@janustech.com>
[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]
On 1/10/19 3:42 AM, Leonid Bloch wrote:
> If you've noticed, the original script was in AWK. But to be as generic
> as possible, I didn't write the generation script in AWK because even
> AWK is not guaranteed to be installed on the build system. The only
> interpreted language that is guaranteed to be there is shell (most basic
> shell) because .configure itself needs it.
>
> Sure, the script could be prettier and shorter, but I wanted to keep it
> compatible with the most basic shell, not only Bash, and without needing
> external programs.
awk is portable - autoconf-generated scripts assume it exists (same as
sed, grep, ls, ...) if you have a /bin/sh. In fact, the GNU Coding
Standards has a nice list of programs that you can blindly assume exist.
It's true you may have to use a lowest-common-denominator when using
the tools that are globally available to be portable (not all awk
scripts are portable, even if awk is universally available on systems
with a Bourne-like shell). So avoiding awk on the grounds that it might
not be present is the wrong approach.
> Eric - thanks for the comment about 'local' - I will get rid of it if we
> decide to include this patch.
I'm still not convinced we need it. I would much rather see a patch
that makes QemuOpt accept default integer values as integers rather than
as strings, so we don't have to worry about stringifying special macros.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-10 13:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 21:33 [Qemu-devel] [PATCH v2 0/1] include: Auto-generate the sizes lookup table Leonid Bloch
2019-01-03 21:33 ` [Qemu-devel] [PATCH v2 1/1] " Leonid Bloch
2019-01-08 9:31 ` Markus Armbruster
2019-01-08 15:19 ` Eric Blake
2019-01-10 9:42 ` Leonid Bloch
2019-01-10 12:40 ` Markus Armbruster
2019-01-10 16:49 ` Leonid Bloch
2019-01-10 19:11 ` Markus Armbruster
2019-01-10 13:33 ` Eric Blake [this message]
2019-01-10 19:33 ` Eric Blake
2019-01-08 12:20 ` Kevin Wolf
2019-01-10 10:04 ` Leonid Bloch
2019-01-10 12:51 ` Markus Armbruster
2019-01-10 16:53 ` Leonid Bloch
2019-01-11 7:50 ` Markus Armbruster
2019-01-11 15:29 ` Eric Blake
2019-01-10 12:51 ` Alberto Garcia
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=1551373d-91fa-1345-1757-7299b073d157@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=lbloch@janustech.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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;
as well as URLs for NNTP newsgroup(s).