janneke pushed a commit to branch core-packages-team
in repository guix.

commit 6660c6ecedd7263877f49c261d544356223ab6ca
Author: Janneke Nieuwenhuizen <jann...@gnu.org>
AuthorDate: Fri Jan 3 18:45:22 2025 +0100

    gnu: perl-tk: Fix build with gcc-14.
    
    * gnu/packages/tcl.scm (perl-tk)[inputs]: Remove labels.
    [arguments]: Use G-Expressions.  Add CC to #:make-maker-flags to relax
    gcc-14's strictness.
    
    Change-Id: Id4d65d2e60bbb1e1e78a220b9e6c72277d24e799
---
 gnu/packages/tcl.scm | 20 ++++++++++++--------
 1 file changed, 12 insertions(+), 8 deletions(-)

diff --git a/gnu/packages/tcl.scm b/gnu/packages/tcl.scm
index 0d9c7909b6..3e4113d2ed 100644
--- a/gnu/packages/tcl.scm
+++ b/gnu/packages/tcl.scm
@@ -278,15 +278,19 @@ interfaces (GUIs) in the Tcl language.")
                "0pha40m97fzafjnq8vwkbi5sml6xv8jki6qi60rxrzmxlrqp5aij"))))
     (build-system perl-build-system)
     (native-inputs (list pkg-config))
-    (inputs `(("libx11" ,libx11)
-              ("libpng" ,libpng)
-              ("libjpeg" ,libjpeg-turbo)))
+    (inputs (list libx11 libpng libjpeg-turbo))
     (arguments
-     `(#:make-maker-flags `(,(string-append
-                              "X11=" (assoc-ref %build-inputs "libx11")))
-
-       ;; Fails to build in parallel: <http://bugs.gnu.org/18262>.
-       #:parallel-build? #f))
+     (list
+      #:make-maker-flags
+      #~(list (string-append "X11=" #$libx11)
+              ;; Using CFLAGS partly works but also creates a broken Makefile
+              #$(string-append "CC=gcc"
+                               " -Wno-error=implicit-function-declaration"
+                               " -Wno-error=implicit-int"
+                               " -Wno-error=incompatible-pointer-types"
+                               " -Wno-error=int-to-pointer-cast"))
+      ;; Fails to build in parallel: <http://bugs.gnu.org/18262>.
+      #:parallel-build? #f))
     (synopsis "Graphical user interface toolkit for Perl")
     (description
      "Tk is a Graphical User Interface ToolKit.")

Reply via email to