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 4Zyt1G4TMbz33B8 for ; Thu, 15 May 2025 14:30:58 +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 4Zyt1C1FGzz2yHY for ; Thu, 15 May 2025 14:30:55 +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 4Zyt1B4q2hz199 for ; Thu, 15 May 2025 14:30:54 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1747319454; 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=cZh87nSa23isdBSjL//rXyX3+F/X+WvTSk0ovvhfdIY=; b=IitIF2ew8+Hw4G5T+0KruBLm2HtFcdAbc2gELQSjvmEY7+eHiPIC0XQrsCre+DbmdXoD2/ WKD3NT8Ct5o8uhBA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1747319454; 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=cZh87nSa23isdBSjL//rXyX3+F/X+WvTSk0ovvhfdIY=; b=lBbmlUZStTXbeZP6djg6NYPMZH3LCNh4O7rVb0fLskx3o7Y4sz5fsh07W5Z0bqlGqyYh/S c/Cf5BYp2NHXWas8SV2W0se35TlIOX8VUE7lO97twsLkTFGUXqmfloNbU2Fp8ay4cZWOhH dyXCdJTOINUOXqJDD1qqsQ5EVt77ZCBK0KTMpWY7gMI3OM3DAXPEPYgXtbp5LX4R/dTMUl 7F5fA6caZUeZQrzC87zq8pCMkldqOEyop489tap2m/BsUHw+YjI5zm0UPpyNqTP4X8lrmB NzfNjkt84diuLohkQVePBsuOsy1Sep5V9u0ZjMM8FaOC1jFx2YcrKo2yR9XI9g== Message-ID: <9b7b4ae7-9383-4f51-9e23-23979fbc4cd6@ipfire.org> Date: Thu, 15 May 2025 16:30:50 +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: ruby build now failing in aarch64 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi All, The fix to udev to not fail if the linker emits warnings solved the udev build on aarch64 for me. However now it has got to building ruby and that has now failed. The error message is In file included from vm_core.h:118, from eval_intern.h:5, from debug.c:16: vm_callinfo.h: In function 'vm_ci_dump': internal.h:89:72: error: 'RUBY_FUNCTION_NAME_STRING' undeclared (first use in this function) 89 | #define rp(obj) rb_obj_info_dump_loc((VALUE)(obj), __FILE__, __LINE__, RUBY_FUNCTION_NAME_STRING) | ^~~~~~~~~~~~~~~~~~~~~~~~~ vm_callinfo.h:183:9: note: in expansion of macro 'rp' 183 | rp(ci); | ^~ internal.h:89:72: note: each undeclared identifier is reported only once for each function it appears in 89 | #define rp(obj) rb_obj_info_dump_loc((VALUE)(obj), __FILE__, __LINE__, RUBY_FUNCTION_NAME_STRING) | ^~~~~~~~~~~~~~~~~~~~~~~~~ vm_callinfo.h:183:9: note: in expansion of macro 'rp' 183 | rp(ci); | ^~ vm_callinfo.h: In function 'vm_ci_new_': internal.h:89:72: error: 'RUBY_FUNCTION_NAME_STRING' undeclared (first use in this function) 89 | #define rp(obj) rb_obj_info_dump_loc((VALUE)(obj), __FILE__, __LINE__, RUBY_FUNCTION_NAME_STRING) | ^~~~~~~~~~~~~~~~~~~~~~~~~ vm_callinfo.h:221:16: note: in expansion of macro 'rp' 221 | if (debug) rp(ci); | ^~ and the RUBY_FUNCTION_NAME_STRING undeclared I found a comment that it could be related to gcc15 but it seemed to be for windows systems. The version of ruby we have is 3.4.1 but 3.4.4 has been just issued with a fix Bug #21286: Windows - MSYS2 just updated to GCC 15.1.0, builds failing - Ruby - Ruby Issue Tracking System The bug report does have comments that it is strongly impacting windows systems but it is also affecting other OS's. I will try doing a build with the latest ruby and see if that solves the aarch64 build. Regards, Adolf.