From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/libtool/files/
Date: Tue, 27 Mar 2018 08:00:07 +0000 (UTC) [thread overview]
Message-ID: <1522137600.d8532ad3d28b8026453b2cbab85e969bd05d4a2f.grobian@gentoo> (raw)
commit: d8532ad3d28b8026453b2cbab85e969bd05d4a2f
Author: Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 27 07:59:45 2018 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Tue Mar 27 08:00:00 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d8532ad3
sys-devel/libtool: fix applying eprefix patch, bug #651670
Closes: https://bugs.gentoo.org/651670
Package-Manager: Portage-2.3.24, Repoman-2.3.6
sys-devel/libtool/files/libtool-2.2.10-eprefix.patch | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sys-devel/libtool/files/libtool-2.2.10-eprefix.patch b/sys-devel/libtool/files/libtool-2.2.10-eprefix.patch
index 5a2980d2979..c4693ee7fee 100644
--- a/sys-devel/libtool/files/libtool-2.2.10-eprefix.patch
+++ b/sys-devel/libtool/files/libtool-2.2.10-eprefix.patch
@@ -1,5 +1,5 @@
---- ./libltdl/m4/libtool.m4.orig 2010-07-02 12:41:07.000000000 +0200
-+++ ./libltdl/m4/libtool.m4 2010-07-02 12:45:39.000000000 +0200
+--- a/m4/libtool.m4
++++ b/m4/libtool.m4
@@ -2087,7 +2087,7 @@
mingw* | cegcc*) lt_search_path_spec=`$ECHO "$lt_search_path_spec" |\
$SED 's,/\([[A-Za-z]]:\),\1,g'` ;;
next reply other threads:[~2018-03-27 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 8:00 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-10 2:51 [gentoo-commits] repo/gentoo:master commit in: sys-devel/libtool/files/ Sam James
2021-11-05 22:10 Sam James
2017-02-04 21:22 David Seifert
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=1522137600.d8532ad3d28b8026453b2cbab85e969bd05d4a2f.grobian@gentoo \
--to=grobian@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