[jira] [Updated] (THRIFT-3271) Could not find or load main class configtest_ax_javac_and_java on some non-english systems

["Jens Geyer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/THRIFT-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Geyer updated THRIFT-3271:
-------------------------------
    Attachment: THRIFT-1787-Thrift-compiling-Java-Problem.patch

Same patch as posted in THRIFT-1787.

> Could not find or load main class configtest_ax_javac_and_java on some non-english systems
> ------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-3271
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3271
>             Project: Thrift
>          Issue Type: Bug
>          Components: Build Process
>         Environment: - German openSuse 13.2
> - path with Umlauts (Arbeitsfläche) within
>            Reporter: Jens Geyer
>            Assignee: Jens Geyer
>             Fix For: 0.9.3
>
>         Attachments: THRIFT-1787-Thrift-compiling-Java-Problem.patch
>
>
> The JVM fails to locate the *.class file within an path that contains (e.g.) Umlauts, such as in {{~/Arbeitsfläche/Thrift because}} of LC_ALL=C being set by configure. The symptom is, that 
> {code}
> java configtest_ax_javac_and_java
> {code}
> works fine when invoked by hand, but configure fails at exactly that step, even with an explictly set classpath -cp . with the message:
> {code:title=config.log}
> Running "/usr/bin/javac configtest_ax_javac_and_java.java"
> Running "/usr/bin/java configtest_ax_javac_and_java"
> Error: Could not find or load main class configtest_ax_javac_and_java
> {code}
> Temporarily adding {{LC_ALL=}} right before the Java check solves the issue. The other workaround is to use a path using only {{LC_ALL=C}}-compatible characters.
> It seems to be related to the issue mentioned at http://lists.gnu.org/archive/html/autoconf/2011-10/msg00000.html and I eventually came up with the reason because after checking the usual suspects like CLASSPATH and the like I finally wondered whether it might have something to do with the fact that Java emits english error messages during configure, but german messages otherwise.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)