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: media-gfx/solvespace/files/, media-gfx/solvespace/
Date: Mon,  7 Jun 2021 16:04:59 +0000 (UTC)	[thread overview]
Message-ID: <1623050034.099369de66cdc8a91f4e9b372bb2c38a6767a881.sam@gentoo> (raw)

commit:     099369de66cdc8a91f4e9b372bb2c38a6767a881
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jun  7 06:40:38 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jun  7 07:13:54 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=099369de

media-gfx/solvespace: fix build with GCC 11

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

 .../solvespace-2.3-gcc11-missing-limits-inc.patch     | 19 +++++++++++++++++++
 media-gfx/solvespace/solvespace-2.3.ebuild            |  7 ++++++-
 2 files changed, 25 insertions(+), 1 deletion(-)

diff --git a/media-gfx/solvespace/files/solvespace-2.3-gcc11-missing-limits-inc.patch b/media-gfx/solvespace/files/solvespace-2.3-gcc11-missing-limits-inc.patch
new file mode 100644
index 00000000000..ecf02fc5c01
--- /dev/null
+++ b/media-gfx/solvespace/files/solvespace-2.3-gcc11-missing-limits-inc.patch
@@ -0,0 +1,19 @@
+https://bugs.gentoo.org/790776
+--- a/src/exportvector.cpp
++++ b/src/exportvector.cpp
+@@ -4,6 +4,7 @@
+ // Copyright 2008-2013 Jonathan Westhues.
+ //-----------------------------------------------------------------------------
+ #include <libdxfrw.h>
++#include <limits>
+ #include "solvespace.h"
+ 
+ VectorFileWriter::~VectorFileWriter() {
+--- a/src/importdxf.cpp
++++ b/src/importdxf.cpp
+@@ -1,3 +1,5 @@
++#include <limits>
++
+ #include "solvespace.h"
+ #include "libdxfrw.h"
+ #include "libdwgr.h"

diff --git a/media-gfx/solvespace/solvespace-2.3.ebuild b/media-gfx/solvespace/solvespace-2.3.ebuild
index ca5fc5249b9..25975546f2b 100644
--- a/media-gfx/solvespace/solvespace-2.3.ebuild
+++ b/media-gfx/solvespace/solvespace-2.3.ebuild
@@ -1,7 +1,8 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2021 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
+
 DXFRW_COMMIT="87ff1082f49b1286a033ac8f38fe8dde0975bb8b"
 DXFRW_PV="0.6.3"
 DXFRW_P="libdxfrw-${DXFRW_PV}-${DXFRW_COMMIT}"
@@ -31,6 +32,10 @@ DEPEND="${RDEPEND}
 # NOTE: please keep commit hash actually when version up
 GIT_COMMIT_HASH="4d1e1341d926ac356b295d5cc3d61c7a6cd7d07d"
 
+PATCHES=(
+	"${FILESDIR}"/${PN}-2.3-gcc11-missing-limits-inc.patch
+)
+
 src_prepare() {
 	rm -r "extlib/libdxfrw" || die  "rm extlib/libdxfrw failed"
 	mv "${WORKDIR}/libdxfrw-${DXFRW_COMMIT}" "extlib/libdxfrw" || die "move libdxfrw-${DXFRW_COMMIT} failed"


             reply	other threads:[~2021-06-07 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 16:04 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-28 21:12 [gentoo-commits] repo/gentoo:master commit in: media-gfx/solvespace/files/, media-gfx/solvespace/ Andreas Sturmlechner
2022-06-09 19:33 Matthew Smith

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=1623050034.099369de66cdc8a91f4e9b372bb2c38a6767a881.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