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 4ZyGts1k6Tz33B1 for ; Wed, 14 May 2025 15:08:21 +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 4ZyGtn58QKz2yVK for ; Wed, 14 May 2025 15:08:17 +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 4ZyGtn1WPnz2SR; Wed, 14 May 2025 15:08:17 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1747235297; 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=PRm6ErrA2jw0vwAANZjblzO0rftGIE1isEpJgQgqrHY=; b=+nWSNZD+7BUDStZ7MD1V355IeT+0U3wfMG8DjbfDKpu2KpwT8W/HGFKK7i82ICex7pvdoP kHvJ0m5EloxqgKCw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1747235297; 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=PRm6ErrA2jw0vwAANZjblzO0rftGIE1isEpJgQgqrHY=; b=I+KuQbByo6axTqbftSIZEEyuDRT1GBSKyQGMkFLA1+eW2VLzqvFx1TDAItE5zk5tMKVUhQ sGVFq09ukxsbIMtQ94le8xDCayOsrx9C/iNgXFiRomksx5USpLqwzvaJnYS3SKPELmvjy+ GF7OIsQvMl8s9moDYzawrkZ45KnC1XSWaNR89NjMu8i76ZVKksF5ZjBLnqpPr9XofL3ET+ siYYPlhlWzpWPGtCPhj3JORP2L72kkulLLevn9rTF3Nm+b+wHmbQL12LJzhmDDDdwfdcZp ar27OgggYQfqtcn+BwBfJwVf/Ukx2cQLT6WkvSX9LN1E2KGYEPjliuTSo1inEw== 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: <65cdb2f8-89a4-4062-9d46-530a256e6ea4@ipfire.org> Date: Wed, 14 May 2025 16:08:16 +0100 Cc: "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: <23057E82-1952-4999-ABD4-B2ED465D3335@ipfire.org> References: <65cdb2f8-89a4-4062-9d46-530a256e6ea4@ipfire.org> To: Adolf Belka 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=E2=80=99t = 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 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