Re: bug in 2.3.18ac9 net/Config.in
Andrzej Krzysztofowicz (ankry@pg.gda.pl)
Tue, 28 Sep 1999 15:59:49 +0038 (MET DST)
> On 28 Sep 1999, Jes Sorensen wrote:
> > >>>>> "David" == David Weinehall <tao@acc.umu.se> writes:
> >
> > David> It's better to fix the Config.in files than to blame
> > David> menuconfig/xconfig each time... After all, we don't blame make
> > David> if there are errors in the Makefile's.
> >
> > So we hack Config.in because menuconfig is broken, that really sounds
> > like a stupid solution to me.
> >
> > Having the following in Config.in is _not broken:
> >
> > if [ "$ARCH" = "ppc"]
> > bool "foo" CONFIG_SOME_RANDOM_THING
> > fi
> > if [ "$ARCH" = "mips"]
> > bool "bar" CONFIG_SOME_RANDOM_THING
> > fi
> >
> > Is _not_ broken as long as the condition cannot invoke the question
> > twice. This is just one example of brokenness in the menu based config
> > programs.
>
> As long as you add the proper ';then' to those if's, it works ok with
> menuconfig too, if I'm not all wrong... It's just xconfig that doesn't
> work.
Each section has *two* obvious errors:
1. missing ;then (or <newline>then
2. missing whitespace before "]"
And not only xconfig has problem with it. If you run Configure (make config)
you should see "syntax error near unexpected token `fi'" or "[: missing `]'"
Menuconfig probably just ignores the error ...
Are you able to set this variable ?
--
=======================================================================
Andrzej M. Krzysztofowicz ankry@mif.pg.gda.pl
phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math., Technical University of Gdansk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/