From: Jan Kiszka <jan.kiszka@siemens.com>
To: Florian Bezdeka <florian.bezdeka@siemens.com>, xenomai@lists.linux.dev
Subject: Re: [PATCH 0/2] Use Debian bookworm for CI build jobs
Date: Fri, 6 Oct 2023 19:27:31 +0200 [thread overview]
Message-ID: <12213afe-70f1-418f-9997-1f9416933f50@siemens.com> (raw)
In-Reply-To: <91c0fafe-7c43-4555-9004-fbe5eb43605a@siemens.com>
On 06.10.23 18:50, Jan Kiszka wrote:
> On 05.10.23 10:50, Florian Bezdeka wrote:
>> Hi all,
>>
>> Disclaimer: This series is completely untested. I have no infrastructure
>> at hand to test modifications to .gitlab-ci.yml. The Xenomai
>> hackerspace hosted on gitlab.com is unable to execute CI jobs
>> (currently).
>>
>> The series does two things:
>> - Move from Debian bullseye to Debian bookworm for all build jobs
>> - Add one more build job to still cover building against libc versions
>> that do not provide y2038 support for 32 bit applications.
>>
>> Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
>> ---
>> Florian Bezdeka (2):
>> ci: Switch to Debian bookworm
>> ci: Add build test for older glibc where y2038 support is not available
>>
>> .gitlab-ci.yml | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>> ---
>> base-commit: aaea684b95331336f0a04b9d15f8f24552e64d7d
>> change-id: 20231005-flo-ci-to-bookworm-9d7672d6f642
>>
>> Best regards,
>
> Thanks, applied. Means, it's being tested now...
>
I had to set GCC_VERSION as well, but now it seems to run.
Jan
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2023-10-06 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 8:50 [PATCH 0/2] Use Debian bookworm for CI build jobs Florian Bezdeka
2023-10-05 8:50 ` [PATCH 1/2] ci: Switch to Debian bookworm Florian Bezdeka
2023-10-05 8:50 ` [PATCH 2/2] ci: Add build test for older glibc where y2038 support is not available Florian Bezdeka
2023-10-06 16:50 ` [PATCH 0/2] Use Debian bookworm for CI build jobs Jan Kiszka
2023-10-06 17:27 ` Jan Kiszka [this message]
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=12213afe-70f1-418f-9997-1f9416933f50@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=xenomai@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).