From: Andy Wingo <INVALID.NOREPLY@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Andy Wingo" <wingo@pobox.com>,
"Ian Hulin" <ian@hulin.org.uk>,
bug-guile@gnu.org
Subject: [bug #31963] guile-config: inconsistent behaviour when run using lilypond configure under meta/uninstalled-env bash or fully install
Date: Sun, 13 Feb 2011 18:43:53 +0000 [thread overview]
Message-ID: <20110213-184353.sv20118.82374@savannah.gnu.org> (raw)
In-Reply-To: <20101223-220121.sv81024.28066@savannah.gnu.org>
Follow-up Comment #1, bug #31963 (project guile):
Ian, did you happen to have a stale "guile-config" binary around in Guile's
$abs_top_builddir? At some point it switched from being there to being in
meta/, but you could have been left with a stale build product.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?31963>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2011-02-13 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 22:01 [bug #31963] guile-config: inconsistent behaviour when run using lilypond configure under meta/uninstalled-env bash or fully install Ian Hulin
2011-02-13 18:43 ` Andy Wingo [this message]
2011-02-14 21:04 ` Ian Hulin
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110213-184353.sv20118.82374@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=ian@hulin.org.uk \
--cc=ludo@gnu.org \
--cc=wingo@pobox.com \
/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).