Bug#300753: Success for jdbc3

[Wolfgang Baer]

Hi Markus,

Markus Schaber wrote:
> Hi,
> 
> I now can successfully build it using libant1.6, kaffe and jikes, using
> an additional small source patch. I can build with and without SSL, but
> I can only build the jdbc3 version.
> 
> Building the JDBC version (forced with -D switches) fails due to not
> implemented abstract methods.
> 
> What's the best to come around this limit?

Thats why it needs to build against the non-free jdks:

Against j2sdk1.3 (implements JDBC 2.0 interface) for JDBC2 jars.
Against j2sdk1.4 (implements JDBC 3.0 interface) for JDBC3 jars.

All the free vm's using recent gnu classpath libraries are
already implementing JDBC 3.0 interfaces. Therefore these can only
be used for JDBC3 jar building.

I have exactly the same problem with moving xalan2 to main. It depends
on DOM Level 2 and free vms are already at Level 3.

I had success with using gcj-3.4 as it's based on an older gnu classpath
release. Maybe try against gcj-3.3 or gcj-3.4 - don't know at which
JDBC level they are. Give them a try :-)

Wolfgang