From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Michal Orzel" <michal.orzel@amd.com>,
"Anthony PERARD" <anthony.perard@vates.tech>
Subject: Re: [PATCH 7/8] Infrastructure for arm64 linux builds
Date: Thu, 10 Apr 2025 11:57:23 +0100 [thread overview]
Message-ID: <96fe43c7-e2a6-47d0-bdd7-e6284c86acfa@citrix.com> (raw)
In-Reply-To: <8ef0f462-a487-4d76-84e7-9552c75995b7@citrix.com>
On 10/04/2025 11:41 am, Andrew Cooper wrote:
> On 09/04/2025 6:15 pm, Andrew Cooper wrote:
>> On 09/04/2025 6:11 pm, Marek Marczykowski-Górecki wrote:
>>> On Wed, Apr 09, 2025 at 05:37:01PM +0100, Andrew Cooper wrote:
>>>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>>>> ---
>>>> CC: Roger Pau Monné <roger.pau@citrix.com>
>>>> CC: Stefano Stabellini <sstabellini@kernel.org>
>>>> CC: Michal Orzel <michal.orzel@amd.com>
>>>> CC: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
>>>> CC: Anthony PERARD <anthony.perard@vates.tech>
>>>> ---
>>>> .gitlab-ci.yml | 7 ++++++
>>>> containerize | 1 +
>>>> images/alpine/3.18-arm64-build.dockerfile | 27 +++++++++++++++++++++++
>>>> scripts/build-linux.sh | 10 +++++++++
>>>> 4 files changed, 45 insertions(+)
>>>> create mode 100644 images/alpine/3.18-arm64-build.dockerfile
>>>>
>>>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>>>> index ff8dce7be05d..6e38c2f2a108 100644
>>>> --- a/.gitlab-ci.yml
>>>> +++ b/.gitlab-ci.yml
>>>> @@ -19,6 +19,13 @@ stages:
>>>> exclude:
>>>> - binaries/.gitignore
>>>>
>>>> +.arm64-artifacts:
>>>> + extends: .artifacts
>>>> + tags:
>>>> + - arm64
>>>> + variables:
>>>> + CONTAINER: alpine:3.18-arm64-build
>>> Arm64 kernel used to be built in a Bookworm container.
>> So did x86 before they were moved across.
>>
>>> The build in alpine
>>> has "find: unrecognized: -printf" in the middle of the build. It doesn't
>>> fail outright, but something might be broken. I guess it's related to
>>> initramfs - maybe some option can be disabled, to avoid this message?
>> Nothing seems to break...
>>
>> There's also a bad awk regex. Alpine seem to fix this by using mawk,
>> except they then have to patch the Linux build system to take the
>> override properly.
>>
>> I can't see anything obvious they do to fix this -printf warning.
> Yes I can. We want findutils too.
>
> x86 also wants diffutils too. (as I'm fixing that side of things too)
Excellent. Both x86 and ARM are clean with these changes:
https://gitlab.com/xen-project/hardware/test-artifacts/-/jobs/9682944850
https://gitlab.com/xen-project/hardware/test-artifacts/-/jobs/9682944867
The awk complaint has gone away too, so I suppose that's a knock-on effect.
~Andrew
next prev parent reply other threads:[~2025-04-10 10:58 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 16:36 [PATCH TEST-ARTEFACTS 0/8] Cleanup and Linux ARM64 support Andrew Cooper
2025-04-09 16:36 ` [PATCH 1/8] Consistently use DOCKER_CMD in makefiles Andrew Cooper
2025-04-09 16:36 ` [PATCH 2/8] Port containerise Andrew Cooper
2025-04-10 9:33 ` Anthony PERARD
2025-04-10 9:35 ` Andrew Cooper
2025-04-09 16:36 ` [PATCH 3/8] Fix container user setup Andrew Cooper
2025-04-10 9:41 ` Anthony PERARD
2025-04-09 16:36 ` [PATCH 4/8] Clean up Gitlab yaml Andrew Cooper
2025-04-09 17:15 ` Marek Marczykowski-Górecki
2025-04-10 9:38 ` Andrew Cooper
2025-04-10 10:07 ` Anthony PERARD
2025-04-10 10:11 ` Andrew Cooper
[not found] ` <Z_jid7eTY7EPIoWu@l14>
2025-04-11 9:45 ` Andrew Cooper
2025-04-09 16:36 ` [PATCH 5/8] Adjust Linux build script to work with other major versions Andrew Cooper
2025-04-09 16:57 ` Marek Marczykowski-Górecki
2025-04-09 17:18 ` Andrew Cooper
2025-04-09 16:37 ` [PATCH 6/8] Factor our x86-isms in the linux build script Andrew Cooper
2025-04-09 17:05 ` Marek Marczykowski-Górecki
2025-04-09 22:59 ` Marek Marczykowski-Górecki
2025-04-09 23:04 ` Andrew Cooper
2025-04-09 16:37 ` [PATCH 7/8] Infrastructure for arm64 linux builds Andrew Cooper
2025-04-09 17:11 ` Marek Marczykowski-Górecki
2025-04-09 17:15 ` Andrew Cooper
2025-04-10 10:41 ` Andrew Cooper
2025-04-10 10:57 ` Andrew Cooper [this message]
2025-04-10 12:21 ` Marek Marczykowski-Górecki
2025-04-10 9:59 ` Andrew Cooper
2025-04-09 16:37 ` [PATCH 8/8] Linux 6.6.86 for x86 and arm64 Andrew Cooper
2025-04-09 17:01 ` [PATCH TEST-ARTEFACTS 0/8] Cleanup and Linux ARM64 support Andrew Cooper
2025-04-10 0:09 ` Jason Andryuk
2025-04-10 9:17 ` Andrew Cooper
2025-04-10 18:20 ` Alejandro Vallejo
2025-04-10 18:28 ` Alejandro Vallejo
2025-04-10 19:50 ` [RFC PATCH] x86/xen: Fix PVH dom0 xen_hypercall detection Jason Andryuk
2025-04-10 21:49 ` Andrew Cooper
2025-04-11 11:35 ` Ard Biesheuvel
2025-04-11 14:28 ` Jason Andryuk
2025-04-11 15:32 ` Ard Biesheuvel
2025-04-11 12:46 ` Alejandro Vallejo
2025-04-11 13:08 ` Jan Beulich
2025-04-11 14:10 ` Alejandro Vallejo
2025-04-18 10:58 ` [PATCH TEST-ARTEFACTS 0/8] Cleanup and Linux ARM64 support David Woodhouse
2025-04-10 21:16 ` Jason Andryuk
2025-04-10 21:50 ` Jason Andryuk
2025-04-11 12:41 ` Alejandro Vallejo
2025-04-10 9:32 ` Jürgen Groß
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=96fe43c7-e2a6-47d0-bdd7-e6284c86acfa@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=marmarek@invisiblethingslab.com \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.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.