From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guile-user@gnu.org
Subject: guile-lzlib fix for native build with gcc-14
Date: Sat, 07 Dec 2024 09:57:44 +0100 [thread overview]
Message-ID: <87ed2jan07.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 162 bytes --]
Hi Mathieu,
This is a bit of a deja-vu, I'm using the attached patch for a native
build of guile-lzlib with gcc-14 on "core-packages-team".
Greetings,
Janneke
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-build-Support-gcc-14.patch --]
[-- Type: text/x-patch, Size: 910 bytes --]
From 8b0db8997007d427ce9e77cb8191e698d1c47f02 Mon Sep 17 00:00:00 2001
From: "janneke@gnu.org" <janneke@gnu.org>
Date: Sat, 7 Dec 2024 09:48:49 +0100
Subject: [PATCH] build: Support gcc-14.
* configure.ac: When compiling natively declare LZ_decompress_open before
using it in conftest.c.
---
configure.ac | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 4c56768..ffdab1d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -43,7 +43,10 @@ EOF
else
old_LIBS="$LIBS"
LIBS="-llz"
- AC_LINK_IFELSE([AC_LANG_SOURCE([int main () { return LZ_decompress_open(); }])],
+ AC_LINK_IFELSE([AC_LANG_SOURCE([
+int LZ_decompress_open ();
+int main () { return LZ_decompress_open(); }
+])],
[guile_cv_liblz_libdir="`ldd conftest$EXEEXT | grep liblz | sed '-es/.*=> \(.*\) .*$/\1/g'`"])
LIBS="$old_LIBS"
fi])
--
2.46.0
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
next reply other threads:[~2024-12-07 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 8:57 Janneke Nieuwenhuizen [this message]
2024-12-07 20:29 ` guile-lzlib fix for native build with gcc-14 Mathieu Othacehe
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ed2jan07.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guile-user@gnu.org \
--cc=othacehe@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).