In this special case its always one tab - no matter how many spaces. Recipes in gnumake must be indented with tab, in microsoft nmake - any whitespace is ok. Im ok with these rules (replace all "^([ ]+)" with tab afair) but think its funny that gnu people make effort to detect this kind of "error" and display sarcastic, 100% accurate comment just to annoy microsoft crowd.
grg12
@grg12
Best posts made by grg12
-
RE: Yes gmake, thats EXACTLY what i meant
Latest posts made by grg12
-
RE: Yes gmake, thats EXACTLY what i meant
Well, some time ago someone had bright idea that it will be relly nice if version control could automagically change end of line charcters depending of user operating system. If you develop such system (especially if its MKS or Integrity) be so kind and give me option to disable this "feature". Please, do it before i loose my mind and disable it with a crowbar....
Sometimes automated help shold be left out where "mr. Paperclip" lies -
RE: Yes gmake, thats EXACTLY what i meant
In this special case its always one tab - no matter how many spaces. Recipes in gnumake must be indented with tab, in microsoft nmake - any whitespace is ok. Im ok with these rules (replace all "^([ ]+)" with tab afair) but think its funny that gnu people make effort to detect this kind of "error" and display sarcastic, 100% accurate comment just to annoy microsoft crowd.
-
Yes gmake, thats EXACTLY what i meant
Just a minor case of sarcastic error code...
Makefile.mak:85 ××× missing separator (did you mean TAB instead of 8 spaces? ). Stop.Rewriting makefile from nmake to gnu