On Sat, 15 Apr 2017, Rüdiger Meier wrote:
On 04/15/2017 12:52 AM, Petrus Hyvönen wrote:
Hi,
First, again - many thanks to all of you who made jcc work with python 3,
this is a great thing!
Now playing with linux building and I am using anaconda python distribution
and it seems like the lin
On Sat, 15 Apr 2017, Petrus Hyvönen wrote:
Hi,
First, again - many thanks to all of you who made jcc work with python 3,
this is a great thing!
Now playing with linux building and I am using anaconda python distribution
and it seems like the link library for python is called libpython3.6m.so
On 04/15/2017 12:52 AM, Petrus Hyvönen wrote:
Hi,
First, again - many thanks to all of you who made jcc work with python 3,
this is a great thing!
Now playing with linux building and I am using anaconda python distribution
and it seems like the link library for python is called libpython3.6m.
Hi,
First, again - many thanks to all of you who made jcc work with python 3,
this is a great thing!
Now playing with linux building and I am using anaconda python distribution
and it seems like the link library for python is called libpython3.6m.so
instead of the libpython3.6 that other python s
t;>>> '-framework', 'Python'],
>>>>
>>>> Any suggestions or pointers most appreciated. The relevant build errors are
>>>> below... Thanks! :-)
>>>
>>> You must ensure that the compi
nd you need to rebuild Python from sources,
using the same compiler as you're using to build JCC.
Andi..
- >8
building 'jcc' extension
creating build/temp.macosx-10.6-x86_64-2.7
creating build/temp.macosx-10.6-x86_64-2.7/jcc
creating build/temp.macosx-10.6-x86_64-2.7/jcc/so
at I did modify jcc's setup.py to add '-framework', 'Python' under
LFLAGS:
'darwin/frameworks': ['-framework', 'JavaVM'
'-framework', 'Python'],
Any suggestions or pointers most appreciat
You are right. I am stuck where I feared I would end up. I will have to
change my provider because they will not support a new Linux
distribution. Thanks for the advise.
Henri.
Op 20-10-2012 2:46, Andi Vajda schreef:
On Fri, 19 Oct 2012, Henk wrote:
Thanks, Andi. My provider has an old vers
On Fri, 19 Oct 2012, Henk wrote:
Thanks, Andi. My provider has an old version of Red Hat, that I cannot
update. The GCC version is 3.4.6 20060404. I hope I can update the GCC.
Updating the GCC from source is also not a simple procedure, it seems.
Indeed and you're running a really old versio
Thanks, Andi. My provider has an old version of Red Hat, that I cannot
update. The GCC version is 3.4.6 20060404. I hope I can update the GCC.
Updating the GCC from source is also not a simple procedure, it seems.
Henry
Op 19-10-2012 19:31, Andi Vajda schreef:
On Oct 19, 2012, at 1:50, Henk
On Oct 19, 2012, at 1:50, Henk wrote:
> Hello,
>
> I am trying to build JCC on Linux Redhat 7.2 2.96-129.7.2. Installed
> JDK1.6.0_37, used setuptools.py (patched it) or PIP, and both with the same
> result. I doing this from a virtualenv.
If that 2.96-129.7.2 version number is the version
Hello,
I am trying to build JCC on Linux Redhat 7.2 2.96-129.7.2. Installed
JDK1.6.0_37, used setuptools.py (patched it) or PIP, and both with the
same result. I doing this from a virtualenv.
I get these errors and don't know what they mean. Hope you have any ideas.
Henry
Error text (extrac
Please, don't hijack a thread, start a new one when switching topics. Your
questions below have nothing to do with building on Python 2.4.
On Jun 17, 2012, at 5:39, "Petrus Hyvönen" wrote:
> I am trying to clean up my wrap script and comes to some questions.
>
> Is there a way to see if a met
Dear Andi,
I am trying to clean up my wrap script and comes to some questions.
Is there a way to see if a method or constructor is now wrapped due to that any
of its inputs/outputs are not wrapped? (to make sure that I haven't missed any
--package)
If i "--package java.io" does that mean that
Hi Felix,
On Tue, 12 Jun 2012, Felix Schwarz wrote:
I'm trying to build JCC on Python 2.4.3 (CentOS 5). However during the
compilation I get this error:
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size
I should add that I'm using OpenJDK 1.6:
java-1.6.0-openjdk-1.6.0.0-1.25.1.10.6.el5_8
java-1.6.0-openjdk-devel-1.6.0.0-1.25.1.10.6.el5_8
fs
Hey,
I'm trying to build JCC on Python 2.4.3 (CentOS 5). However during the
compilation I get this error:
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC
-D_
Petrus,
> g++: build\temp.win32-2.6\Release\jcc\sources\libjcc.a: No such file or
> director
> y
If you could find a mail tool which doesn't wrap the lines of the log
you're trying to send, that would help to debug this. But it looks to
me as if something is not creating that directory before tr
Hi Petrus,
On Jul 4, 2011, at 23:15, Petrus Hyvönen wrote:
> This is likely another faq but,
>
> I've moved to a windows 7 machine (64bit) and trying to compile jcc. mingw32
> compiler, JDK, JRE installed. I'm getting a libjcc.a - No such file or
> directory error. javac is available at the co
Hi,
This is likely another faq but,
I've moved to a windows 7 machine (64bit) and trying to compile jcc. mingw32
compiler, JDK, JRE installed. I'm getting a libjcc.a - No such file or
directory error. javac is available at the command prompt.
Building with:
python setup.py build --compiler=ming
p://www.orbiteam.de
> -Original Message-
> From: Baseer Khan [mailto:bas...@yahoo.com]
> Sent: Thursday, May 19, 2011 6:26 AM
> To: pylucene-dev@lucene.apache.org
> Subject: Need help building JCC on windows
>
> I don't seem to resolve the undefined reference issue wh
I don't seem to resolve the undefined reference issue while building JCC on
windows 7 using Mingw32 compiler.
Any help?
C:\glassfish3\jdk
running install
running bdist_egg
running egg_info
writing JCC.egg-info\PKG-INFO
writing top-level names to JCC.egg-info\top_level.txt
wr
Andi Vajda wrote:
>
> On Tue, 23 Mar 2010, Bill Janssen wrote:
>
> > Andi Vajda wrote:
> >
> >>> That's why I made it a JCC option, which could be enabled/disabled
> >>> via the config.py file. (That is, you could build it shared with or
> >>> without auto-find, but if you decided you wanted
On Tue, 23 Mar 2010, Bill Janssen wrote:
Just to catch the error, perhaps a hash of the config properties of the
JCC used to compile the PyLucene extension could be baked into both, and
compared at module load time?
Hmm, that's an idea. I'm not sure how lenient/strict this check needs to be,
Andi Vajda wrote:
>
>
> On Tue, 23 Mar 2010, Bill Janssen wrote:
>
> > Andi Vajda wrote:
> >
> >>> The way extensions are distributed on Windows makes it even worse.
> >>> Building an extension with --wininst (or any other way) does not package
> >>> it with the JCC it was compiled with. And
On Tue, 23 Mar 2010, Bill Janssen wrote:
Andi Vajda wrote:
That's why I made it a JCC option, which could be enabled/disabled
via the config.py file. (That is, you could build it shared with or
without auto-find, but if you decided you wanted it the other way,
you could simply edit config.p
Andi Vajda wrote:
>
> On Tue, 23 Mar 2010, Bill Janssen wrote:
>
> > Andi Vajda wrote:
> >
> >>
> >> On Tue, 23 Mar 2010, Bill Janssen wrote:
> >>
> >>> Andi Vajda wrote:
> >>>
> - the --find-jvm-dll trick is in jcc/windows.py and is not a JCC build
> option but a JCC run opti
Andi Vajda wrote:
>
> On Tue, 23 Mar 2010, Bill Janssen wrote:
>
> > Bill Janssen wrote:
> >
> >> Andi Vajda wrote:
> >>
> >>> - the --find-jvm-dll trick is in jcc/windows.py and is not a JCC build
> >>> option but a JCC run option. In other words, if you want the feature
> >>> for
Andi Vajda wrote:
> > That's why I made it a JCC option, which could be enabled/disabled
> > via the config.py file. (That is, you could build it shared with or
> > without auto-find, but if you decided you wanted it the other way,
> > you could simply edit config.py to change it.)
>
> If you b
On Tue, 23 Mar 2010, Bill Janssen wrote:
Andi Vajda wrote:
The way extensions are distributed on Windows makes it even worse.
Building an extension with --wininst (or any other way) does not package
it with the JCC it was compiled with. And nothing in the package name
tells you whether it
Andi Vajda wrote:
> > The way extensions are distributed on Windows makes it even worse.
> > Building an extension with --wininst (or any other way) does not package
> > it with the JCC it was compiled with. And nothing in the package name
> > tells you whether it was shared or non-shared.
>
>
On Tue, 23 Mar 2010, Bill Janssen wrote:
Andi Vajda wrote:
On Tue, 23 Mar 2010, Bill Janssen wrote:
Andi Vajda wrote:
- the --find-jvm-dll trick is in jcc/windows.py and is not a JCC build
option but a JCC run option. In other words, if you want the feature
for your extension
On Tue, 23 Mar 2010, Bill Janssen wrote:
Bill Janssen wrote:
Andi Vajda wrote:
- the --find-jvm-dll trick is in jcc/windows.py and is not a JCC build
option but a JCC run option. In other words, if you want the feature
for your extension, when it starts, invoke jcc with, among m
On Tue, 23 Mar 2010, Bill Janssen wrote:
Andi Vajda wrote:
- the --find-jvm-dll trick is in jcc/windows.py and is not a JCC build
option but a JCC run option. In other words, if you want the feature
for your extension, when it starts, invoke jcc with, among many other
things, -
Andi Vajda wrote:
>
> On Tue, 23 Mar 2010, Bill Janssen wrote:
>
> > Andi Vajda wrote:
> >
> >> - the --find-jvm-dll trick is in jcc/windows.py and is not a JCC build
> >> option but a JCC run option. In other words, if you want the feature
> >> for your extension, when it starts, in
On Tue, 23 Mar 2010, Bill Janssen wrote:
Andi Vajda wrote:
- the --find-jvm-dll trick is in jcc/windows.py and is not a JCC build
option but a JCC run option. In other words, if you want the feature
for your extension, when it starts, invoke jcc with, among many other
things, -
Bill Janssen wrote:
> Andi Vajda wrote:
>
> > - the --find-jvm-dll trick is in jcc/windows.py and is not a JCC build
> > option but a JCC run option. In other words, if you want the feature
> > for your extension, when it starts, invoke jcc with, among many other
> > things, --fin
Andi Vajda wrote:
>
> On Mar 23, 2010, at 9:29, Bill Janssen wrote:
>
> > Well, it doesn't work out-of-the-box. I'll see if I can figure out
> > what's going on.
>
> Can you be more specific ? 'it' ?
A fresh checkout of the svn sources.
Bill
Andi Vajda wrote:
> I did not test the mingw32 compiler stuff as I don't have it.
> Please check it out and let me know how it works for you.
Once I fixed jcc/helpers/mingw32.py, I find we're back to the same old
breakage:
/c/Python26/python.exe -m jcc.__main__ --shared --compiler mingw32 --jar
Andi Vajda wrote:
> - the --find-jvm-dll trick is in jcc/windows.py and is not a JCC build
> option but a JCC run option. In other words, if you want the feature
> for your extension, when it starts, invoke jcc with, among many other
> things, --find-jvm-dll when you build your exte
Andi Vajda wrote:
> - the --find-jvm-dll trick is in jcc/windows.py and is not a JCC build
> option but a JCC run option. In other words, if you want the feature
> for your extension, when it starts, invoke jcc with, among many other
> things, --find-jvm-dll when you build your exte
On Mar 23, 2010, at 9:29, Bill Janssen wrote:
Well, it doesn't work out-of-the-box. I'll see if I can figure out
what's going on.
Can you be more specific ? 'it' ?
Andi..
Bill
On Sat, 20 Mar 2010, Bill Janssen wrote:
Here's my latest patch against the SVN trunk. It allows you to say
"--auto-find-jvm-dll" when building JCC:
python setup.py build --auto-find-jvm-dll install
and puts that setting in the jcc/config.py file. Later, if it'
Andi Vajda wrote:
> I was thinking of putting it into a tree sibling to jcc, called
> helpers, where all this build stuff could move to - including a mini
> fork of setuptools for patch.43 if it really had to come to this.
>
> So helpers.windows has your stuff, helpers.setuptools, the patched
>
On Mar 20, 2010, at 15:54, Bill Janssen wrote:
Here's my latest patch against the SVN trunk. It allows you to say
"--auto-find-jvm-dll" when building JCC:
python setup.py build --auto-find-jvm-dll install
and puts that setting in the jcc/config.py file. Later, if it'
Here's my latest patch against the SVN trunk. It allows you to say
"--auto-find-jvm-dll" when building JCC:
python setup.py build --auto-find-jvm-dll install
and puts that setting in the jcc/config.py file. Later, if it's set,
when "jcc" is imported, it lo
On Mar 20, 2010, at 14:49, Bill Janssen wrote:
Andi Vajda wrote:
Ah ok, I missed that. The import of config.py can be surrounded by
try/
catch since SHARED is not needed during jcc build time. I'll add that
and simulate the execution path to find other such holes.
Here's one I don't see a
Bill Janssen wrote:
> Andi Vajda wrote:
>
> > Ah ok, I missed that. The import of config.py can be surrounded by
> > try/
> > catch since SHARED is not needed during jcc build time. I'll add that
> > and simulate the execution path to find other such holes.
>
> Here's one I don't see a good wo
Andi Vajda wrote:
> Ah ok, I missed that. The import of config.py can be surrounded by
> try/
> catch since SHARED is not needed during jcc build time. I'll add that
> and simulate the execution path to find other such holes.
Here's one I don't see a good workaround for:
if __name__ == '__main_
Andi, I'll send in a new patch for you to look at. It patches setup.py,
jcc/__init__.py, and jcc/windows.py. I've tried to honor all your
constraints.
Bill
Andi Vajda wrote:
>
> On Mar 19, 2010, at 19:57, Bill Janssen wrote:
>
> > Andi Vajda wrote:
> >
> >>> Andi Vajda wrote:
> >>>
> >>>
On Mar 19, 2010, at 19:57, Bill Janssen wrote:
Andi Vajda wrote:
Andi Vajda wrote:
I integrated your changes in trunk rev 925041.
I took a look at this, and I don't think it will work. You can't
import
jcc.windows before writing jcc.config, for one thing. I'll put it
back
in set
Andi Vajda wrote:
> > Andi Vajda wrote:
> >
> >> I integrated your changes in trunk rev 925041.
> >
> > I took a look at this, and I don't think it will work. You can't import
> > jcc.windows before writing jcc.config, for one thing. I'll put it back
> > in setup.py again?
>
> This is importe
On Fri, 19 Mar 2010, Bill Janssen wrote:
Andi Vajda wrote:
I integrated your changes in trunk rev 925041.
I took a look at this, and I don't think it will work. You can't import
jcc.windows before writing jcc.config, for one thing. I'll put it back
in setup.py again?
This is imported d
Andi Vajda wrote:
> I integrated your changes in trunk rev 925041.
I took a look at this, and I don't think it will work. You can't import
jcc.windows before writing jcc.config, for one thing. I'll put it back
in setup.py again?
> It would be easier to do this if you sent a patch, so I hope I
On Thu, 18 Mar 2010, Bill Janssen wrote:
Andi, attached please find a copy of jcc/setup.py with the following
modifications:
1. On Windows, look in the registry to find out where the Java JDK
is installed, instead of hard-coding a probably-bogus path.
2. Added a branch for "mingw32", whi
One other gotcha I should note. We knew this before, but it's good
to have it recorded somewhere. When building with mingw32, you need to
specify the compiler:
$ python setup.py build --compiler=mingw32
But then when you go to make a binary:
$ python setup.py bdist --formats=wininst
you w
Andi, attached please find a copy of jcc/setup.py with the following
modifications:
1. On Windows, look in the registry to find out where the Java JDK
is installed, instead of hard-coding a probably-bogus path.
2. Added a branch for "mingw32", which is triggered if
"--compiler=mingw32"
On Thu, 4 Jun 2009, edwin.mad...@verizonwireless.com wrote:
getting jvm_NULL_THUNK_DATA not found error in the last step of building JCC on
Cygwin/windows with "python setup.py build" after switching to gcc version
4.3.2 20080827 (beta) 2 (GCC) with Advise from Andi V, and C
getting jvm_NULL_THUNK_DATA not found error in the last step of building JCC on
Cygwin/windows with "python setup.py build" after switching to gcc version
4.3.2 20080827 (beta) 2 (GCC) with Advise from Andi V, and Christian H. gcc4x
is available from Cygwin, but not as default -do no
edwin.mad...@verizonwireless.com schrieb:
> For PyLucene, has anyone succeeded in building JCC with gcc version 3.4.4 on
> Cygwin windows?
>
> "python setup.py build" is throwing errors while compiling JArray.cpp that
> comes with PyLucene-2.4.0-2
> ..
On Wed, 3 Jun 2009, edwin.mad...@verizonwireless.com wrote:
For PyLucene, has anyone succeeded in building JCC with gcc version 3.4.4 on
Cygwin windows?
"python setup.py build" is throwing errors while compiling JArray.cpp that
comes with PyLucene-2.4.0-2
..
jcc/sources/JArr
For PyLucene, has anyone succeeded in building JCC with gcc version 3.4.4 on
Cygwin windows?
"python setup.py build" is throwing errors while compiling JArray.cpp that
comes with PyLucene-2.4.0-2
..
jcc/sources/JArray.cpp: In instantiation of `_t_jarray':
jcc/sources/
62 matches
Mail list logo
