Bug#620209: make: inconsistant description of ifdef directive behavior

2016-02-15 Thread Manoj Srivastava
>> Note that ifdef only tests whether a variable has a value. It does not >> expand the variable to see if that value is nonempty. Consequently, tests >> using ifdef return true for all definitions except those like foo =. To >> test for an empty value, use ifeq ($(foo),). >The paragraph that beg

Bug#620209: make: inconsistant description of ifdef directive behavior

2011-03-30 Thread Jonathan Nieder
reassign 620209 make-doc 3.81-5 tags 620209 + upstream quit Hi! Britton Leo Kerin wrote: [out of order for convenience] > The manual says: > > ifdef variable-name I assume you mean the manual shown with "info make"? [...] > The ifdef form takes the name of a variable as its argument, no

Bug#620209: make: inconsistant description of ifdef directive behavior

2011-03-30 Thread Britton Leo Kerin
Package: make Version: 3.81-5 Severity: normal The manual says: ifdef variable-name The ifdef form takes the name of a variable as its argument, not a reference to a variable. The value of that variable has a non-empty value, the text-if-true is effective; otherwise, the te