From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: udev build failing in aarch64 builder
Date: Wed, 14 May 2025 16:08:16 +0100 [thread overview]
Message-ID: <23057E82-1952-4999-ABD4-B2ED465D3335@ipfire.org> (raw)
In-Reply-To: <65cdb2f8-89a4-4062-9d46-530a256e6ea4@ipfire.org>
Hello Adolf,
I noticed that the build failed and hoped this would be a random one-off problem. Turns out it is not.
I looked through the log and it seems that some libraries don’t seem to be built with GCS (GNU Compiler Security).
When I upgraded to GCC 15 I built the entire distribution, so I am a little surprised that this is now happening in next. But that is what the branch is for.
I will have to run a build on my build system and investigate. Not a clue what could be causing this.
As soon as I have something I will report back.
-Michael
> On 14 May 2025, at 12:18, Adolf Belka <adolf.belka@ipfire.org> wrote:
>
> Hi All,
>
> I have done an update build of boost on my home x86_64 system. As boost has different rootfiles for aarch64 and riscv64 I also ran builds on the aarch64 and riscv64 builders.
>
> The aarch64 builder failed when building udev, which is before my boost change so shouldn't be influenced by it. I repeated the build just in case but it failed again.
>
> I restored the boost lfs file and then built again and it failed again.
>
> The riscv64 had no problems building udev and also not on my x86_64 system.
>
> The udev build log is around 4,500 lines long so I have put it in IPFire NoPaste.
>
> https://nopaste.ipfire.org/view/GcfWtEyc
>
> Regards,
>
> Adolf.
>
>
>
next prev parent reply other threads:[~2025-05-14 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 11:18 Adolf Belka
2025-05-14 15:08 ` Michael Tremer [this message]
2025-05-14 16:49 ` Michael Tremer
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=23057E82-1952-4999-ABD4-B2ED465D3335@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox