[PyCUDA] Build Problems on SuSE 11.0, now Pytools not found
wrosner at tirnet.de
Sat Nov 21 14:02:06 PST 2009
Am Samstag, 21. November 2009 20:00:10 schrieb pycuda-request at tiker.net:
> Message: 3
> Date: Sat, 21 Nov 2009 13:39:13 -0500
> From: Andreas Kl?ckner <lists at informa.tiker.net>
> Subject: Re: [PyCUDA] Build Problems on SuSE 11.0, x86_64 - cannot
> find -llibboost_python-mt
> To: pycuda at tiker.net
> Message-ID: <200911211339.19819.lists at informa.tiker.net>
> Content-Type: text/plain; charset="iso-8859-1"
> On Samstag 21 November 2009, Wolfgang Rosner wrote:
> > OK, for me it works now, but peomple might be even more (and earlier)
> > happy if the pytools issue had been mentioned in the setup wiki.
> Pytools should be installed automatically along with 'python setup.py
> install'. If it didn't: do you have any idea why?
could it be that I ran "make install"
instead of "python setup.py install" ?
(sorry, I'm just getting used to Python, preferred perl in earlier live)
first I thought it was due to the different python path structures.
standard on SuSE is
but the egg-laying machine seems to put stuff to
(maybe I could have reconfigured this, anyway)
but I don't know why, altough
live outside obvious scope, the pycuda demos
But for gl_interop.py
I got "No module named vertex_buffer_object"
is new in python-opengl ~ Version 3.
There are only rpms for Version 2.0.something for SuSE 11.0
I got new source from http://pyopengl.sourceforge.net
build and install, obviously to
However, gl_interop.py did not run until I did
(was PYTHONPATH="" before)
maybe this is since there is still the old python-opengl-2.0.1.09-224.1
in the way which is caught before.
But to figure it out I'm definitely lacking sufficient python experience.
> > If you like and give me an wiki account, I'd go to share my experience.
> No account required. (though you can create one yourself) Please do share.
hm, might give it a try.
I think best I could offer was be to prepare an own SuSE page with my
It all comes down to different ways and places where stuff is stored.
But I think my approach is not the best one, in the view back it were better
to configure new stuff so that it meets SuSE structure. Maybe.
Well, but this might break other dependencies?
Smells like big 'Baustelle'...
So if your expectation of quality on your wiki is not too high, I'll post my
More information about the PyCUDA