Re: [PyCUDA] undefined symbol error

[Andreas Kloeckner]

Chris  writes:

> Hey Andreas,
> I am having a similar issue that Kambiz Tavabi was having. Here is the error
> (I have pycuda on anaconda2 just like Kambiz)
>
>  File "main_class.py", line 17, in 
> import pycuda.gl as cuda_gl
>  File
> "/home/uchytilc/anaconda2/lib/python2.7/site-packages/pycuda-2016.1.2-py2.7-linux-x86_64.egg/pycuda/gl/__init__.py",
> line 2, in 
> import pycuda._driver as _drv
> ImportError:
> /home/uchytilc/anaconda2/lib/python2.7/site-packages/pycuda-2016.1.2-py2.7-linux-x86_64.egg/pycuda/_driver.so:
> undefined symbol: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEED1Ev
>
> The weird thing is that I have some files that are having this problem and
> some that are not, with identical import statements.
>
> import sys
>
> from OpenGL.GL import *
> from OpenGL.GLUT import *
> from OpenGL.GLU import *
> from OpenGL.GL.ARB.vertex_buffer_object import *
> from OpenGL.GL.ARB.pixel_buffer_object import *
>
> import pycuda.gl as cuda_gl
> import pycuda.driver as cuda_driver
>
> The files that are experiencing this issue are all files that run this
> import statement right at the top in the main.py file, the one I initialize
> from. The one that doesn't hit this error has the import statements in a
> second file that is being imported with an __init__.py file. Not sure if
> this is pure coincidence or not but I figured it was worth bringing up.

Sorry for the delay in responding. GCC 5.1 switched its C++ ABI with version
5. I suspect some of the binary packages you have installed are using
the old ABI (Anaconda is built on CentOS 6 I believe and would be using
the old ABI), while C++ software you built on your machine (PyCUDA) will
use the new ABI. See here for more info:

https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html

Try adding (in PyCUDA's siteconf.py)

-D_GLIBCXX_USE_CXX11_ABI=0

to CXXFLAGS.

Hope that helps,
Andreas

___
PyCUDA mailing list
PyCUDA@tiker.net
https://lists.tiker.net/listinfo/pycuda

Re: [PyCUDA] pipwin error with runpy.py

[Andreas Kloeckner]

"Slein, Ryan"  writes:
> I've spent a few days digging through forums without any luck so I figured 
> I'd post to the mailing list as per request of the forums. Any advice would 
> be greatly appreciated. I am new to python and cuda, and entirely 
> self-taught, so sorry in advanced for any gaps of knowledge on my part.
>
> I am trying to install pycuda but am getting hung up on one of the last 
> install steps, pipwin install pycuda. I keep getting an error in runpy.py 
> when trying to install the software through anaconda. BeautifulSoup tells me 
> it is an lxml file error (see attached cmd) in anaconda\lib\runpy.py for both 
> Python/Anaconda 2 and Python/Anaconda 3 (see attached code: Line 184 for 
> anaconda3 and Line 174 for anaconda2). I've tried to do what BeautifulSoup 
> stated but haven't succeeded, hopefully the solution is obvious to someone 
> with much more experience than myself.
>
> I've also tried building from means other than conda with no luck. I
> am open to try other build packages if you don't know of any conda
> work arounds. Some computer specs: Windows 10 Pro V1607 OS Build
> 14393.693 & Command Prompt Version 10.0.14393. Please let me know if
> you need any further information of my system.

The message you show appears to be a non-fatal warning and unrelated to
PyCUDA, which does not use BeatifulSoup. If you show a relevant error
message (bonus points for text format), we may be in a better position
to help.

Andreas

___
PyCUDA mailing list
PyCUDA@tiker.net
https://lists.tiker.net/listinfo/pycuda