GNU bug report logs - #14707
automake 1.14 test hang for t/compile4.sh on Linux if "cl" executable is in path

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Diab Jerius <dj <at> head.cfa.harvard.edu>
Subject: bug#14707: closed (Re: bug#14707: automake 1.14 test hang for
 t/compile4.sh on Linux if "cl" executable is in path)
Date: Sun, 21 Jul 2013 12:16:03 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#14707: automake 1.14 test hang for t/compile4.sh on Linux if "cl" executable is in path

which was filed against the automake package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 14707 <at> debbugs.gnu.org.

-- 
14707: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14707
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Diab Jerius <dj <at> head.cfa.harvard.edu>
Cc: 14707-done <at> debbugs.gnu.org,
 "automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#14707: automake 1.14 test hang for t/compile4.sh on Linux
 if "cl" executable is in path
Date: Sun, 21 Jul 2013 13:15:27 +0100

Reference:
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14707>

On 06/28/2013 10:25 PM, Diab Jerius wrote:
>
> [SNIP]
>
> That fixes the problem.
> 
Thanks, will push shortly then.  I'm also closing the bug report.

Best regards,
  Stefano

[Message part 3 (message/rfc822, inline)]

From: Diab Jerius <dj <at> head.cfa.harvard.edu>
To: bug-automake <at> gnu.org
Subject: automake 1.14 test hang for t/compile4.sh on Linux if "cl"
 executable is in path
Date: Mon, 24 Jun 2013 10:45:11 -0400

Hi,

On the Linux boxes I compile on, there's a /usr/local/bin/cl executable
(from the IRAF package).  Unfortunately, it seems that t/compile4.sh
interprets that as a Microsoft compiler.

The IRAF cl is an interactive program, so compile4.sh invokes it and it
hangs waiting for input.

Is there perhaps a better way of checking for the Microsoft compiler, or
restricting these tests to Microsoft operating systems?

Thanks,

Diab

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.