Community
Participate
Working Groups
In latest, the class Messages.java collides with the properties file messages.properties when generating the executable using gcj on Windows XP. A second problem is related to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21540. This bug prevents the class CompilerOptions from being properly compiled by gcj.
I would vote to fix the collision by moving messages.properties file to its parent folder (/org.eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler). As Olivier figured, collision got introduced when switching to new NLS format. This prevents building ecj on Win32 machines (which aren't case sensitive). Fix is trivial, candidating for RC4. We need to keep translators in the loop. Dirk - would you vote for it ?
Dani - would you vote for it ?
+1 for 3.1 RC4.
Created attachment 23662 [details] Patch that is fixing both issues In fact I got some help from Tom Tromey from Redhat about the collision problem.
With the patch, I can generate the executable. I'll try to modify the script to use the .class file version of the CompilerOptions class. This would reduce the patch.
+1 for RC4.
Fixed and released in HEAD.
messages.properties has been moved in its parent. And temporary constant fields have been added in CompilerOptions. These will be removed for 3.1.1.
Verified for Build id: I20050624-0010. (Checked that source changes were present and that the file move took proper effect in batch compiler reporting. Did nothing with gcj itself.)
Verified.