From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4ZyK7j1493z30NY for ; Wed, 14 May 2025 16:49:37 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) client-signature RSA-PSS (4096 bits)) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4ZyK7d4ZqWz30Mg for ; Wed, 14 May 2025 16:49:33 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4ZyK7c6m9xzm2; Wed, 14 May 2025 16:49:32 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1747241373; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=I1HZ1jXXKX3ahneBiQ+uJdLQg3QrhJumUjdkLupIx98=; b=gXZ4euk0ktkGZ5+RcnNcHJS1kVmm9gnp/M8tCaQDWB0iulCZuzXeCRY9MkAzf5mTuXXMTD /CBMvErhAXaxW1DA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1747241373; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=I1HZ1jXXKX3ahneBiQ+uJdLQg3QrhJumUjdkLupIx98=; b=JKVFkQmhs2zjk3xUFiowmBT5TvdC/mtXwQEDCF0PmN2+NuLJkT5aZaoURU6WqkKE3VF/U+ IbAC6PEjYGLkKlChztb/MKgxMnEnYQODHfREOrxQxagy6kdjPzekSe2nnXTFNrFa4lNhxX 5WrBU3fZS6SXLgCpa0cVCrEP9Dcnk9S26hVh6DEgsXulIHir0j/pgKRAiTJgLq9+Gkwpa1 od/SfQ/pzxxkYf5gLNRaq/bW8yXwhU/PXnmJpGqciJvCM3gQQLf0w+cTvOWx4CmJq5z5BC KGPS/SJj7sV8r3sxFJ1aLybCywtwXVNt2Op22XbUHUWftRUGl91VkTmJDEApHA== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: udev build failing in aarch64 builder From: Michael Tremer In-Reply-To: <23057E82-1952-4999-ABD4-B2ED465D3335@ipfire.org> Date: Wed, 14 May 2025 17:49:32 +0100 Cc: "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: <87FBE1D9-7C86-4A0E-8717-8356A1F70A61@ipfire.org> References: <65cdb2f8-89a4-4062-9d46-530a256e6ea4@ipfire.org> <23057E82-1952-4999-ABD4-B2ED465D3335@ipfire.org> To: Adolf Belka 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=3Dipfire-2.x.git;a=3Dcommitdiff;h=3D7cc5c8a2b79c= 58bca5a06887ffeda0159c50a3a6 We don=E2=80=99t use GCS (yet?) and so we don=E2=80=99t 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 = wrote: >=20 > Hello Adolf, >=20 > I noticed that the build failed and hoped this would be a random = one-off problem. Turns out it is not. >=20 > I looked through the log and it seems that some libraries don=E2=80=99t = seem to be built with GCS (GNU Compiler Security). >=20 > 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. >=20 > I will have to run a build on my build system and investigate. Not a = clue what could be causing this. >=20 > As soon as I have something I will report back. >=20 > -Michael >=20 >> On 14 May 2025, at 12:18, Adolf Belka wrote: >>=20 >> Hi All, >>=20 >> 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. >>=20 >> 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. >>=20 >> I restored the boost lfs file and then built again and it failed = again. >>=20 >> The riscv64 had no problems building udev and also not on my x86_64 = system. >>=20 >> The udev build log is around 4,500 lines long so I have put it in = IPFire NoPaste. >>=20 >> https://nopaste.ipfire.org/view/GcfWtEyc >>=20 >> Regards, >>=20 >> Adolf. >>=20 >>=20 >>=20 >=20