Re: GCJ ------ file type not supported by system

Christopher Friedt <[email protected]> Thu, 4 Sep 2014 07:31:23 -0400
Newsgroups gmane.comp.java.classpath.devel
Message-ID <CAF4BF-TMV2JT2beCEeJTLXi6amoU7wrcVqw4vCL3yJ0RXGQ3qA@mail.gmail.com>
--089e0115f04837f2a905023bb198
Content-Type: text/plain; charset=UTF-8

On Sep 3, 2014 12:13 PM, "Guillermo Rodriguez Garcia" <
[email protected]> wrote:
> > If someone wants to take the project, the best thing to do is to start
> > contributing patches. After all, how can the maintainer know if someone
> > is seriously willing to take his role if there lack of a serious and
> > recent contribution flow?

I've been eavesdropping on this bread a bit. Personally, I don't really
care who is maintaining classpath, but I still use it regularly for
embedded Java on several architectures.

There are even a few patches I've been using for years that I would like to
get upstream as configurable features. I did submit these to the list, if
I'm not mistaken,but never received any feedback. In particular,

1) a patch to allow mmaping special files (e.g. /dev/video0) via
MappedByteBuffer FileChannel.map()
2) a patch that implements direct ByteBuffers (i.e. reducing the JNI
overhead per-transaction) that extends the ability to CharBuffers,
ShortBuffers, LongBuffers, etc.

If I am not able to get these patches upstream (even with some reworking),
I'm effectively maintaining a fork, which I would rather not do.

A gift repository would, of course, be a welcome improvement :-)

C

--089e0115f04837f2a905023bb198
Content-Type: text/html; charset=UTF-8

<p dir="ltr"><br>
On Sep 3, 2014 12:13 PM, &quot;Guillermo Rodriguez Garcia&quot; &lt;<a href="mailto:[email protected]">[email protected]</a>&gt; wrote:<br>
&gt; &gt; If someone wants to take the project, the best thing to do is to start<br>
&gt; &gt; contributing patches. After all, how can the maintainer know if someone<br>
&gt; &gt; is seriously willing to take his role if there lack of a serious and<br>
&gt; &gt; recent contribution flow?</p>
<p dir="ltr">I&#39;ve been eavesdropping on this bread a bit. Personally, I don&#39;t really care who is maintaining classpath, but I still use it regularly for embedded Java on several architectures.</p>
<p dir="ltr">There are even a few patches I&#39;ve been using for years that I would like to get upstream as configurable features. I did submit these to the list, if I&#39;m not mistaken,but never received any feedback. In particular,</p>

<p dir="ltr">1) a patch to allow mmaping special files (e.g. /dev/video0) via MappedByteBuffer FileChannel.map()<br>
2) a patch that implements direct ByteBuffers (i.e. reducing the JNI overhead per-transaction) that extends the ability to CharBuffers, ShortBuffers, LongBuffers, etc.</p>
<p dir="ltr">If I am not able to get these patches upstream (even with some reworking), I&#39;m effectively maintaining a fork, which I would rather not do.</p>
<p dir="ltr">A gift repository would, of course, be a welcome improvement :-)</p>
<p dir="ltr">C<br>
</p>

--089e0115f04837f2a905023bb198--