lkml.org 
[lkml]   [2001]   [Jul]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH] Re: 2.4.6p6: dep_{bool,tristate} $CONFIG_ARCH_xxx bugs
Date
On Sun, 1 Jul 2001 19:25:11 -0700, 
"Adam J. Richter" <adam@yggdrasil.com> wrote:
> Does anyone know if there is any code that would break if
>we put quotation marks around the $CONFIG_xxxx references in the
>dep_xxx commands in all of the Config.in files?

That has the same problem that AC was worried about. Variables that
used to be treated as "undefined, don't care" are now treated as
"undefined, assume n and forbid".

As long as there is any ambiguity about how a rule is meant to treat
undefined variables, treating all undefined variables as 'n' is not
safe. Before making a global change like this, first verify that no
rule treats undefined variables as "don't care". Otherwise something
will break.

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

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