Re: Hardcoded java paths in shared objects [was:Re: Building is too difficult and release of a first pre-built egg]
On 2011-06-02 18:26, Andi Vajda wrote: On Jun 2, 2011, at 3:10, Philippe Ombredannepombreda...@gmail.com wrote: On 2011-06-01 20:54, Roman Chyla wrote: Note that the location of the java that was used for the project built will be hardcoded inside the dynamic library, but I plan to change the header and set a few standard paths there. This is actually worse than I thought: not only the java location seems hardcoded in the shared object as a hard path to the libs folder, but also there is an implied dep on setuptools via pkg_resources So for now, you cannot even build on a jdk and deploy on a jre. If the solution to this is to remove the hardcoded paths and expect the dynamic linker to find the dependencies via some environment variable like LD_LIBRARY_PATH you'd be creating a security vulnerability. This is how I did it originally (years ago) and people complained about it so I switched to hardcoded paths for shared library dependencies wherever possible. Andi: could we come at least with a build option to enable this? I am sure there are bad ways and correct ways to address possible security issues as there are many packages that rely on this. And given the variety of *nix locations for a JVM and the various JVMs available we need some flexibility there imho. Leave it hardcoded by default allright and a bbuild flag to get it working otherwise if ones wants to build it this way? -- Cordially Philippe philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com nexB - Open by Design (tm) - http://www.nexb.com http://eclipse.org/atf - http://eclipse.org/soc - http://eclipse.org/vep http://drools.org/ - http://easyeclipse.org - http://phpeclipse.com
Hardcoded java paths in shared objects [was:Re: Building is too difficult and release of a first pre-built egg]
On 2011-06-01 20:54, Roman Chyla wrote: Note that the location of the java that was used for the project built will be hardcoded inside the dynamic library, but I plan to change the header and set a few standard paths there. This is actually worse than I thought: not only the java location seems hardcoded in the shared object as a hard path to the libs folder, but also there is an implied dep on setuptools via pkg_resources So for now, you cannot even build on a jdk and deploy on a jre. -- Cordially Philippe philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com nexB - Open by Design (tm) - http://www.nexb.com http://eclipse.org/atf - http://eclipse.org/soc - http://eclipse.org/vep http://drools.org/ - http://easyeclipse.org - http://phpeclipse.com
[jira] [Reopened] (PYLUCENE-10) Building Pylucene is way too difficult
[ https://issues.apache.org/jira/browse/PYLUCENE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philippe Ombredanne reopened PYLUCENE-10: - I would like to reopen this issues on two grounds: 1/ I have started http://code.google.com/a/apache-extras.org/p/pylucene-extra and two other folks have already joined in to help 2/ there are likely things that can be done in the code to make building easier on the one hand and to make built eggs more portable, in particular less dependent on a certain java runtime filesystem location Building Pylucene is way too difficult -- Key: PYLUCENE-10 URL: https://issues.apache.org/jira/browse/PYLUCENE-10 Project: PyLucene Issue Type: Bug Environment: Linux, Windows Mac Reporter: Philippe Ombredanne Labels: build, linux, mac, window The amount of work needed to make a redistributable build for a few common os is rather big Could there be an effort to provide these pre-built? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (PYLUCENE-10) Building Pylucene is way too difficult
Building Pylucene is way too difficult -- Key: PYLUCENE-10 URL: https://issues.apache.org/jira/browse/PYLUCENE-10 Project: PyLucene Issue Type: Bug Environment: Linux, Windows Mac Reporter: Philippe Ombredanne The amount of work needed to make a redistributable build for a few common os is rather big Could there be an effort to provide these pre-built? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Building is too difficult and release of a first pre-built egg
Howdy! I think it is way too hard to build PyLucene for the mere mortals. Getting eggs is yet another level of difficulties I created an issue: https://issues.apache.org/jira/browse/PYLUCENE-10 and started an Apache extra project, releasing a first egg for the Linux 64/Python 2.5.2/Oracle JDK 1.5 combo http://code.google.com/a/apache-extras.org/p/pylucene-extra/downloads/list I hope that can help some folks. -- Cordially Philippe philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com nexB - Open by Design (tm) - http://www.nexb.com http://twitter.com/pombr http://eclipse.org/atf - http://eclipse.org/soc - http://eclipse.org/vep http://drools.org/ - http://easyeclipse.org - http://phpeclipse.com
