On Wed, Oct 31, 2007 at 09:42:05AM +0100, Fabian Groffen wrote: > On 30-10-2007 22:33:56 +0000, Ying Zhang wrote: > > Added a new variable in build.properties (build_compiler) to make > > compiler switching easier. > > http://ant.apache.org/manual/CoreTasks/javac.html > > <quote> > It is possible to use different compilers. This can be specified by > either setting the global build.compiler property, which will affect all > <javac> tasks throughout the build, or by setting the compiler > attribute, specific to the current <javac> task. Valid values for either > the build.compiler property or the compiler attribute are: > </quote> > > In other words, don't do what you just did. Just rely on standard > behaviour, and set build.compiler in your build.properties to gcj if you > want to build with gcj.
Also be aware that on systems without Sun Java, there's also a "javac" that calls gcj's compiler; hence, "javac" does not mean Sun Java. Moreover, I thought the goal of the whole exercise was to get the xrpcwrapper compiled with both, Sun Java and gcj, right? Hence, what is/was the reason to (try to) force the use of "javac"? Stefan -- | Dr. Stefan Manegold | mailto:[EMAIL PROTECTED] | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 | ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Monetdb-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-developers
