From: Ian Hulin <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: Thu, 23 Dec 2010 22:01:22 +0000 [thread overview]
Message-ID: <20101223-220121.sv81024.28066@savannah.gnu.org> (raw)
In-Reply-To:
URL:
<http://savannah.gnu.org/bugs/?31963>
Summary: guile-config: inconsistent behaviour when run using
lilypond configure under meta/uninstalled-env bash or fully install
Project: Guile
Submitted by: ian_hulin
Submitted on: Thu Dec 23 22:01:21 2010
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
Hi all,
If we run lilypond ./configure under meta/uninstalled-env bash on a machine
where 1.8.7 is installed it hangs
as follows:
ian@nanny-ogg:~/lily-build-g2$ /home/ian/lilypond/configure
--srcdir=/home/ian/lilypond --disable-optimising --prefix=/usr/local
checking build system type... i686-pc-linux-gnu
<snip>
checking for working metafont mode... ljfour
checking for kpsewhich... kpsewhich
checking for guile-config... guile-config
If I run exactly the same configuration in a Virtual Machine with guile
configured, compiled and installed the configuration runs to completion.
ian@greebo:~/lily-build-g2$ /home/ian/lilypond/configure
--srcdir=/home/ian/lilypond --disable-optimising --prefix=/usr/local
checking build system type... i686-pc-linux-gnu
<snip>
checking for guile-config... guile-config
checking guile-config version... 1.9.14
checking guile compile flags... -pthread -I/usr/local/include/guile/2.0
<snip>
configure: creating ./config.status
config.status: creating config.make
config.status: creating config.hh
Type:
make all to build LilyPond
make install to install LilyPond
make help to see all possible targets
Edit local.make for local Makefile overrides.
ian@greebo:~/lily-build-g2$
It's really tedious having to keep a full VM or laptop installation set
up to work around this inconsistency, is there any chance of fixing this
in the guile kit, please? If not, how can we work around this in our
configure?
I think this has been the behaviour since Guile V1.9.11.
Cheers,
Ian Hulin
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?31963>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next reply other threads:[~2010-12-23 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 22:01 Ian Hulin [this message]
2011-02-13 18:43 ` [bug #31963] guile-config: inconsistent behaviour when run using lilypond configure under meta/uninstalled-env bash or fully install Andy Wingo
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=20101223-220121.sv81024.28066@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).