>> A lot of rules files uses loops around configure calls, however there's no
>> export mode which escapes the spaces in the output. Please add one. The sh 
>> mode
>> won't work either for this case.

is there a reason not to escape the whitespace by default for 
--export=configure?


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to