Skip to content
This repository has been archived by the owner on Dec 30, 2023. It is now read-only.

Import error: undefined symbol #101

Open
gravelandblood opened this issue Oct 30, 2016 · 4 comments
Open

Import error: undefined symbol #101

gravelandblood opened this issue Oct 30, 2016 · 4 comments

Comments

@gravelandblood
Copy link

I have installed the python wrapper successfully.
But an error occurs when I import it:

>>> import pcl
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/dist-packages/pcl/__init__.py", line 2, in <module>
    from ._pcl import *
ImportError: /usr/local/lib/python2.7/dist-packages/pcl/_pcl.so: undefined symbol: _ZN3pcl7PCLBaseINS_8PointXYZEE13setInputCloudERKN5boost10shared_ptrIKNS_10PointCloudIS1_EEEE

Best Wishes!

@SinghGauravKumar
Copy link

Any solution of this?

@SkanderHannachi
Copy link

SkanderHannachi commented Apr 20, 2017

same here

EDIT : it's numpy related. look here : #79

@mikeroberts3000
Copy link

mikeroberts3000 commented Aug 31, 2017

@SkanderHannachi these two errors don't appear to me to be directly related. One is regarding an undefined symbol that seems to originate from python-pcl code:

_ZN3pcl7PCLBaseINS_8PointXYZEE13setInputCloudERKN5boost10shared_ptrIKNS_10PointCloudIS1_EEEE

In contrast, #79 is regarding an undefined symbol that seems to originate from some lower-level CPython code:

PyFPE_counter

Can you provide more detail regarding how these two issues are related?

@mikeroberts3000
Copy link

mikeroberts3000 commented Sep 1, 2017

I ended up finding an astonishing workaround for this issue.

When I run python setup.py install, the setup script prints out a few gcc and g++ commands. If you can believe it, the workaround for this problem was to take each gcc and g++ command, copy it to the command line, and run it manually. And then to run python setup.py install again. Running the setup script again will not call gcc or g++, but will copy the relevant files to the Python site-packages folder.

So, the build environment is somehow different when invoking gcc and g++ from setup.py, as opposed to invoking gcc and g++ manually from the command line.

There are several open issues where other people have similar errors (#63, #101, #119), so I don't think this issue is due to a local build configuration problem on my machine.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants