lkml.org 
[lkml]   [1999]   [Sep]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: bug in 2.3.18ac9 net/Config.in
Hi Jes,

> 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

It *is* broken because it's missing the "then" keyword.

> 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 far as that part goes, you try designing and implementing a semantics
for a random-execution config language. It's harder than it looks.

We are actually on the same side here, I think. We both want real
semantics and real error reporting.

Michael

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

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:0.039 / U:0.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site