compiling com.mysql.jdbc.Driver with gcj

Wed Oct 12 15:05:00 GMT 2005

>>>>> "Khiraly" == Khiraly <khiraly123@gmx.net> writes:

Khiraly> gcj-4.0 --classpath=../mysql-connector-java-3.1.10-bin.jar:.
Khiraly> org/dcwatch/dchub/core/*.java org/dcwatch/dchub/util/*java
Khiraly> org/dcwatch/sql/SqlConnection.java ForceInclude.java
Khiraly> --main=org.dcwatch.dchub.core.Core ../mysql-connector-java-3.1.10-bin.jar -o faszom3.out
Khiraly> org/dcwatch/sql/SqlConnection.java:6: internal compiler error:
Khiraly> Segmentation fault
Khiraly> Please submit a full bug report,
Khiraly> with preprocessed source if appropriate.
Khiraly> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
While this probably ought to work, and it is definitely a bug that it
crashes, it is more typical to do separate compilation. Try
compiling the .java files to one .o and the .jar to another, and then
link them together.
Khiraly> java/util/TreeMap.java: In class 'com.mysql.jdbc.Connection':
Khiraly> java/util/TreeMap.java: In method
Khiraly> 'com.mysql.jdbc.Connection.execSQL(com.mysql.jdbc.Statement,java.lang.String,int,com.mysql.jdbc.Buffer,int,int,boolean,boolean,java.lang.String,boolean,byte)':
Khiraly> java/util/TreeMap.java:2916: error: verification error at PC=644
Note that there is a known bug where the error is reported against the
wrong location. This verification error doesn't really occur in
TreeMap.
The verifier used in this case in 4.0 has a few known bugs,
apparently the .jar triggers one of them. One option would be to
compile your application "BC". There is some information about doing
this here:
http://gcc.gnu.org/wiki/How%20to%20BC%20compile%20with%20GCJ
This is how we compile the applications we ship in FC.
Tom