public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/gf2x/files/, dev-libs/gf2x/
Date: Sat, 19 Nov 2022 01:35:05 +0000 (UTC)	[thread overview]
Message-ID: <1668821683.f0fb5cc9d77001e24b84cf76c19ea1abe88d5e74.sam@gentoo> (raw)

commit:     f0fb5cc9d77001e24b84cf76c19ea1abe88d5e74
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 19 01:11:09 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Nov 19 01:34:43 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f0fb5cc9

dev-libs/gf2x: fix configure w/ clang 16

Fixed myself then realised upstream patch, you need to request an account for inria
*from a member* so not bothering with strict prototypes...

Closes: https://bugs.gentoo.org/879663
Signed-off-by: Sam James <sam <AT> gentoo.org>

 .../gf2x/files/gf2x-1.3.0-configure-clang16.patch  | 28 ++++++++++++++++++++++
 .../{gf2x-1.3.0.ebuild => gf2x-1.3.0-r1.ebuild}    |  1 +
 2 files changed, 29 insertions(+)

diff --git a/dev-libs/gf2x/files/gf2x-1.3.0-configure-clang16.patch b/dev-libs/gf2x/files/gf2x-1.3.0-configure-clang16.patch
new file mode 100644
index 000000000000..df085ef3b694
--- /dev/null
+++ b/dev-libs/gf2x/files/gf2x-1.3.0-configure-clang16.patch
@@ -0,0 +1,28 @@
+https://bugs.gentoo.org/879663
+https://gitlab.inria.fr/gf2x/gf2x/-/commit/a2f0fd388c12ca0b9f4525c6cfbc515418dcbaf8
+
+From a2f0fd388c12ca0b9f4525c6cfbc515418dcbaf8 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Emmanuel=20Thom=C3=A9?= <Emmanuel.Thome@inria.fr>
+Date: Thu, 17 Sep 2020 23:40:54 +0200
+Subject: [PATCH] fix #include in configure test
+
+See there: https://trac.sagemath.org/ticket/30494
+--- a/config/acinclude.m4
++++ b/config/acinclude.m4
+@@ -661,6 +661,7 @@ AC_DEFUN([GF2X_PROG_CC_FOR_BUILD_WORKS],
+ # remove anything that might look like compiler output to our "||" expression
+ rm -f conftest* a.out b.out a.exe a_out.exe
+ cat >conftest.c <<EOF
++#include <stdlib.h>
+ int
+ main ()
+ {
+@@ -699,6 +700,7 @@ AC_DEFUN([GF2X_PROG_EXEEXT_FOR_BUILD],
+ AC_CACHE_CHECK([for build system executable suffix],
+                gf2x_cv_prog_exeext_for_build,
+ [cat >conftest.c <<EOF
++#include <stdlib.h>
+ int
+ main ()
+ {
+GitLab

diff --git a/dev-libs/gf2x/gf2x-1.3.0.ebuild b/dev-libs/gf2x/gf2x-1.3.0-r1.ebuild
similarity index 97%
rename from dev-libs/gf2x/gf2x-1.3.0.ebuild
rename to dev-libs/gf2x/gf2x-1.3.0-r1.ebuild
index 65685f3dbd3a..bb6abab0ffb6 100644
--- a/dev-libs/gf2x/gf2x-1.3.0.ebuild
+++ b/dev-libs/gf2x/gf2x-1.3.0-r1.ebuild
@@ -20,6 +20,7 @@ IUSE+=" ${IUSE_CPU_FLAGS// / cpu_flags_x86_}"
 PATCHES=(
 	"${FILESDIR}/fno-common.patch"
 	"${FILESDIR}/${P}-0001-src-tunefft.c-add-include-statement-for-MIN-and-MAX.patch"
+	"${FILESDIR}/${P}-configure-clang16.patch"
 )
 
 src_prepare() {


             reply	other threads:[~2022-11-19  1:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  1:35 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-26 18:18 [gentoo-commits] repo/gentoo:master commit in: dev-libs/gf2x/files/, dev-libs/gf2x/ Michael Orlitzky

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=1668821683.f0fb5cc9d77001e24b84cf76c19ea1abe88d5e74.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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