Re: 2.5: troubles with piping make output

From: Russell King (rmk@arm.linux.org.uk)
Date: Sun Nov 03 2002 - 16:24:35 EST


On Sun, Nov 03, 2002 at 09:54:05PM +0100, Roman Zippel wrote:
> On Sun, 3 Nov 2002, Russell King wrote:
> > No thanks. That breaks my build scripts. I don't want to go logging into
> > multiple machines just to run make oldconfig when the old system worked
> > perfectly well.
> >
> > "perfectly well" here means that make oldconfig worked over ssh, with the
> > local end logging the stdout to a file as well as the terminal, with stdin
> > from the terminal. It is quite reasonable to expect the configuration to
> > continue as normal.
>
> Huh? What do you mean? oldconfig still works as before, above only happens
> if you touch .config or a Kconfig file, kconfig tries to automatically
> update .config and will fail if stdio is redirected, but needs user input.
> The problem is not a missing fflush, the question is why kconfig couldn't
> detect the pipe.

ssh host make -C $tree oldconfig ARCH=arm

that doesn't allocate a terminal. I want such commands to _prompt_ for
input. If they die because its not a terminal, I consider that _broken_.
Why? The command is able to read input from a human, and write its output
to a human via the ssh pipes.

If you insist on breaking this, I'll insist on fixing it. Its a misfeature
that you refuse to run in this situation.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Thu Nov 07 2002 - 22:00:30 EST