From: "Mike Frysinger (vapier)" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in sys-devel/automake/files: automake-1.10-ccnoco-ldflags.patch
Date: Fri, 29 May 2009 23:41:11 +0000 [thread overview]
Message-ID: <E1MABhH-0006ST-JA@stork.gentoo.org> (raw)
vapier 09/05/29 23:41:11
Added: automake-1.10-ccnoco-ldflags.patch
Log:
Add fix from upstream for ccnoco test failure with custom LDFLAGS #203914 by Carsten Lohrke.
(Portage version: 2.2_rc33/cvs/Linux x86_64)
Revision Changes Path
1.1 sys-devel/automake/files/automake-1.10-ccnoco-ldflags.patch
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/automake/files/automake-1.10-ccnoco-ldflags.patch?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/automake/files/automake-1.10-ccnoco-ldflags.patch?rev=1.1&content-type=text/plain
Index: automake-1.10-ccnoco-ldflags.patch
===================================================================
http://bugs.gentoo.org/203914
From 6e86514729c6dccb6213fdde8d93d7061c8108a5 Mon Sep 17 00:00:00 2001
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Date: Mon, 7 Jan 2008 21:53:38 +0100
Subject: [PATCH] Fix ccnoco.test for uncommon LDFLAGS settings.
* tests/ccnoco.test (Mycomp): Use a tighter match for -c -o,
to avoid matching for example `LDFLAGS=-Wl,--sort-common'.
* THANKS: Update.
Report and analysis by Carsten Lohrke and Mike Frysinger.
---
ChangeLog | 7 +++++++
THANKS | 1 +
tests/ccnoco.test | 6 +++---
3 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/tests/ccnoco.test b/tests/ccnoco.test
index 8b37fe8..ca75922 100755
--- a/tests/ccnoco.test
+++ b/tests/ccnoco.test
@@ -57,8 +57,8 @@ END
cat > Mycomp << 'END'
#!/bin/sh
-case "$@" in
- *-c*-o* | *-o*-c*)
+case " "$* in
+ *\ -c*\ -o* | *\ -o*\ -c*)
exit 1
;;
esac
--
1.6.3
reply other threads:[~2009-05-29 23:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1MABhH-0006ST-JA@stork.gentoo.org \
--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