public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joshua Kinard" <kumba@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-vcs/git/, dev-vcs/git/files/
Date: Sun,  6 Sep 2015 23:16:16 +0000 (UTC)	[thread overview]
Message-ID: <1441581332.e7c87c71a93aade54a574d2d11738019654029cd.kumba@gentoo> (raw)

commit:     e7c87c71a93aade54a574d2d11738019654029cd
Author:     Joshua Kinard <kumba <AT> gentoo <DOT> org>
AuthorDate: Sun Sep  6 23:15:32 2015 +0000
Commit:     Joshua Kinard <kumba <AT> gentoo <DOT> org>
CommitDate: Sun Sep  6 23:15:32 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e7c87c71

Fix #493306, where libiconv.so was merged into FreeBSd's libc in 10.x.  Without, git attempts to use -liconv during linking, which will fail on Gentoo/FreeBSD 10.x installs.

Package-Manager: portage-2.2.20.1

 dev-vcs/git/files/git-2.5.1-freebsd-10.x-no-iconv.patch | 14 ++++++++++++++
 dev-vcs/git/git-2.5.1.ebuild                            |  3 +++
 2 files changed, 17 insertions(+)

diff --git a/dev-vcs/git/files/git-2.5.1-freebsd-10.x-no-iconv.patch b/dev-vcs/git/files/git-2.5.1-freebsd-10.x-no-iconv.patch
new file mode 100644
index 0000000..a874236
--- /dev/null
+++ b/dev-vcs/git/files/git-2.5.1-freebsd-10.x-no-iconv.patch
@@ -0,0 +1,14 @@
+diff -Naurp git-2.5.1.orig/config.mak.uname git-2.5.1/config.mak.uname
+--- git-2.5.1.orig/config.mak.uname	2015-08-28 15:37:13.000000000 -0400
++++ git-2.5.1/config.mak.uname	2015-09-06 18:54:28.538437000 -0400
+@@ -189,7 +189,9 @@ ifeq ($(uname_O),Cygwin)
+ 	SPARSE_FLAGS = -isystem /usr/include/w32api -Wno-one-bit-signed-bitfield
+ endif
+ ifeq ($(uname_S),FreeBSD)
+-	NEEDS_LIBICONV = YesPlease
++	ifeq ($(shell expr "$(uname_R)" : '[1-9]\.'),2)
++		NEEDS_LIBICONV = YesPlease
++	endif
+ 	OLD_ICONV = YesPlease
+ 	NO_MEMMEM = YesPlease
+ 	BASIC_CFLAGS += -I/usr/local/include

diff --git a/dev-vcs/git/git-2.5.1.ebuild b/dev-vcs/git/git-2.5.1.ebuild
index 352b93a..cf36860 100644
--- a/dev-vcs/git/git-2.5.1.ebuild
+++ b/dev-vcs/git/git-2.5.1.ebuild
@@ -229,6 +229,9 @@ src_prepare() {
 
 	epatch "${FILESDIR}"/git-2.2.0-svn-fe-linking.patch
 
+	# Bug #493306, where FreeBSD 10.x merged libiconv into its libc.
+	epatch "${FILESDIR}"/git-2.5.1-freebsd-10.x-no-iconv.patch
+
 	epatch_user
 
 	sed -i \


             reply	other threads:[~2015-09-06 23:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06 23:16 Joshua Kinard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-09-29 15:16 [gentoo-commits] repo/gentoo:master commit in: dev-vcs/git/, dev-vcs/git/files/ Lars Wendler
2015-10-10 11:17 Justin Lecher
2015-11-19 23:26 Robin H. Johnson
2016-01-05 10:04 Lars Wendler
2016-05-08 22:57 Mike Gilbert
2016-06-07 12:26 Lars Wendler
2017-02-25 20:38 Lars Wendler
2017-05-24  8:49 Lars Wendler
2018-06-06 14:34 Lars Wendler
2018-09-04 15:53 Lars Wendler
2019-05-14  8:58 Lars Wendler
2019-10-26 12:55 Lars Wendler
2020-02-17  9:48 Lars Wendler
2021-08-17 10:58 Lars Wendler
2021-11-08 18:42 Mike Gilbert
2022-08-12 15:46 Sam James
2022-09-01  3:11 Sam James
2022-11-30  7:48 Sam James
2025-01-08  3:40 Sam James
2025-01-11  6:37 Sam James
2025-01-30  0:40 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=1441581332.e7c87c71a93aade54a574d2d11738019654029cd.kumba@gentoo \
    --to=kumba@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