public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Palimaka" <kensington@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-i18n/jfbterm/files/, app-i18n/jfbterm/
Date: Sun, 12 Feb 2017 11:36:17 +0000 (UTC)	[thread overview]
Message-ID: <1486899364.f3ff448671e8102de87143905d9b847362f15997.kensington@gentoo> (raw)

commit:     f3ff448671e8102de87143905d9b847362f15997
Author:     Michael Palimaka <kensington <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 12 11:35:48 2017 +0000
Commit:     Michael Palimaka <kensington <AT> gentoo <DOT> org>
CommitDate: Sun Feb 12 11:36:04 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f3ff4486

app-i18n/jfbterm: add patch from Fedora fixing build with gcc-5

Gentoo-bug: 571066

Package-Manager: Portage-2.3.3, Repoman-2.3.1

 .../files/jfbterm-0.4.7-wrong-inline-gcc5.patch    | 24 ++++++++++++++++++++++
 app-i18n/jfbterm/jfbterm-0.4.7-r4.ebuild           |  3 ++-
 2 files changed, 26 insertions(+), 1 deletion(-)

diff --git a/app-i18n/jfbterm/files/jfbterm-0.4.7-wrong-inline-gcc5.patch b/app-i18n/jfbterm/files/jfbterm-0.4.7-wrong-inline-gcc5.patch
new file mode 100644
index 0000000000..974ccbc413
--- /dev/null
+++ b/app-i18n/jfbterm/files/jfbterm-0.4.7-wrong-inline-gcc5.patch
@@ -0,0 +1,24 @@
+Source: http://pkgs.fedoraproject.org/cgit/rpms/jfbterm.git/plain/jfbterm-0.4.7-wrong-inline-gcc5.patch
+
+--- jfbterm-0.4.7/pen.c.inline_gcc5	2003-08-30 03:48:16.000000000 +0900
++++ jfbterm-0.4.7/pen.c	2015-02-09 10:36:47.182751545 +0900
+@@ -62,7 +62,7 @@
+ 	p->attr = q->attr;
+ }
+ 
+-inline void tpen_off_all_attribute(TPen* p)
++void tpen_off_all_attribute(TPen* p)
+ {
+ 	p->bcol = 0;
+ 	p->fcol = 7;
+--- jfbterm-0.4.7/pen.h.inline_gcc5	2002-07-17 01:21:23.000000000 +0900
++++ jfbterm-0.4.7/pen.h	2015-02-09 10:36:52.058705503 +0900
+@@ -58,7 +58,7 @@
+ void tpen_init(TPen* p);
+ void tpen_final(TPen* p);
+ void tpen_copy(TPen* p, TPen* q);
+-inline void tpen_off_all_attribute(TPen* p);
++void tpen_off_all_attribute(TPen* p);
+ void tpen_higlight(TPen* p);
+ void tpen_dehiglight(TPen* p);
+ void tpen_underline(TPen* p);

diff --git a/app-i18n/jfbterm/jfbterm-0.4.7-r4.ebuild b/app-i18n/jfbterm/jfbterm-0.4.7-r4.ebuild
index a1266429d3..b79f0ff20b 100644
--- a/app-i18n/jfbterm/jfbterm-0.4.7-r4.ebuild
+++ b/app-i18n/jfbterm/jfbterm-0.4.7-r4.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2009 Gentoo Foundation
+# Copyright 1999-2017 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # $Id$
 
@@ -24,6 +24,7 @@ src_unpack() {
 	epatch "${FILESDIR}/${P}-sigchld-debian.patch"
 	epatch "${FILESDIR}/${P}-no-kernel-headers.patch"
 	epatch "${FILESDIR}/${P}-gentoo.patch"
+	epatch "${FILESDIR}/${P}-wrong-inline-gcc5.patch"
 
 	eautoreconf
 }


             reply	other threads:[~2017-02-12 11:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12 11:36 Michael Palimaka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-07 14:13 [gentoo-commits] repo/gentoo:master commit in: app-i18n/jfbterm/files/, app-i18n/jfbterm/ Akinori Hattori
2025-02-12 18:16 Sam James

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=1486899364.f3ff448671e8102de87143905d9b847362f15997.kensington@gentoo \
    --to=kensington@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