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 4Zy9nw3PHgz30VM for ; Wed, 14 May 2025 11:18:44 +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) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4Zy9ns0JcZz2xyW for ; Wed, 14 May 2025 11:18:41 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4Zy9nr0DtMzkM for ; Wed, 14 May 2025 11:18:39 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1747221520; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=5b/5iBDKQo5hwqyRedRtl8BOP0XoOXPK6AskbQxPdp8=; b=2Kq+GuEoGBrmJJbToWcsrgXHXsH5y8hEhqZ8cTn8JIPamcdj4g9jo0nj3j3zRyCalRJaBY FX3dWCOyfHO5o8BQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1747221520; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=5b/5iBDKQo5hwqyRedRtl8BOP0XoOXPK6AskbQxPdp8=; b=WIxz2lkqwDEHeJVu2o2D0CfHLteE/RIjmxBvi3akqrJAxYjJ0JqZ3Up2JL4zVtNchfD7la 0jOmpGiKu2Un5tTY4SRsmbv4dNg85witvRPCjmE+r8Wj0FXacecvq9STbekDE7IU8r0UIx YGAmtgwIRF2u0NSVmuzWi3hgCfdXrJlKV5N1SzymBhL1pQhWV0ZLVzFVoRIo53N5nrQQiw qa7cApImjPdzh88MgnkxvhupzGqZdV1Go4Ba40pvwynf0pmdNXatAWLrjy4/Vh1P//2nIT IYGc5T3hmXdxL2ZjVGNbybFBedXMMi1UDf2xoZl2qMGiBre5ojUR/5wMfr+GJA== Message-ID: <65cdb2f8-89a4-4062-9d46-530a256e6ea4@ipfire.org> Date: Wed, 14 May 2025 13:18:36 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Content-Language: en-GB To: "IPFire: Development-List" From: Adolf Belka Subject: udev build failing in aarch64 builder Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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.