public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libintl/, dev-libs/libintl/files/
Date: Tue, 13 Oct 2015 03:34:14 +0000 (UTC)	[thread overview]
Message-ID: <1444707169.fbc240f551b32a009511d34ac5c3fd7c15ef82b9.vapier@gentoo> (raw)

commit:     fbc240f551b32a009511d34ac5c3fd7c15ef82b9
Author:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 13 03:32:49 2015 +0000
Commit:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Tue Oct 13 03:32:49 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fbc240f5

dev-libs/libintl: fix build in bionic systems

 .../libintl/files/libintl-0.19.5-langinfo.patch    | 35 ++++++++++++++++++++++
 dev-libs/libintl/libintl-0.19.6.ebuild             |  2 ++
 2 files changed, 37 insertions(+)

diff --git a/dev-libs/libintl/files/libintl-0.19.5-langinfo.patch b/dev-libs/libintl/files/libintl-0.19.5-langinfo.patch
new file mode 100644
index 0000000..bf96e69
--- /dev/null
+++ b/dev-libs/libintl/files/libintl-0.19.5-langinfo.patch
@@ -0,0 +1,35 @@
+this has been sent upstream
+
+From eac944b0757963ac1ba035ea72617734510ede22 Mon Sep 17 00:00:00 2001
+From: Mike Frysinger <vapier@chromium.org>
+Date: Mon, 12 Oct 2015 17:58:51 -0400
+Subject: [PATCH] intl/localename: control langinfo.h inclusion
+
+This header is only used to work around buggy behavior in old versions
+of glibc, so do not include it all the time.  Otherwise we get build
+failures on systems that do not provide langinfo.h.
+
+* gettext-runtime/intl/localename.c: Wrap langinfo.h include with same
+ifdefs used in the source later on.
+---
+ gettext-runtime/intl/localename.c | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/gettext-runtime/intl/localename.c b/gettext-runtime/intl/localename.c
+index f8cf3f2..c27be86 100644
+--- a/gettext-runtime/intl/localename.c
++++ b/gettext-runtime/intl/localename.c
+@@ -38,7 +38,9 @@
+ # if defined __APPLE__ && defined __MACH__
+ #  include <xlocale.h>
+ # endif
+-# include <langinfo.h>
++# if __GLIBC__ >= 2 && !defined __UCLIBC__
++#  include <langinfo.h>
++# endif
+ # if !defined IN_LIBINTL
+ #  include "glthread/lock.h"
+ # endif
+-- 
+2.5.2
+

diff --git a/dev-libs/libintl/libintl-0.19.6.ebuild b/dev-libs/libintl/libintl-0.19.6.ebuild
index 5c78826..a8fbdac 100644
--- a/dev-libs/libintl/libintl-0.19.6.ebuild
+++ b/dev-libs/libintl/libintl-0.19.6.ebuild
@@ -28,6 +28,8 @@ RDEPEND="${DEPEND}
 S="${WORKDIR}/${MY_P}/gettext-runtime"
 
 src_prepare() {
+	epatch "${FILESDIR}"/${PN}-0.19.5-langinfo.patch
+
 	# The libtool files are stored higher up, so make sure we run in the
 	# whole tree and not just the subdir we build.
 	elibtoolize "${WORKDIR}"


             reply	other threads:[~2015-10-13  3:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13  3:34 Mike Frysinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-29 15:04 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libintl/, dev-libs/libintl/files/ Sam James
2024-02-20  5:24 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=1444707169.fbc240f551b32a009511d34ac5c3fd7c15ef82b9.vapier@gentoo \
    --to=vapier@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