From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] scripts/update-linux-headers.sh: Remove temporary directory inbetween
Date: Mon, 27 May 2024 17:04:22 +0200 [thread overview]
Message-ID: <871q5npa89.fsf@redhat.com> (raw)
In-Reply-To: <20240527060243.12647-1-thuth@redhat.com>
On Mon, May 27 2024, Thomas Huth <thuth@redhat.com> wrote:
> We are reusing the same temporary directory for installing the headers
> of all targets, so there could be stale files here when switching from
> one target to another. Make sure to delete the folder before installing
> a new set of target headers into it.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> scripts/update-linux-headers.sh | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/scripts/update-linux-headers.sh b/scripts/update-linux-headers.sh
> index 8963c39189..fbf7e119bc 100755
> --- a/scripts/update-linux-headers.sh
> +++ b/scripts/update-linux-headers.sh
> @@ -112,6 +112,7 @@ for arch in $ARCHLIST; do
> arch_var=ARCH
> fi
>
> + rm -rf "$hdrdir"
> make -C "$linux" O="$blddir" INSTALL_HDR_PATH="$hdrdir" $arch_var=$arch headers_install
>
> rm -rf "$output/linux-headers/asm-$arch"
Hm. I presume that headers-install gives us the same set of headers
outside include/asm for every arch?
next prev parent reply other threads:[~2024-05-27 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 6:02 [PATCH] scripts/update-linux-headers.sh: Remove temporary directory inbetween Thomas Huth
2024-05-27 15:04 ` Cornelia Huck [this message]
2024-05-27 15:35 ` Thomas Huth
2024-05-27 15:43 ` Cornelia Huck
2024-05-28 15:56 ` Michael S. Tsirkin
2024-05-28 17:40 ` Thomas Huth
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=871q5npa89.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 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.