From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Javi Merino" <javi.merino@cloud.com>
Cc: xen-devel@lists.xenproject.org,
"Doug Goldstein" <cardoe@cardoe.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: [XEN PATCH v1 4/6] CI: Refresh the Debian 12 arm32 cross compile container
Date: Thu, 24 Oct 2024 11:51:17 +0000 [thread overview]
Message-ID: <Zxo0s72TBQtuWTXS@l14> (raw)
In-Reply-To: <762312efd58aa1b41cfcb5439f2fd35580b8bba6.1729760501.git.javi.merino@cloud.com>
On Thu, Oct 24, 2024 at 11:04:19AM +0100, Javi Merino wrote:
> diff --git a/automation/build/debian/12-arm64v8-arm32-gcc.dockerfile b/automation/build/debian/12-arm64v8-arm32-gcc.dockerfile
> new file mode 100644
> index 000000000000..bdc935706bfa
> --- /dev/null
> +++ b/automation/build/debian/12-arm64v8-arm32-gcc.dockerfile
> @@ -0,0 +1,28 @@
> +# syntax=docker/dockerfile:1
> +FROM --platform=linux/arm64/v8 debian:bookworm
> +LABEL maintainer.name="The Xen Project" \
> + maintainer.email="xen-devel@lists.xenproject.org"
Recent update of other dockerfile was repeating the "LABEL" intruction
for each label, maybe we should continue to do that (which avoid the
backslash at the end of lines).
> +
> +ENV DEBIAN_FRONTEND=noninteractive
> +ENV CROSS_COMPILE /usr/bin/arm-linux-gnueabihf-
While the syntax "ENV VAR value" is supported, it's been discouraged by
docker's doc (https://docs.docker.com/reference/dockerfile/#env). Also,
here we have two ENV instructions with two different syntax, could you
use the = for declaring CROSS_COMPILE as well?
Thanks,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2024-10-24 11:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 10:04 [XEN PATCH v1 0/6] automation: Refresh the remaining Debian containers Javi Merino
2024-10-24 10:04 ` [XEN PATCH v1 1/6] CI: Refresh the Debian 12 x86_64 container Javi Merino
2024-10-24 14:04 ` Andrew Cooper
2024-10-24 15:10 ` Javi Merino
2024-10-25 14:46 ` Andrew Cooper
2024-11-04 15:40 ` Javi Merino
2024-10-24 10:04 ` [XEN PATCH v1 2/6] CI: Refresh the Debian 12 x86_32 container Javi Merino
2024-10-24 13:04 ` Javi Merino
2024-10-24 10:04 ` [XEN PATCH v1 3/6] CI: Refresh the Debian 12 arm64 container Javi Merino
2024-10-24 23:03 ` Stefano Stabellini
2024-11-04 16:17 ` Javi Merino
2024-10-24 10:04 ` [XEN PATCH v1 4/6] CI: Refresh the Debian 12 arm32 cross compile container Javi Merino
2024-10-24 11:51 ` Anthony PERARD [this message]
2024-10-24 12:59 ` Javi Merino
2024-10-24 10:04 ` [XEN PATCH v1 5/6] CI: Refresh the Debian 12 cppcheck container Javi Merino
2024-10-24 23:11 ` Stefano Stabellini
2024-10-24 10:04 ` [XEN PATCH v1 6/6] CI: Run the builds and tests that use the Debian 12 containers as a normal user Javi Merino
2024-10-24 23:47 ` Stefano Stabellini
2024-10-29 17:18 ` Javi Merino
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=Zxo0s72TBQtuWTXS@l14 \
--to=anthony.perard@vates.tech \
--cc=cardoe@cardoe.com \
--cc=javi.merino@cloud.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.