Dear Tiago,

Thanks for the tip.
Please see the attached log file. As far as I know, there were no flags added, but perhaps the epd setup script  (setup.csh) was first initialized.
The EPD python is the python interpreter I would like to use.

Best,
Eli

On Sun, Feb 5, 2017 at 6:09 PM, Tiago Peixoto [via Main discussion list for the graph-tool project] <[hidden email]> wrote:
On 05.02.2017 14:08, bloodymeli wrote:
> Thanks!
>
> This is indeed strange, as the library is installed to
> /usr/local/epd/lib/python2.7/site-packages/graph_tool/libgraph_tool_core.so
>
> but compiled against:
> libpython2.6.so.1.0 => /usr/lib64/libpython2.6.so.1.0 (0x00007ffff38ce000)
>
> How do I specify which libpython to use?


This should be detected automatically when ./configure is run. The specific
python interpreter can be overridden by setting the PYTHON environment
variable to ./configure.

But your symptom can also be caused by your custom python library (which
seems to be installed in the nonstandard path /usr/local/epd) not being set
in the linker's path. This could be fixed by doing something like: export
LD_LIBRARY_PATH=/usr/local/epd/lib/

But these are just some guesses, since you gave us very little information.
Ideally, you would give us all parameters you passed to ./configure during
compilation, as well as the contents to config.log.

Best,
Tiago

--
Tiago de Paula Peixoto <[hidden email]>


_______________________________________________
graph-tool mailing list
[hidden email]
https://lists.skewed.de/mailman/listinfo/graph-tool

signature.asc (849 bytes) Download Attachment
--
Tiago de Paula Peixoto <[hidden email]>



To unsubscribe from general "did not match C++ signature" error, click here.
NAML


setup.csh (302 bytes) Download Attachment
config.log (144K) Download Attachment


View this message in context: Re: general "did not match C++ signature" error
Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com.