From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e6791a9e4a3210201188daa981d3b2d2c092846e
Date: Fri, 23 May 2025 09:35:06 +0000 (UTC) [thread overview]
Message-ID: <4b3g4B4DRqz2xcq@people01.haj.ipfire.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via e6791a9e4a3210201188daa981d3b2d2c092846e (commit)
from bfbf3566b6a206cac68c1b36764451f73f89049f (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit e6791a9e4a3210201188daa981d3b2d2c092846e
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Fri May 23 09:34:45 2025 +0000
ruby: Fix build on aarch64
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/ruby | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/lfs/ruby b/lfs/ruby
index 6eb5b057d..8c06bac74 100644
--- a/lfs/ruby
+++ b/lfs/ruby
@@ -34,6 +34,8 @@ TARGET = $(DIR_INFO)/$(THISAPP)
# https://mirror.cyberbits.eu/ruby/
+CFLAGS += -DRUBY_FUNCTION_NAME_STRING=__FUNCTION__
+
###############################################################################
# Top-level Rules
###############################################################################
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-05-23 9:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4b3g4B4DRqz2xcq@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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