%% "Noel L Yap" <[EMAIL PROTECTED]> writes:
nly> I found a workaround (I still think it's a bug).
This is not a bug.
nly> If the whitespace in front of the include line are spaces instead
nly> of tabs, the problem doesn't occur.
IEEE Std 1003.2-1992, section 6.2.7.3 "Target Rules", lines 405-408:
... Text following a semicolon, if any, and all following lines that
begin with a <tab> are command lines to be executed to update the
target.
So, there is no question that _any_ line starting with a TAB, appearing
in a command line context, must be treated as such. Clearmake is
_clearly_ violating the POSIX.2 standard for make here by treating the
"include" line specially, even though it begins with a TAB.
The standard continues:
The first nonempty line that does not begin with a <tab> or # shall
begin a new entry. An empty or blank line, or a line beginning with
#, may begin a new entry.
Although it's permissible in the standard for blank lines to "break"
target rules it's not required, and I know of _no_ implementation of
make, including clearmake, that actually does this, and doing so in GNU
make would be a huge break with backward-compatibility.
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org http://www.paulandlesley.org/gmake/
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
