Re: Compiling issue
- Posted by jimcbrown (admin) Feb 06, 2012
- 1717 views
I looked at unique_c_name() in c_decl.e and that looked correct, so the current 4.0 branch should not experience this problem.
This problem could be happening in the 4.0.3 build if TUNIX was somehow set to true. In that case, unique_c_name() would not compensate for the case-insensitivity and think CircMot.c (for CircMot.exw) and Circmot.c (for Circmot.ew) are the same.
TUNIX should not be set to true, but I can see how this might have happened: someone crosstranslated the Windows code for the release. If crosstranslation is 100% perfect, then there shouldn't be any problems, but 4.0.3 was released a while ago and it's possible some old crosstranslation bug corrupted the build (e.g. incorrectly leaving TUNIX set even though the target system was Windows).
Try 4.0.2, 4.0.1, and 4.0.0 (in that order) to see if they have the same bug. If they don't, we can be pretty sure that these defects are a result of a badly built binary and we simply will need to re-release 4.0.3
