From:	tolj AT uni-duesseldorf DOT de (Stipe Tolj)
Subject:	Re: B20: Kaffe configure script locking on NT 4.0.
19 Nov 1998 09:08:24 -0800 :
Message-ID:	<3653609F.2F2BFCE.cygnus.gnu-win32@uni-duesseldorf.de>
References:	<199811171428 DOT JAA20848 AT host DOT ott DOT igs DOT net>
Mime-Version:	1.0
To:	mtr AT ottawa DOT com
Cc:	gnu-win32 AT cygnus DOT com

> The configure script in Kaffe's source tree seems to be causing the Cygwin
> (b20) tools no end of grief on my Windows NT 4.0 workstation.  Basically,
> the script starts running and producing the expected output ("checking for
> foobie... yes" "checking for bletch... no"), but at random points the script
> just stops executing.  BASH (in the form of /bin/sh.exe) sits there and
> sucks up 100% of the CPU time, but nothing gets executed.  Control-C
> processing doesn't work, but the console window can be terminated.
>
> The problem is partially deterministic.  I can replicate it 100% of the time
> -- I've never had the configuration script successfully run to completion.
> It breaks at different points, however, with each run.  Sometimes it stops
> very early in the process (seemingly before it even gets the chance to
> execute the first sub-script), sometimes it stops after processing
> seemingly hundreds of checks.  It never actually finishes, however.
>
> Can somebody please give me an idea of a) what the problem could be and b)
> what I can do to work around it?  (Please CC my personal address on any
> replies.)

if it is a autoconf generated script your should have a look to config.log at
the top directory. This may give more conclussions what is happening.

Regards,
Stipe

--
Stipe Tolj <tolj AT uni-duesseldorf DOT de>
Cygwin Porting Project
Department of Economical Computer Science
University of Cologne, Germany
http://www-public.rz.uni-duesseldorf.de/~tolj




-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -