<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://blog.gmane.org/gmane.comp.java.classpath.devel">
    <title>gmane.comp.java.classpath.devel</title>
    <link>http://blog.gmane.org/gmane.comp.java.classpath.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9880"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9865"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9860"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9855"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9851"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9846"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9843"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9842"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9840"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9836"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9830"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9826"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9806"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9803"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9802"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9798"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9775"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9774"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9773"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.classpath.devel/9760"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9880">
    <title>java.lang.TypeNotPresentException when using reflection</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9880</link>
    <description>I have been attempting to use reflection, in particular to get the
superclass of a particular class, but this seems to fail when using
Classpath v0.97.2 with JamVM 1.5.0.

In a stripped down version of what I am trying to achieve, I am attempting
to run the following code, which I have unceremoniously poached from
http://developer.classpath.org/pipermail/classpath/2006-November/001605.html:

public class Main {

    static class A extends ArrayList&lt;String&gt; {};

    public static void main(String[] args)
    {
        A a = new A();
        Object x = a;
        ((Collection)x).add(new Byte((byte) 1));
        System.out.println(x.getClass().getGenericSuperclass());
        System.out.println("We have a list parametrized with: " +

((ParameterizedType)x.getClass().getGenericSuperclass()).getActualTypeArguments()[0]);
    }
}

This code is compiled using the Eclipse Compiler and run on a PowerPC
implementation. Classpath was compiled using Sun's javac compiler, version
1.6. Running the code, however, yields th</description>
    <dc:creator>Tom Spencer</dc:creator>
    <dc:date>2008-08-13T17:20:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9865">
    <title>Help a noob?</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9865</link>
    <description>Hey there.

I'm trying to get classpath running on my sgi (old stuff, I know).  Can
it be done?  I wanted to find out.

I have a very small java app I really want to get working.  Right now, I
only have Java 1.4 on this machine, but I really need 1.5.  I don't care
if 90% of java doesn't work.

OK, I've got all the underlying packages installed (gconf, orbit, cairo,
idl, etc etc etc.  Took me quite awhile to get them all).

In any event When I do a ./configure --disable-plugin, I get a complaint
about missing javac -source 1.5

But that's weird.  This is supposed to be a REPLACEMENT for java...why
would it need javac?  How can I get around the need for javac?  And why
is it needed anyway?

Also, I notice the "WARNING...in the code below: checking jni_md.h
support... configure: WARNING: no"

Can anyone help? (or make a suggestion of how to get a java 1.5 running
on an sgi?)

Thanks

Geoff

---------
checking build system type... mips-sgi-irix6.5
checking host system type... mips-sgi-irix6.5
checking target sy</description>
    <dc:creator>Greene, Geoffrey N</dc:creator>
    <dc:date>2008-08-12T18:59:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9860">
    <title>FW: Help a noob?</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9860</link>
    <description>




</description>
    <dc:creator>Greene, Geoffrey N</dc:creator>
    <dc:date>2008-08-12T20:11:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9855">
    <title>Server downtime</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9855</link>
    <description>Hi,

I need to take the server down to investigate a possible failed disk in 
the software RAID.  I am hoping that it's just a Linux or Xen bug. Also, 
I'd like to upgrade Xen to a more modern version if possible.

I'm planning to take the server down in about 3 hours (around 2pm 
Pacific Time).  Hopefully, it won't take me too long to investigate 
and/or upgrade it.

There is always the possibility that things won't go well with the RAID 
or the upgrade.  I only have the one server online, so if I encounter 
any big problems, please be patient as I try to figure out the best way 
to recover.  Luckily, I do have recent backups.

This will affect jimpick.com, kaffe.org, developer.classpath.org, 
planet.classpath.org, and icedtea.classpath.org.

While the server is down, my jimpick.com/kaffe.org email addresses will 
not be working.  I can still be reached at my backup email address at 
&lt;jim.pick&lt; at &gt;gmail.com&gt;.

Cheers,

  - Jim


</description>
    <dc:creator>Jim Pick</dc:creator>
    <dc:date>2008-08-09T18:26:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9851">
    <title>Jikes RVM 3.0.0 released</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9851</link>
    <description>We're very happy to announce the release of Jikes RVM version 3.0.0.

The road towards 3.0 began just about two years ago and a large number of
people, both on the core team and from our user community at large, have
contributed to making it a success. Thank You!

The release is available for download at
http://downloads.sourceforge.net/jikesrvm/jikesrvm-3.0.0.tar.bz2

The detailed release notes for major changes since 2.9.3 can be found below
or in JIRA (http://jira.codehaus.org/browse/RVM/fixforversion/13530),
but we'd like to highlight some of the larger themes that went into the 3.0
release (many of which have already been released in  the 2.9.x releases
we've made along the way).
  ** Normalization of source code and build process
    *** Complete rewrite of the build/test systems to use ant.
    *** Jikes RVM can be developed in Eclipse using the JDT
    *** Extensive restructuring of package structure
    *** Removal of VM_ and OPT_ prefixes from all source files.
  ** Increased system stability and p</description>
    <dc:creator>Ian Rogers</dc:creator>
    <dc:date>2008-08-07T21:43:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9846">
    <title>Java Transaction API</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9846</link>
    <description>Dear all,

It seems Classpath includes the full set of interfaces for the Java
Transaction API:

http://en.wikipedia.org/wiki/Java_Transaction_API

while the J2SE spec. only prescribes three exceptions used by CORBA:

http://java.sun.com/javase/6/docs/api/javax/transaction/package-summary.html

They were (apparently) added by Warren Levy and Tom Tromey back in 2001.

Gentoo currently has a JTA package that uses the version of these
interfaces from Sun.  These still seem to under a proprietary license
(though IANAL):

http://java.sun.com/javaee/technologies/jta/

even though there is presumably also a GPL version in Glassfish.

How do other distributions handle this? Is it worth our while moving
these out of GNU Classpath into a separate package so people can use
the Free Classpath versions?

Thanks,
</description>
    <dc:creator>Andrew John Hughes</dc:creator>
    <dc:date>2008-07-31T21:52:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9843">
    <title>HTTPS/SSL problem</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9843</link>
    <description>Hi,
a classpath user reported a problem with SSL on the jalimo list.

When connecting to a server through HTTPS/SSL he gets:

java.io.EOFException
   at
gnu.javax.net.ssl.provider.SSLSocketImpl.doHandshake(SSLSocketImpl.java:445)
   at
gnu.javax.net.ssl.provider.SSLSocketImpl$SocketOutputStream.write(SSLSocketImpl.java:91)
   at java.io.OutputStream.write(OutputStream.java:86)

This is caused from SSLSocketImpl.java line 445:

int i = sockIn.read();
if (i == -1)
throw new EOFException();

Now my question is: What can be the reason that the other side closed
the connection (at least I assume that is the case, when sockIn.read()
return -1) What is the best way to debug this?

Has anyone successfully connected to an HTTPS/SSL server using GNU
Classpath already?

Regards
Robert

</description>
    <dc:creator>Robert Schuster</dc:creator>
    <dc:date>2008-07-17T20:35:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9842">
    <title>Issues while using ImageWriter in ubuntu 64bit</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9842</link>
    <description>
Hello all,

My problem is actually a known bug in linux with the ImageWriter class while
writing jpeg images:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28447

Also, somebody's committed a patch to this problem here:
http://gcc.gnu.org/ml/java-patches/2005-q1/msg00018.html

Now the issue is i am not too sure how i should apply this patch? it seems
someone has checked in a whole lot of files to fix this? Do i need to
recompile the kernel or something? Can anyone help me with this fix, does
anyone have a simpler fix?

Thanks...
</description>
    <dc:creator>ndesk1900</dc:creator>
    <dc:date>2008-07-16T04:08:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9840">
    <title>META-INF/INDEX.LIST</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9840</link>
    <description>What is this file and why is it accessed at startup? At the startup of every Java program, it would appear that the paths: "/META-INF/INDEX.LIST" and "" are have the stat file operation applied to them.

I am working on a research project at UIUC and I have an issue with this happening due to the nature of the file system which the custom JVM we have created works. If anyone has information relating to where / why these accesses are made it would be very appreciated. Essentially I need to figure out what they are supposed to be accomplishing since it doesn't seem to matter that they fail. Avoiding them all together or routing them through an alternative means would be ideal.

Thanks for any responses,
J.J. Sestrich


</description>
    <dc:creator>jsestri2&lt; at &gt;uiuc.edu</dc:creator>
    <dc:date>2008-07-11T21:18:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9836">
    <title>classpath build problems with libtool 2.2.4</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9836</link>
    <description>Hi,
I am currently trying to build classpath (0.93) in an environment using
libtool 2.2.4.

I basically disable all optional external dependencies and compile with
jikes:

  --with-jikes=jikes \
  --with-fastjar=fastjar \
  --with-glibj \
  --disable-local-sockets \
  --disable-alsa \
  --disable-gconf-peer \
  --disable-gtk-peer \
  --disable-plugin \
  --disable-dssi \
  --disable-examples \
  --disable-tools \
  --with-glibj-dir=${STAGING_DATADIR}/classpath-initial \
  --with-native-libdir=${STAGING_LIBDIR}/classpath-initial \
  --includedir=${STAGING_INCDIR}/classpath-initial \

This is the error I get from libtool:

i686-linux-libtool: link: unsupported hardcode properties
i686-linux-libtool: link: See the libtool documentation for more
information.
i686-linux-libtool: link: Fatal configuration error.

Which is caused by the following command:

make[3]: Entering directory
`/home/rob/oe/beagle/tmp/work/i686-linux/classpath-initial-0.93-r1/classpath-0.93/native/jni/java-net'
/bin/sh ../../../i686-linux-li</description>
    <dc:creator>Robert Schuster</dc:creator>
    <dc:date>2008-07-06T15:06:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9830">
    <title>Crypto functions supported.</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9830</link>
    <description>Hello all!

I'm a new member and navigating into the classpath
&lt;http://developer.classpath.org/pipermail/classpath/&gt;page
I realized the info is complete. However for now it's a little difficult to
know if the issues I'm searching are completely support for the gnu.

I'm searching a java examples (not too interested in the source code, only
the "black boxes") for the following process.

Please could you tell me if all are supported by GNU ClassPath into the
Crypto functions? Thanks in advance.

1- KeyPair generation in assymetric encryption.
2- 3DES key generation.
3- To guard or store the generated keys.
4- Assymetric encryption and decryption. RSA.
5- Random number generation.
6- To generate and validate DSS.
7- Support of X.509 certificate (e.g. entity knows the seriousness of a
digital signature generator).

Thanks and regards.

José Ignacio Saavedra Vivas
Systems Engineer
</description>
    <dc:creator>NACHO SAAVEDRA</dc:creator>
    <dc:date>2008-06-28T02:36:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9826">
    <title>array overflow in local.c</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9826</link>
    <description/>
    <dc:creator>Robert Schuster</dc:creator>
    <dc:date>2008-06-27T09:52:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9806">
    <title>Other class libraries</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9806</link>
    <description>Since OpenJDK has been released, I've noticed that a tendency has
arisen to not treat
that codebase with the same 'don't look if working on the same code'
approach we had
when it was proprietary.  When working on GNU Classpath, we still need
to be careful
about cross-pollination between codebases, even though the OpenJDK
class libraries
are under (nearly) the same license.

This also applies for other class libraries, namely Harmony's.

Thanks,
</description>
    <dc:creator>Andrew John Hughes</dc:creator>
    <dc:date>2008-06-24T14:20:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9803">
    <title>CACAO 0.99.1 released.</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9803</link>
    <description>CACAO 0.99.1 released.

This is a bug-fix release.  Here is a short list of the most important
changes:

  * Fixed compilation of OpenJDK code (libltdl related).
  * Imported new gnu/java/lang/CPStringBuilder.java to fix OOMEs.
  * Fixed abort with OpenJDK's java binary when exiting.

CACAO uses GNU Classpath as default Java runtime library and supports
upstream releases or CVS snapshots.  This release requires GNU
Classpath 0.96 or higher to build and was tested against GNU Classpath
0.97.2 on a number of various platforms.

CACAO's ./configure has some options for Java runtime configuration,
namely:

  --with-java-runtime-library=&lt;type&gt;
  --with-java-runtime-library-prefix=&lt;dir&gt;
  --with-java-runtime-library-classes=&lt;path&gt;
  --with-java-runtime-library-libdir=&lt;dir&gt;

For detailed information, use ./configure --help.

Currently supported JIT compiler architectures are:

  * alpha
  * arm
  * i386
  * m68k (broken)
  * mips
  * powerpc
  * powerpc64
  * s390
  * sparc64
  * x86_64

Information about working a</description>
    <dc:creator>Christian Thalinger</dc:creator>
    <dc:date>2008-06-17T19:43:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9802">
    <title>Problem with TLS client authentication (bad_certificate)</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9802</link>
    <description>Hi,

I am working an a project that needs TLS with client authentication on 
an embedded system (ARM-linux) with keys stored in pkcs12. I have 
successfully ported the jamvm and classpath on this plattform. Now
I am working on the TLS part on a virtual machine not directly on the 
embedded bord. In this development-environment I am using this setup:

Client:

  - Debian Linux 2.6.18-6-686
  - jamvm 1.5.1
  - classpath 0.97.1
  - bouncycastle provider bcprov15-139 (pkcs12 support)

Server:

  - Debian Linux
  - Sun jdk 1.6


The problem is, a BAD_CERTIFICATE error occurs during the handshake.

The client answers server-hello, with write_certificate, 
write-client-key-exchange and write_certificate_verify. After that the 
client recieves the bad_certificate alert from the server caused by 
"certificate verify message signature error".

The private key of the client is sored in a pkcs12 file loaded via 
bcprovider, the trusted key of the server is stored in a gkr.


Thanks,

   gerhard
</description>
    <dc:creator>Gerhard Fliess</dc:creator>
    <dc:date>2008-06-17T07:56:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9798">
    <title>CACAO 0.99 released.</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9798</link>
    <description>CACAO 0.99 "Just one step left..." released.

This is a major feature enhancement and bug-fix release.  Here is a
short list of the most important changes:

  * Initial support to use OpenJDK as Java runtime library.
  * Fixed memory leak in Boehm-GC.
  * Boehm-GC updated to version 7.1.
  * Removed libltdl dependency.
  * Renamed --with-classpath configure options to
    --with-java-runtime-library.
  * Renamed --with-jre-layout to --enable-layout.
  * Replaced --with-classpath-includedir with --with-jni_h and
    --with-jni_md_h to better support OpenJDK/IcedTea builds.
  * Use 8-byte stack-slots on all architectures.
  * Faster C-to-Java calls.
  * Removed genoffsets, cross-compilation is now much easier.
  * Implemented Class.isAnonymousClass(), isLocalClass() and
    isMemberClass() for GNU Classpath.
  * Annotation support.
  * Assertion support.
  * Linenumber table code rewritten.
  * Exception table code rewritten.

The major feature enhancement of this release is the OpenJDK support.
CACAO's libjvm</description>
    <dc:creator>Christian Thalinger</dc:creator>
    <dc:date>2008-06-14T14:54:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9775">
    <title>Savannah has Mercurial!</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9775</link>
    <description>I just noticed this announcement when submitting the news announcement
for 0.97.2.

What do people think to the idea of switching?  Maybe post 0.98?

</description>
    <dc:creator>Andrew John Hughes</dc:creator>
    <dc:date>2008-06-06T02:37:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9774">
    <title>Classpath 0.97.2 released!</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9774</link>
    <description>We are proud to announce the release of GNU Classpath 0.97.2, the
second bugfix release for GNU Classpath 0.97.

GNU Classpath, essential libraries for java, is a project to create
free core class libraries for use with runtimes, compilers and tools
for the java programming language.

The GNU Classpath developer snapshot releases are not directly aimed
at the end user but are meant to be integrated into larger development
platforms. For example JamVM, CACAO and Kaffe can make use of an
installed copy of GNU Classpath 0.97.2, while GCC (gcj) will use the
developer snapshots as a base for future versions. For more projects
based on GNU Classpath, see
http://www.gnu.org/software/classpath/stories.html

This is the second of a new series of bugfix releases that follow a
major (0.x) release. A 0.x.y release will only contain minor bug
fixes. It will not cause major changes in the functionality of GNU
Classpath, either for better or for worse.

With this bugfix release, the following issues have been resolved:

  </description>
    <dc:creator>Andrew John Hughes</dc:creator>
    <dc:date>2008-06-06T02:33:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9773">
    <title>New GNU Classpath developer Joshua Sumali</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9773</link>
    <description>Hi all,

I am happy to announce that Joshua is now one of our active hackers with
commit access. Joshua has been working on integrating gjdoc into the
main classpath tree. Something which we have wanted for a long time.

Joshua please post a patch and ChangeLog entry for adding yourself to
the AUTHORS file to the classpath-patches mailinglist. You can consider
that patch pre-approved of course so feel free to commit it immediately
as a test of your new powers, if you want to do something that is the
least likely to break the build :) But remember that with power comes
responsibility! (*)

Thanks,

Mark

(*) http://www.gnu.org/software/classpath/docs/hacking.html
</description>
    <dc:creator>Mark Wielaard</dc:creator>
    <dc:date>2008-05-27T19:16:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9760">
    <title>javah in 0.97+ -&gt; trouble</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9760</link>
    <description>Hi,
from 0.97 onwards, classpath needs a working javah tool. Such a program
is provided by classpath' tools.zip but needs a working runtime and
class library first.

Earlier classpath releases had pre-generated header files and needed no
javah program.

Someone with less knowledge of the subtile changes in each classpath
release wanted to introduce 0.97.1 in OE as the class library which runs
the compiler etc. This currently fails because in my previous bootstrap
effort I did not care to provide a working javah (it would be from
classpath 0.93).

I would like to suggest the following way to fix this issue: The build
system should allow using the just built javah application being run
with a provided java executable. This would be less pain for me and
would probably also benefit other cross compilation efforts.

E.g. --enable-builtin-javah should set the javah executable to some
script which is generated (perhaps from the real gjavah) which is run
with the java vm specified by --with-java.

Regards
Robert

</description>
    <dc:creator>Robert Schuster</dc:creator>
    <dc:date>2008-05-13T23:19:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.classpath.devel/9758">
    <title>gnu.xml.datatype.JAXPDatatypeFactory not there</title>
    <link>http://comments.gmane.org/gmane.comp.java.classpath.devel/9758</link>
    <description>Hi,
javax.xml.datatype.DatatypeFactory declares:

public static final String DATATYPEFACTORY_IMPLEMENTATION_CLASS =
"gnu.xml.datatype.JAXPDatatypeFactory";

The value is a fallback value which is treated as a class which is to be
instantiated. Unfortunately this class does not exist.

Has this class been renamed or has it really not been written yet?

Regards
Robert

</description>
    <dc:creator>Robert Schuster</dc:creator>
    <dc:date>2008-05-13T17:22:56</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.java.classpath.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.java.classpath.devel</link>
  </textinput>
</rdf:RDF>
