Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

run-time link issue in IPython Notebook

I'm trying to run QuantLib + cython wrappers (pyql) in a IPython notebook. From the console, I can:

  • build QuantLib and run the test suite
  • build pyql and run the test suite (path to QuantLib.so set with -rpath arguments in g++)
  • use ldd to verify that the run-time links are resolved
  • invoke ipython (from the console) and run tests, works fine. The key point being run-time link to the QuantLib.so library.

Now I open an IPython notebook, cd to the proper directory, try to import a module, get an import error (libQuantLib.so.0 not found). Same problem if a use a notebook without sage enhancements.

Is the ipython interpreter used in a notebook somehow different from the one invoked in a console? More generally, what is the canonical way to register a dynamic library for use in a notebook, given that "ldconfig -n <path>" is not an option?

run-time link issue in IPython Notebook

I'm trying to run QuantLib + cython wrappers (pyql) in a IPython notebook. From the console, I can:

  • build QuantLib and run the test suite
  • build pyql and run the test suite (path to QuantLib.so set with -rpath arguments in g++)
  • use ldd to verify that the run-time links are resolved
  • invoke ipython (from the console) and run tests, works fine. The key point being run-time link to the QuantLib.so library.

Now I open an IPython notebook, cd to the proper directory, try to import a module, get an import error (libQuantLib.so.0 not found). Same problem if a I use a notebook without sage enhancements.

Is the ipython interpreter used in a notebook somehow different from the one invoked in a console? More generally, what is the canonical way to register a dynamic library for use in a notebook, given that "ldconfig -n <path>" is not an option?

[Solved] run-time link issue in IPython Notebook

I'm trying to run QuantLib + cython wrappers (pyql) in a IPython notebook. From the console, I can:

  • build QuantLib and run the test suite
  • build pyql and run the test suite (path to QuantLib.so set with -rpath arguments in g++)
  • use ldd to verify that the run-time links are resolved
  • invoke ipython (from the console) and run tests, works fine. The key point being run-time link to the QuantLib.so library.

Now I open an IPython notebook, cd to the proper directory, try to import a module, get an import error (libQuantLib.so.0 not found). Same problem if I use a notebook without sage enhancements.

Is the ipython interpreter used in a notebook somehow different from the one invoked in a console? More generally, what is the canonical way to register a dynamic library for use in a notebook, given that "ldconfig -n <path>" is not an option?