qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] configure: Ensure tests/qemu-iotests exists before writing common.env
Date: Wed, 14 May 2014 16:32:07 +0200	[thread overview]
Message-ID: <20140514143207.GL3610@noname.redhat.com> (raw)
In-Reply-To: <1400077612-28488-1-git-send-email-peter.maydell@linaro.org>

Am 14.05.2014 um 16:26 hat Peter Maydell geschrieben:
> Before we write common.env to the tests/qemu-iotests directory, ensure
> that it exists. This fixes out-of-tree builds from clean.
> 
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> If somebody would like to review this I'll apply it to master as
> a buildfix...
> 
>  configure | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/configure b/configure
> index 6adfa72..c4e43ed 100755
> --- a/configure
> +++ b/configure
> @@ -4770,6 +4770,7 @@ fi
>  
>  iotests_common_env="tests/qemu-iotests/common.env"
>  
> +mkdir -p "$(dirname "$iotests_common_env")"
>  echo "# Automatically generated by configure - do not modify" > $iotests_common_env
>  echo >> $iotests_common_env
>  echo "PYTHON='$python'" >> $iotests_common_env

We already have an mkdir -p, in the section at line 5161ff. Perhaps we
should just move that to further above?

But as this is a build fix, I don't want to start bikeshedding, so I'm
not objecting to your patch.

Kevin

  reply	other threads:[~2014-05-14 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 14:26 [Qemu-devel] [PATCH] configure: Ensure tests/qemu-iotests exists before writing common.env Peter Maydell
2014-05-14 14:32 ` Kevin Wolf [this message]
2014-05-14 14:46   ` Peter Maydell
2014-05-14 14:54     ` Kevin Wolf
2014-05-14 22:47 ` Max Reitz
2014-05-15  8:15   ` Peter Maydell

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=20140514143207.GL3610@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).