On Thu, May 09, 2002 at 10:16:47PM -0400, Paul D. Smith wrote:
> %% Earnie Boyd <[EMAIL PROTECTED]> writes:
>
> eb> Russ Allbery wrote:
> >> Paul D Smith <[EMAIL PROTECTED]> writes:
> >>
> >> > I notice that the AC_FUNC_SETVBUF_REVERSED macro has no option for how
> >> > it behaves during cross-compilation.
Why not fall back to "setbuf(stdout, NULL)" if, for whatever
reason, you can't determine the right setvbuf() calling sequence?
Sure it's less efficient -- perhaps much less -- but it'll
produce correct results without guessing.
(Background: gmake only uses setvbuf() to make stdout
line-buffered. I presume the reason is to make sure the output
from make and its subprocesses interleaves properly.)
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. [EMAIL PROTECTED]
| | /
Anyone who swims with the current will reach the big music steamship;
whoever swims against the current will perhaps reach the source.
- Paul Schneider-Esleben
