From: Titus von Boxberg <titus@v9g.de>
To: crossgcc@sourceware.org
Cc: yann.morin.1998@anciens.enib.fr
Subject: [PATCH 1 of 5] configure: correct check_for
Date: Sun, 21 Aug 2011 13:13:00 -0000 [thread overview]
Message-ID: <a946359cb4429037976e.1313932141@mikulin.boxberg.lan> (raw)
In-Reply-To: <patchbomb.1313932140@mikulin.boxberg.lan>
# HG changeset patch
# User Titus von Boxberg <titus@v9g.de>
# Date 1313876746 -7200
# Node ID a946359cb4429037976e6ff22c51515401eaf820
# Parent 41bd6777fa4f767d6264db7c58986920014fd708
configure: correct check_for
check_for didn't set variable 'where' when the path to a prog
was passed manually "(cached)".
Signed-off-by: "Titus von Boxberg" titus@v9g.de
diff -r 41bd6777fa4f -r a946359cb442 configure
--- a/configure Wed Aug 17 23:53:49 2011 +0200
+++ b/configure Sat Aug 20 23:45:46 2011 +0200
@@ -171,6 +171,7 @@
eval val="\${${var}}"
if [ -n "${val}" ]; then
status="${val} (cached)\n"
+ where="${val}"
break
fi
fi
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-08-21 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 13:13 [PATCH 0 of 5] Several patches for OSX,uClibc,gdb-6.8 Titus von Boxberg
2011-08-21 13:13 ` Titus von Boxberg [this message]
2011-08-21 13:14 ` [PATCH 3 of 5] patches/uClibc-0.9.30: install_headers build step portable to OSX 10.7 Titus von Boxberg
2011-08-21 13:14 ` [PATCH 4 of 5] docs/Using on MacOS: Document usage with Xcode 4.1 Titus von Boxberg
2011-08-21 13:14 ` [PATCH 2 of 5] main: need path to libtoolize Titus von Boxberg
2011-08-21 13:21 ` [PATCH 5 of 5] patches/gdb/6.8: correct compilation error when stpcpy is a define Titus von Boxberg
2011-08-21 22:22 ` [PATCH 0 of 5] Several patches for OSX,uClibc,gdb-6.8 Yann E. MORIN
2011-08-21 22:53 ` Yann E. MORIN
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=a946359cb4429037976e.1313932141@mikulin.boxberg.lan \
--to=titus@v9g.de \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).