Re: kbuild 2.5 is ready for inclusion in the 2.5 kernel

Keith Owens (kaos@ocs.com.au)
Thu, 09 May 2002 11:44:38 +1000


On Wed, 8 May 2002 20:55:46 -0400,
Daniel Jacobowitz <dan@debian.org> wrote:
>On Thu, May 09, 2002 at 10:10:19AM +1000, Keith Owens wrote:
>> On Wed, 8 May 2002 19:25:57 +0200,
>> Alex Riesen <Alexander.Riesen@synopsys.com> wrote:
>> >i've found the reason: the make's stdin was redirected in /dev/null
>> >(my make is aliased to a program prettifying output).
>>
>> Use standard make.
>
>Wouldn't you call it a bug anyway if running
>'make -f Makefile-2.5 oldconfig < /dev/null' went on to build a kernel?
>That's pretty surprising behavior.
>
>(Not saying that that does happen, but it's how I read Alex's message)

It would be a bug, that is not what is causing the problem.
make oldconfig < /dev/null breaks on both kbuild 2.4 and 2.5, oldconfig
requires input. If you want no prompts with oldconfig taking defaults
for new values then

yes '' | make oldconfig (kbuild 2.4)
make defconfig (kbuild 2.5)

I cannot reproduce Alex's problems using standard make or gmake. It is
almost certainly a problem with his version of make or the wrapper
around it, it is introducing spurious targets. If the problem occurs
using standard GNU make then I will look at it.

-
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/