[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #33399] Double-colon rules sometimes behave like if they were singl
|
From: |
ordcoder |
|
Subject: |
[bug #33399] Double-colon rules sometimes behave like if they were single-colon |
|
Date: |
Sun, 18 Sep 2011 12:05:30 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 |
Follow-up Comment #2, bug #33399 (project make):
Actually, given right quoting, make handles whitespace in target names just
fine: example in original post works as expected if rules were single-colon.
The problem described is different: it's that make doesn't set double-colon
flag on rule when actual and literal target names have different lengths
(because of successfully escaped characters (not necessary whitespace (e.g.
target a:b fails the same way))).
The attached patch fixes this problem, it is only one line long and it doesn't
break backward compatibility.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?33399>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/