[...catching up on last few week's email...] Tom Rini wrote: > > Hello. Cufrrently in both 2.4 ad 2.5, scripts/Configure implements > optional min/max arguments for the 'int' keyword. > There are two problems however, first being that the spec, as defined in > Documentation/kbuild/config-language.txt states that the int verb does > not take range parameters, so this is out of spec. > Secondly, if one specifies a default value higher than 10000000 (or > lower than -10000000) oldconfig/config become horribly unhappy, unless > the invalid range parameters are included. > > So, would anyone object to patches to fix this behavior and any Config > entries which use it? Thanks.
I don't think any entries use it, they would turn up as parse errors in gcml2. I think the best way to fix the behaviour is to remove it from Configure entirely, so that Configure matches the spec. Another approach would be to add a "int"-like and "hex"-like statements which allowed multiple ranges of values to be specified, as in CML2. This would cater for things like if [ "$CONFIG_SOUND_MSNDCLAS" = "y" ]; then int ' MSND Classic IRQ 5, 7, 9, 10, 11, 12' CONFIG_MSNDCLAS_IRQ 5 hex ' MSND Classic memory B0000, C8000, D0000, D8000, E0000, E8000' CONFIG_MSNDCLAS_MEM D0000 hex ' MSND Classic I/O 210, 220, 230, 240, 250, 260, 290, 3E0' CONFIG_MSNDCLAS_IO 290 fi But that's probably not worth doing with Roman's lkc here. Greg. -- the price of civilisation today is a courageous willingness to prevail, with force, if necessary, against whatever vicious and uncomprehending enemies try to strike it down. - Roger Sandall, The Age, 28Sep2001. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
