<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to patches</title><link href="https://sourceforge.net/p/jpype/patches/" rel="alternate"/><link href="https://sourceforge.net/p/jpype/patches/feed.atom" rel="self"/><id>https://sourceforge.net/p/jpype/patches/</id><updated>2012-06-26T07:57:09Z</updated><subtitle>Recent changes to patches</subtitle><entry><title>Simple patch for getDefaultJVMPath on Linux</title><link href="https://sourceforge.net/p/jpype/patches/10/" rel="alternate"/><published>2012-06-26T07:57:09Z</published><updated>2012-06-26T07:57:09Z</updated><author><name>Joril</name><uri>https://sourceforge.net/u/joril/</uri></author><id>https://sourceforge.netc9986076ed91565b1034931e5557f220f4caa472</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I wrote a simple implementation of getDefaultJVMPath for Linux, it just checks a list of known locations. Tested on Ubuntu 10.04&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Building for OS X Lion (2)</title><link href="https://sourceforge.net/p/jpype/patches/9/" rel="alternate"/><published>2012-05-04T08:51:13Z</published><updated>2012-05-04T08:51:13Z</updated><author><name>rik0</name><uri>https://sourceforge.net/u/rik0/</uri></author><id>https://sourceforge.neta9af7b6c1a15a3f323258b34f9f678852e3b2824</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I tried to comment on the other "Building for OS X Lion" patch, but I'm not allowed.&lt;br /&gt;
Essentially, instead of hard-coding another Java path, I use /usr/libexec/java_home to get the current one.&lt;/p&gt;
&lt;p&gt;So far so good. I'm using it for Neo4J and for now it works.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Building for OS X Lion</title><link href="https://sourceforge.net/p/jpype/patches/8/" rel="alternate"/><published>2012-02-28T01:57:03Z</published><updated>2012-02-28T01:57:03Z</updated><author><name>Matt</name><uri>https://sourceforge.net/u/magaudet/</uri></author><id>https://sourceforge.netf5437a1e57876c0b1a4ab0be6a5e8fd31205d20f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I've had some success (can at least do a java.lang.System.println() call) with the attached setup.py.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Mac OS X users might use other JDK</title><link href="https://sourceforge.net/p/jpype/patches/7/" rel="alternate"/><published>2012-02-19T18:08:29Z</published><updated>2012-02-19T18:08:29Z</updated><author><name>fabien-duchene</name><uri>https://sourceforge.net/u/fabien-duchene/</uri></author><id>https://sourceforge.net2fc9240b39efd65782dcd20b36301af3d7a3f941</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Since Mac OS X users might use other JDK (eg: openjdk), you might want to take this in account.&lt;br /&gt;
here is my modified version of the setup script.&lt;/p&gt;
&lt;p&gt;cheers.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>slightly better getDefaultJVMPath in linux</title><link href="https://sourceforge.net/p/jpype/patches/6/" rel="alternate"/><published>2011-12-27T11:00:17Z</published><updated>2011-12-27T11:00:17Z</updated><author><name>Miguel Angel Rasero</name><uri>https://sourceforge.net/u/skuda/</uri></author><id>https://sourceforge.net50a41f399920ba8d49b82273dda87429002b249c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I am using JPype in linux and i have been getting problems with the way the path of libjvm.so it is detected, this a more robust way to get it, not perfect still but better anyway.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Support for freebsd added</title><link href="https://sourceforge.net/p/jpype/patches/5/" rel="alternate"/><published>2010-02-19T17:15:38Z</published><updated>2010-02-19T17:15:38Z</updated><author><name>Pascal Chambon</name><uri>https://sourceforge.net/u/pchambon/</uri></author><id>https://sourceforge.netfc79a17838be7e933bf9a82809ad26ef07e1e0ef</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Here is a modified setup.py which allows compilation of jpype on freebsd8.&lt;/p&gt;
&lt;p&gt;It's mainly a matter of removing "ld" library and modifying some java paths.&lt;/p&gt;
&lt;p&gt;Regards, &lt;br /&gt;
Pascal&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Support for Hpux, AIX and Solaris</title><link href="https://sourceforge.net/p/jpype/patches/4/" rel="alternate"/><published>2009-11-05T20:51:03Z</published><updated>2009-11-05T20:51:03Z</updated><author><name>Jan Stürtz</name><uri>https://sourceforge.net/u/stuertz/</uri></author><id>https://sourceforge.net1205250c376a83c172f7a41d0a7952ba946e8dae</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Patch to additionally  support platforms HPUX, AIX and Solaris.&lt;br /&gt;
- contains a fix with a core dump in JPypeException with messages larger the 256 chars.&lt;br /&gt;
- uses set in favour of sets.Set if we have python 2.6 to avoid Deprecation Warning&lt;/p&gt;
&lt;p&gt;minimal tested on &lt;br /&gt;
- hpux11.11 with gcc 4.3,&lt;br /&gt;
- aix5.2 with gcc 4.3,&lt;br /&gt;
- sunos 5 with gcc 4.3,&lt;br /&gt;
and linux2 with gcc4.3&lt;/p&gt;
&lt;p&gt;Known Issues:&lt;br /&gt;
On HPUX the python interpreter must be invoked with LD_PRELOAD_ONCE=&amp;lt;path&amp;gt;/libjvm.sl&lt;br /&gt;
because of problems of the dl on hpux with shhared libs containing thread local storage.&lt;br /&gt;
see also: &lt;a href="http://docs.hp.com/en/JDKJRE60RN/jdk_rnotes_6.0.05.html#TLS" rel="nofollow"&gt;http://docs.hp.com/en/JDKJRE60RN/jdk_rnotes_6.0.05.html#TLS&lt;/a&gt;&lt;br /&gt;
and &lt;a href="http://docs.hp.com/en/5187-0701/ch07s09.html" rel="nofollow"&gt;http://docs.hp.com/en/5187-0701/ch07s09.html&lt;/a&gt;&lt;br /&gt;
I think HP has to compile java with +tls=dynamic. Until this we have to use LD_PRELOAD_ONCE&lt;/p&gt;
&lt;p&gt;On AIX:&lt;br /&gt;
There is a problem with commandline arguments like '-ea' on startJVM, which didn't get through.&lt;br /&gt;
I assume this is a bug with the IBM-AIX java implementation. &lt;/p&gt;
&lt;p&gt;The patch was created on 0.5.4.1 zip file.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>SRPM Package</title><link href="https://sourceforge.net/p/jpype/patches/3/" rel="alternate"/><published>2009-03-03T10:10:05Z</published><updated>2009-03-03T10:10:05Z</updated><author><name>akolev</name><uri>https://sourceforge.net/u/akolev/</uri></author><id>https://sourceforge.net99b8a805036f000af619bb5a80fe456a43ac27d7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Basic draft of spec file for Fedora 10 Package. Todo:&lt;br /&gt;
* Fix English parts :-)&lt;br /&gt;
* Supply .tar.gz tarrball (currently zip only)&lt;br /&gt;
* Add JAVA_HOME building requirement/auto assignement&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Support setuptools building egg and ubuntu gutsy sun java 6</title><link href="https://sourceforge.net/p/jpype/patches/2/" rel="alternate"/><published>2008-02-22T10:51:27Z</published><updated>2008-02-22T10:51:27Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net4f599852e00a0a52446b332bce422f7ef90e0d82</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hey @all,&lt;/p&gt;
&lt;p&gt;i have added an patch for the version JPype-0.5.3 to support Ubuntu Gutsy Sun Java6 Version ...&lt;/p&gt;
&lt;p&gt;To support python egg i changed the import from distutils to setuptools. (Now we can it publish to pypi an use it in buildout) ;-)&lt;/p&gt;
&lt;p&gt;Cya &lt;/p&gt;
&lt;p&gt;Josip&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Support for JDK-1.5_10 and up</title><link href="https://sourceforge.net/p/jpype/patches/1/" rel="alternate"/><published>2007-06-01T09:51:35Z</published><updated>2007-06-01T09:51:35Z</updated><author><name>Gottfried Ganßauge</name><uri>https://sourceforge.net/u/ganssauge/</uri></author><id>https://sourceforge.net19ab510ea4efdc3fa9d42e347b04a917bc11ee0b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;In JDK-1.5_10 Sun changed certain undocumented "features" in jni.h such that JPype doesn't compile with this release of the JDK.&lt;br /&gt;
Among those are the "functions" pointers in struct JavaVM_ and struct JNIEnv_ and struct JavaVM_ alltogether.&lt;br /&gt;
Fortunately the official way of doing things still works so I made a patch against JPype 0.5.2.1 to make it compile again.&lt;br /&gt;
Unfortunately I didn't find the generator for src/native/common/jp_javaenv_autogen.cpp so I had to patch the file itself although it carries a warning not to edit it manually.&lt;br /&gt;
I tested my patch with JDK-1.5_10 and JDK-1.4.2_10.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>