From: Peter TB Brett <peter@peter-b.co.uk>
To: 22342@debbugs.gnu.org
Subject: bug#22342: Infinite loop when GUILE_FOR_BUILD == guile
Date: Sun, 10 Jan 2016 20:28:45 +0000 [thread overview]
Message-ID: <7b233438bdd6e7ff5dd2e30cbb35e9c6@net2air.co> (raw)
I ran across an interesting problem while cross-compiling Guile 2.0.11
with MinGW.
"GEN guile-procedures.texi" sat in an infinite loop, due to meta/guile
exec-ing itself in a tight loop.
This was because I had set GUILE_FOR_BUILD to "guile" in my configure
invocation. In the uninstalled_env environment, "guile" is
"meta/guile", not my installed version of guile in my PATH.
It might be helpful for configure to insist that GUILE_FOR_BUILD is an
absolute path in order to avoid this happening to other naive
cross-compiling users!
Peter
next reply other threads:[~2016-01-10 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 20:28 Peter TB Brett [this message]
2016-08-07 11:29 ` bug#22342: Infinite loop when GUILE_FOR_BUILD == guile Andy Wingo
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=7b233438bdd6e7ff5dd2e30cbb35e9c6@net2air.co \
--to=peter@peter-b.co.uk \
--cc=22342@debbugs.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).