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 4ZywPq5bCXz33K9 for ; Thu, 15 May 2025 16:18:55 +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 4ZywPm2LwBz2yHY for ; Thu, 15 May 2025 16:18:52 +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 4ZywPl1Ncqz110 for ; Thu, 15 May 2025 16:18:51 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1747325931; 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: in-reply-to:in-reply-to:references:references; bh=uiFl/PJIA+TBVJ6ViEAnu6d9kOHPrKEPkzJE13w1QVQ=; b=buxJ8/FciFApV8GTR7viw0J3C15vQBBwgWGtXD/autSdaJWm8IWtVwt4iadvN3bP+a3Dk0 Pl5hLOnpd0YORYBQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1747325931; 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: in-reply-to:in-reply-to:references:references; bh=uiFl/PJIA+TBVJ6ViEAnu6d9kOHPrKEPkzJE13w1QVQ=; b=mPnRZITejmRKxcPRTbNhx1KguSZwgsnP0Grd15iFAp7QfIP/yrzXwAQ9wnUPkfzlflZyOj X19aecMPpJGllfVD9F2vNxYzoKJT9bw/+iixFpnGVs+FWNvt3tuKo1VKEYyGlrDLpQG4QV QU9aMYUUWzkSe+dT3qGRpdKHsY1TsGBouxsHpsQRm9KRwnhayrGbY/Fw7VV4o3EbZ+oJze yGEkMozUX7PxRyrt6YkgaHBF23RNSKJeccVDxh3YCICSpDs+Q4AX9+dIDXkBmKXLiSAWTo o+yd6fEkbRC4Cacn+69Yw2sy9wYO+Cq2w44VZA5ioBud0zsYfi3vGXwlFLCRNA== Message-ID: Date: Thu, 15 May 2025 18:18:47 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: ruby build now failing in aarch64 From: Adolf Belka To: "IPFire: Development-List" References: <9b7b4ae7-9383-4f51-9e23-23979fbc4cd6@ipfire.org> Content-Language: en-GB In-Reply-To: <9b7b4ae7-9383-4f51-9e23-23979fbc4cd6@ipfire.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi All, On 15/05/2025 16:30, Adolf Belka wrote: > 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. Unfortunately building ruby-3.4.4 did not fix the above problem. The same errors still occurred. Regards, Adolf. > > Regards, > Adolf. >