emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#22342: closed (Infinite loop when GUILE_FOR_BUILD


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#22342: closed (Infinite loop when GUILE_FOR_BUILD == guile)
Date: Sun, 07 Aug 2016 11:30:02 +0000

Your message dated Sun, 07 Aug 2016 13:29:45 +0200
with message-id <address@hidden>
and subject line Re: bug#22342: Infinite loop when GUILE_FOR_BUILD == guile
has caused the debbugs.gnu.org bug report #22342,
regarding Infinite loop when GUILE_FOR_BUILD == guile
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
22342: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22342
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Infinite loop when GUILE_FOR_BUILD == guile Date: Sun, 10 Jan 2016 20:28:45 +0000 User-agent: Roundcube Webmail/0.9.4 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




--- End Message ---
--- Begin Message --- Subject: Re: bug#22342: Infinite loop when GUILE_FOR_BUILD == guile Date: Sun, 07 Aug 2016 13:29:45 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
Fixed in master; we capture the full path to GUILE_FOR_BUILD.  Cheers :)

Andy

On Sun 10 Jan 2016 21:28, Peter TB Brett <address@hidden> writes:

> 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


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]