This is a known issue and it has been decided not to fix this problemsince a workaround exists which would be more ideal.
The workaround at this time is to use the new XST parser.
In order to use the new XST parser, add the following switch in the XST script:
-use_new_parser yes
The same switch can alsobe addedto the Other XST Command Line Options field present in the XST Synthesis Options Category within the ISE GUI.