From: Adolf Belka <adolf.belka@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: ruby build now failing in aarch64
Date: Thu, 15 May 2025 18:18:47 +0200 [thread overview]
Message-ID: <b1b3d8e9-5a5c-40dd-ac30-67bee0c26133@ipfire.org> (raw)
In-Reply-To: <9b7b4ae7-9383-4f51-9e23-23979fbc4cd6@ipfire.org>
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.
>
prev parent reply other threads:[~2025-05-15 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 14:30 Adolf Belka
2025-05-15 16:18 ` Adolf Belka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1b3d8e9-5a5c-40dd-ac30-67bee0c26133@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox