I attempted to install pycuda by removing setuptools and install distribute. The install seemed to work, but unfortunately it segfaults when I run pycuda's test_driver.py. If I use my native python that has pycuda installed, the same test_driver.py works flawlessly.
Again what is it with the sage sandboxed python that thwarts my attempts to install many of these packages? On Feb 20, 8:52 pm, SevenThunders <[email protected]> wrote: > I posted this on the development list, but maybe I should have posted > here: > > I have an archlinux x86-64 desktop and I successfully installed > (compiled) sage. I'd like to add some additional functionality > however, but I've been stymied by a number of issues. First my top > issue is to get pycuda working with sage, which apparently others > have done. Unfortunately sage has an installation of setuptools which > doesn't work with pycuda, and is supposed to be somewhat deprecated as > of python 2.6.4. > > -------------- > I get an error of this type: > Does your error message look like this? > > "/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9- > py2.6.egg/setuptools/command/build_ext.py", > line 85, in get_ext_filename > KeyError: '_something' > > You are using Python 2.6.3 with Setuptools. This will not work. > Uninstall setuptools, install > distribute.http://wiki.tiker.net/DistributeVsSetuptools#switching > --------------- > > Two other python libraries I could not install are PyQt4 and pygtk. > The latter runs up against an error: > -------------- > /usr/bin/ld: /opt/sage/sage/local/lib/../lib/ > libpython2.6.a(abstract.o): relocation R_X86_64_32 against > `.rodata.str1.8' can not be used when making a shared object; > recompile with -fPIC > /opt/sage/sage/local/lib/../lib/libpython2.6.a: could not read > symbols: Bad value > -------------- > > This prevents some other libraries from installing. > > I'm not sure why the sage python distribution is so persnickety. What > I'd like to know is how hard would it be to compile sage and configure > it to use Arch Linux's system python, rather than the sandboxed > python that comes with sage. This would make it much easier to > reliably use other python packages, though of course it doesn't > guarantee that sage would see a proven and tested environment, though > isn't version control and package dependencies supposed to mitigate > this issue? -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
