On Wed, Oct 03, 2012 at 02:19:02PM -0700, Alan Irwin wrote: > On 2012-10-03 11:57-0700 Alan W. Irwin wrote: > > > On 2012-10-03 16:03+0100 Andrew Ross wrote: > > > >> I think with respect to your particular issue [with gcj-4.7: error: > > utf8: No such file or directory] > >> it is probably that the --encoding option should be set to utf-8 not utf8. > >> This works fine with openjdk. Can > >> you check with gcj to see if it fixes your problems? > > > > That sounded like a good idea, but it didn't work. > > > > gcj-4.7: error: utf-8: No such file or directory > > > > However, since the string is changed from utf8 to utf-8 in the > > error message, we know exactly what part of our build system is > > creating this problem for gcj. So I looked further > > at the gcj man page, and that states you specify > > encodings as > > > > --encoding=NAME > > > > which is quite a different format (double hyphen and =) than "-encoding > > utf-8". > > > > The man page also suggests the encoding NAMEs are not standardized (although > > "UTF-8" [note the upper-case] always works for gcj). > > > > So I tried "--encoding=UTF-8" everywhere (revision 12237), and that > > works for me! > > > > I believe I have finally solved this issue correctly after > much debugging of the javac command which on my system > is simply a perl wrapper script for gcj which translates > sun java style arguments (the -option value form) to > the equivalent gcj form of argument (the --option=value > form). The issue is that script stops doing any > further translation and simply passes arguments directly > through to gcj once it encounters an argument that > it does not recognize (such as a simple filename). IOW, it > is expecting the filename to be last (which seems a reasonable > assumption to me), and we didn't follow that order so > the -encoding utf8 (or whatever) arguments were not translated. > > So revision 12238 reorders the javac command line so that the filename > is last. Furthermore, although I have proved gcj recognizes all of > utf8, utf-8, and UTF-8, I have used the latter name for the encoding > because that is what the gcj man page recommends. > > Please let me know if "UTF-8" gives any trouble for your > java tool chain. (If it does, feel free to change it > to either utf8 or utf-8 since gcj recognizes those as well > according to my experiments.)
This all still works fine for me with openjdk on Ubuntu. It still leaves the issues with running the examples using openjdk with Debian testing (but not with Ubuntu). Do the examples run fine with gcj? Andrew ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
