Re: udev build failing in aarch64 builder

[Michael Tremer <michael.tremer@ipfire.org>]

Hello,

My build reached the problem really quickly.

I think it is probably best to just turn off that the linker fails on any warning:

  https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=7cc5c8a2b79c58bca5a06887ffeda0159c50a3a6

We don’t use GCS (yet?) and so we don’t need to care about this. The systemd people seem to be slightly too concerned about things outside their own software.

Best,
-Michael

> On 14 May 2025, at 16:08, Michael Tremer <michael.tremer@ipfire.org> wrote:
> 
> 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.
>> 
>> 
>> 
>