Re: MiNT vs GNU configure

[Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>]

Joris.Welkenhuysen@uz.kuleuven.ac.be (Joris Welkenhuysen) writes:

|>>>>>>> "Chris" == Chris Herborth <cherborth@semprini.waterloo-rdp.on.ca> writes:
|>> 
|Chris> Looking in configure, config.status is written with a statement
|Chris> that pulls lines from configure up to a EOF line, which is a
|Chris> fair number of lines down.  Is bash (and /bin/sh) halting
|Chris> because there's a buffer that's too small?  The bash that's
|Chris> working on configure is set to 'Wait' if I check with top, but
|Chris> it never wakes up.
|>> 
|>> 
|>> It sounds very much like the dreaded blocking fork problem.
|>> 
|>> One probably also could fix the pipe
|>> buffer size and recompile the kernel. I would guess that a quite
|>> moderate size would fix the problem for the majority of such scripts.

[...]

|> The problem that is mentioned above is related to the blocking fork, but
|> really is a bug in
|> bash.

This bug is fixed in my MiNT port of bash, available as
ftp.germany.eu.net:/pub/comp/atari-st/mint/bash1141.zoo.

-- 
Andreas Schwab                                      "And now for something
schwab@issan.informatik.uni-dortmund.de              completely different"