On Tue, Oct 14, 2008 at 7:33 AM, Ralf Wildenhues wrote:
> * Jeff Squyres wrote on Tue, Oct 14, 2008 at 01:26:49PM CEST:
>> FWIW: a quick grep through configure doesn't show any calls to bind(),
>> connect(), or accept(). So I don't know why Windows firewall is
>> complaining during running configure.
>
> Probably because this computer has settings that simply prevent unsigned
> executables from running at all. I guess that the original poster's
> issue has nothing to do with network activity whatsoever.
Well... I don't believe this is really the case here, since other
programs run just fine. Is there any chance that one of the
configuration scripts tries to connect, for example, to localhost?
That would probably be blocked by the firewall. I also had to unlock
the firewall for mpirun and lamboot.
Thanks,
Gustavo, aka "The Original Poster" ;-)
|
