From: Ian Hulin <ian@hulin.org.uk>
To: Andy Wingo <INVALID.NOREPLY@gnu.org>
Cc: bug-guile@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: [bug #31963] guile-config: inconsistent behaviour when run using lilypond configure under meta/uninstalled-env bash or fully install
Date: Mon, 14 Feb 2011 21:04:10 +0000 [thread overview]
Message-ID: <4D5998CA.8070707@hulin.org.uk> (raw)
In-Reply-To: <20110213-184353.sv20118.82374@savannah.gnu.org>
On 13/02/11 18:43, Andy Wingo wrote:
> 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.
>
It's possible. I've generally downloaded guile into separate
directories and built from that directory, but in this environment(my
main machine) I did have a fit of enthusiasm and did a complete
installation of a much earlier version of guile (I think 1.9.11) all the
way through to running make install. I then backed out using make
uninstall.
Could this have left crud hanging around to cause the observed effects?
I've been working around it using either a Virtual Machine environment
or my laptop where I've never installed anything before 1.9.14.
How could I check the $abs_top_builddir setting for you?
As I've got a work-round please don't let this hold up the Guile release.
Cheers,
Ian
prev parent reply other threads:[~2011-02-14 21:04 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
2011-02-14 21:04 ` Ian Hulin [this message]
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=4D5998CA.8070707@hulin.org.uk \
--to=ian@hulin.org.uk \
--cc=INVALID.NOREPLY@gnu.org \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).