Cadabra Q&A - Recent questions and answers in Installation trouble

Answered: Cadabra on Windows 10 (2026) - integrate into Jupyter Notebook

Fri, 03 Apr 2026 13:05:06 +0000

In general you're better off using the "new" Jupyter kernel for Cadabra which is built by default. On Linux, this is a lot easier than using the old Xeus-based kernel in a conda setup. I will soon remove that support from the source tree altogether, as conda is more and more problematic and there is nobody maintaining those packages anymore.

On Windows, you really are much much better off by running the jupyter notebook server inside WSL, so you can rely on the Linux packages. Then connect to that via a browser on the Windows side.

Answered: No GUI after compiling from the source (manjaro)

Thu, 02 Jan 2025 15:11:47 +0000

That sounds you either have some old version of cadabra-server floating around, or there is a mixture of different python versions on your system which are not picked up consistently. Can you email me the output of the cmake stage (with a clean build folder)?

The theme warning errors probably have something to do with customisations you (or some manjaro package) has made to the gtk theme.

Answered: compile failed using boost 1.87

Tue, 24 Dec 2024 11:18:24 +0000

2.5.10 is now available via homebrew; please try and let me know if there are any more issues.

Answered: Another "No module named 'sympy' " question.

Sun, 29 Sep 2024 20:58:15 +0000

I have just released 2.5.6, which fixes this issue, and also includes plotting support in the AppImage version. You can find the updated AppImage in the github release assets for this release.

Setting Python version in cmake

Thu, 18 Apr 2024 13:39:33 +0000

I'm the cadabra2 port maintainer for MacPorts. The update to version 2.4.5.6 has caused an issue: Rather than picking up the MacPorts version of Python (it was set to 3.11 for the previous release, but should be updated to version 3.12, as that's now default), the cmake script picks up the macOS version instead (on my Ventura system, that would be 3.9.6). I can properly set -DPYTHON_LIBRARIES and -DPYTHON_SITE_PATH, but I don't see a way of choosing the path to the python binary.

Answered: Question about Installation of Cadabra on Ubuntu&Conda

Fri, 22 Mar 2024 14:41:23 +0000

First of all, I would strongly advise you not to run anything like this as root user, that's just asking for trouble. It's not the cause of the problem you are having, but still important advice.

The Conda package maintainer has unfortunately abandoned it, and therefore there has not been any update for a long time. You are far better off just installing an Ubuntu package for Cadabra for Ubuntu from the download page; those are provided by me and maintained. And it is also what is written on https://cadabra.science/jupyter.html . I would remove the Conda packages first before you try this though.

Let me know if this gets you any further.

Answered: NameError after upgrade

Tue, 05 Mar 2024 18:15:32 +0000

This depends a lot on how you installed Cadabra before. Did it come from the Cadabra package in the Ubuntu repositories? Or from an earlier install from source? If you installed from a previous package, you should do

sudo apt remove cadabra2

to remove it (and then re-install from source).

If you installed from source, you will need to do some more work. Typically, when you install from source, and do not pass any installation directory parameters, things go into

/usr/local/lib/python3.x/dist-packages/

(replace python3.x with the appropriate Python version). For me this contains (among non-cadabra things),

cadabra2.cpython-310-aarch64-linux-gnu.so
cadabra2_defaults.py
cdb_appdirs.py
cadabra2_jupyter/
cdb/
notebook/

(names will differ on a different architecture). Erase all these (both the files and the directories). Then there is also a bunch of cadabra* binaries in

/usr/local/bin/

Finally, there is a directory

/usr/local/share/cadabra2/

If you erase all this and re-install from source, hopefully things go better.

Output not displaying as rendered latex

Thu, 15 Feb 2024 18:26:19 +0000

I am not sure when this started as far as what was upgraded. In Jupyterlab all output is showing as latex statements inside $$s and not rendering.

If I copy the output and paste it into a markdown cell it renders correctly.

I.E. {\mu,\nu,\rho}::Indices(position=free). x::Coordinate. \partial{#}::Derivative.

F{\mu\nu}::AntiSymmetric; F{\mu\nu}::Depends(x). A_{\mu}::Depends(x,\partial{#}). \delta{#}::Accent;

Output: ${}\text{Property Accent attached to}\delta{#}.$

Input: S:= -1/4 \int{ F_{\mu\nu} F^{\mu\nu} }{x};

Output: ${} - \frac{1}{4}\int F^{\mu \nu} F_{\mu \nu}\,\,{\rm d}x$

If I view the file in Jupyter notebook the code renders correctly.

?? Thanks, ChuckW

When I posted this the 2nd example output rendered correctly in the post but not in Jupyterlab?

Windows 11 source install

Tue, 06 Jun 2023 13:36:55 +0000

I've been following the instructions in the git release's readme.rst and setting up to build cababra on windows, but I ran into an issue at the step:


    cmake -DCMAKE_TOOLCHAIN_FILE=C:/Users/chris/vcpkg/scripts/buildsystems/vcpkg.cmake
          -DCMAKE_BUILD_TYPE=RelWithDebInfo 
          -DVCPKG_TARGET_TRIPLET=x64-windows 
          -DCMAKE_INSTALL_PREFIX=C:\Cadabra
          -G "Visual Studio 17 2022" -A x64 ..

It runs fine until I get the error:

-------------------------------------------
  Configuring packages
-------------------------------------------
-- Storing algorithm C++ module as core
-- Storing algorithm C++ module as utils
CMake Error at cmake/functions.cmake:11 (install):
  Syntax error in cmake code at

    C:/Users/chris/cadabra2/cmake/functions.cmake:12

  when parsing string

    C:\Users\chris\anaconda3

  Invalid character escape '\U'.
Call Stack (most recent call first):
  core/CMakeLists.txt:428 (install_directory_permissions)


-- Configuring incomplete, errors occurred!

Not sure how to get around this, looking online suggests it is some forward slash and backslash confusion between windows and cmake when specifying directories.

Any help would be great!

Answered: Can not set the correct Cadabra kernel path for jupyter.

Thu, 05 Jan 2023 20:12:51 +0000

see link https://cadabra.science/faq.html#q_01_01

Answered: Missing directory when running Cadabra for the first time

Wed, 04 Jan 2023 21:31:50 +0000

The cadabra2 package in Debian/Ubuntu is currently broken, and this leads to the error you showed. Please install a package from the download page at https://cadabra.science/download.html instead for now.

Answered: Installing with apt-get on Linux Mint 21

Fri, 09 Dec 2022 07:04:04 +0000

You installed the old 1.x series. The package for the new series (since about 2016) is called cadabra2. You'll need a fairly recent Mint for that though. The alternative is to download a package from the downloads page at https://cadabra.science/download.html .

Answered: Problems installing with brew on MacOS

Mon, 28 Nov 2022 17:39:48 +0000

This turned out to be a compatibility issue with the recently released Python 3.11. I have updated Cadabra to 2.4.2.4 which contains a fix for this, and have also updated the Homebrew tap so that brew install cadabra2 uses this latest version. This now works on my mac, please let me know if there are any remaining issues.

Answered: Support for Apple Silicon(M1)

Sun, 21 Nov 2021 15:28:46 +0000

The current version 2.3.8 builds from source on Apple silicon.

I have also updated the homebrew tap so you can install that way too.

Answered: Configuring jupyterhub with cadabra2

Tue, 10 Aug 2021 21:49:22 +0000

OK... I think I solved the issue by updating the jupyterhub.service configuration. I had to locate the jupyterhub.service file. In my system it was in the folder /etc/systemd/system/

i.e.

sudo gedit /etc/systemd/system/jupyterhub.service

Underneath the existing "Environment=" line, I added another line

Environment=export PYTHONPATH=${PYTHONPATH}:/usr/local/lib/python3.9/site-packages

After saving the file, I had to re-load the configuration into the system with

sudo systemctl daemon-reload

finally - restart the service:

sudo systemctl restart jupyterhub.service

Now I can run cadabra2 commands in jupyterhub from any computer in my LAN (I configured a firewall rule to allow http traffic only from LAN IPs).

Problems in compiling Cadabra from source

Fri, 12 Feb 2021 21:27:10 +0000

When I was trying to build the Cadabra from the source, I did find certain errors during the build, and that I cannot open the application at all.

The building process I was following is exactly from here, and after I input the code cmake --build . --config RelWithDebInfo --target install , I found these errors:

C:\Dev\cadabra2\core\DisplayTerminal.cc(18,14): error C2001: newline in constant [C:\Dev\cadabra2\build\core\cadabra2.v cxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(19,14): error C2001: newline in constant [C:\Dev\cadabra2\build\core\cadabra2.v cxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(18,14): error C2064: term does not evaluate to a function taking 1 arguments [C :\Dev\cadabra2\build\core\cadabra2.vcxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(20,4): error C2059: syntax error: ';' [C:\Dev\cadabra2\build\core\cadabra2.vcxp roj] C:\Dev\cadabra2\core\DisplayTerminal.cc(662,2): error C2059: syntax error: 'if' [C:\Dev\cadabra2\build\core\cadabra2.vc xproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(663,20): error C2065: 'it': undeclared identifier [C:\Dev\cadabra2\build\core\c adabra2.vcxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(664,2): error C2059: syntax error: 'if' [C:\Dev\cadabra2\build\core\cadabra2.vc xproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(664,53): error C2143: syntax error: missing ';' before '{' [C:\Dev\cadabra2\bui ld\core\cadabra2.vcxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(664,53): error C2447: '{': missing function header (old-style formal list?) [C: \Dev\cadabra2\build\core\cadabra2.vcxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(672,6): error C2143: syntax error: missing ';' before '<<' [C:\Dev\cadabra2\bui ld\core\cadabra2.vcxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(672,6): error C4430: missing type specifier - int assumed. Note: C++ does not s upport default-int [C:\Dev\cadabra2\build\core\cadabra2.vcxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(674,2): error C2059: syntax error: 'if' [C:\Dev\cadabra2\build\core\cadabra2.vc xproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(676,22): error C2065: 'it': undeclared identifier [C:\Dev\cadabra2\build\core\c adabra2.vcxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(676,24): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int [C:\Dev\cadabra2\build\core\cadabra2.vcxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(676,25): error C2440: 'initializing': cannot convert from 'initializer list' to 'int' [C:\Dev\cadabra2\build\core\cadabra2.vcxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(676,16): message : The initializer contains too many elements [C:\Dev\cadabra2\ build\core\cadabra2.vcxproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(679,2): error C2059: syntax error: 'if' [C:\Dev\cadabra2\build\core\cadabra2.vc xproj] C:\Dev\cadabra2\core\DisplayTerminal.cc(681,2): error C2059: syntax error: '}' [C:\Dev\cadabra2\build\core\cadabra2.vcx proj] C:\Dev\cadabra2\core\DisplayTerminal.cc(681,2): error C2143: syntax error: missing ';' before '}' [C:\Dev\cadabra2\buil d\core\cadabra2.vcxproj]

And after the installation is complete, I tried to run ctest, which gives that all 47 tests were failed. Therefore, I would like to know what was going on during the compilation.

The OS I am using is Windows 10, with Anaconda 2020.07(Conda 4.9.2), Texlive 6.3.2, and Visual Studio 16.8.5 installed. The exact process conducted was:

Doing git clone from the provided link
Executing C:\Dev\cadabra2\build>cmake -DCMAKE_TOOLCHAIN_FILE=C:/Dev/vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo -DVCPKG_TARGET_TRIPLET=x64-windows -DCMAKE_INSTALL_PREFIX=C:\Cadabra -G "Visual Studio 16 2019" -A x64 ..
Executing cmake command shown in the link from very above, giving error on DisplayTerminal.cc mentioned before.

Answered: Cadabra2 kernel for jupyter

Tue, 09 Feb 2021 18:34:06 +0000

It can't find the cadabra kernel module, set your PYTHON_PATH so it picks it up.

Answered: Installation error v2.3.6.5 on Ubuntu 18.04

Sun, 24 Jan 2021 15:45:20 +0000

Configure with

 cmake -DENABLE_MATHEMATICA=OFF ..

For some reason the script which tries to locate Mathematica messes up other parts of the CMake procedure.

Answered: Windows 10 version still doesn't work

Tue, 08 Dec 2020 20:24:53 +0000

I have updated the Windows installer to Cadabra 2.3.5. All feedback is welcome; I would like to make the windows version part of the regular release process, but that requires that we have a sufficient number of machines on which it is tested.

Download from https://cadabra.science/packages/windows/ .

Answered: Windows 10 64-bit install not working yet

Tue, 08 Dec 2020 20:23:29 +0000

Download from https://cadabra.science/packages/windows/ .

Answered: Installation on Windows Subsystem for Linux (WSL)

Mon, 02 Nov 2020 17:00:21 +0000

I am a Windows user too. I suggest you to create an Ubuntu virtual machine using VM ware on top of which install Ubuntu 20.04 (lts). The last two versions of Cadabra2 for Ubuntu 20.04 should run without any problems.

Answered: Trouble encountered after updating to v2.3.2

Mon, 02 Nov 2020 09:50:00 +0000

What happens with cadabra2 (the command-line client)? On which system is this, and I assume you installed from source?

Answered: cadabra-client: connection failed

Sun, 01 Nov 2020 15:47:40 +0000

For anyone running into this problem: this is a network issue, by which the cadabra2-gtk process is unable to reach the cadabra-server. Try the following:

Start cadabra-server by hand from a separate terminal window. This spits out two lines; a number and a uuid identifier. That first number is the port to which the server has bound.
Try to connect to that port by hand using
```
  telnet localhost [port]
```
Then report here whether the connection is achieved or not.
If the connection failed, check whether /etc/hosts contains a line
```
  127.0.0.1    localhost
```

On WSL it is conceivable that the windows firewall prevents these connections from being created.

Answered: ModuleNotFoundError: no module named 'sympy'

Mon, 21 Sep 2020 20:16:10 +0000

Install the sympy module with anaconda (conda install sympy from the terminal).

Answered: gmpy2 module error

Sat, 29 Aug 2020 18:31:18 +0000

This often happens when you are using a different Python to do that pip command from the one you use to run Cadabra.

Try instead

/usr/local/bin/python3 -m pip install sympy gmpy2

and let me know if that's any better.

Problems with import cdb.core.manip as manip

Thu, 06 Aug 2020 23:09:51 +0000

I am running win 10, and I have installed anaconda, and the package gmpy2. The problemi is that when I try to do import cdb.core.manip as manip I get the error "dll load failed". What can I try to fix it?

Windows 10 installation not working / stuck on source installation

Sun, 02 Aug 2020 07:49:16 +0000

Hi there, I am attempting to install Cadabra with the source code, because neither of the Windows 10 installations are currently working (both lead to Cadabra crashing immediately upon opening).

I am following the instructions, and I am stuck on the following step:

cmake -G "Visual Studio 16 2019" -A x64 ..

I cannot figure out what those dots .. are supposed to be. If I skip this part, and just run:

cmake --build . --config RelWithDebInfo --target install

then run

ctest

all 46 of the tests fail. Any help with this part would be greatly appreciated!

Answered: Issue with brew link

Fri, 12 Jun 2020 16:33:11 +0000

You can try that suggestion, but if that also fails, try brew doctor before you do anything else. That usually comes up with useful suggestions on broken installations.

Answered: Problem with installation from github repository (Debian bullseye)

Tue, 19 May 2020 12:03:08 +0000

Can you please pull from github once more and try on Debian again? I have updated pybind11, which seems to have fixed the issue with attempting to link to the wrong python library. It builds here fine on a clean Debian bullseye installation.

Answered: No output - Running Cadabra 2 on WSL 2 [Ubuntu 18.04] using VS Code

Mon, 20 Apr 2020 00:24:49 +0000

"Have you tried whether running it using Jupyter's own notebook server works?"

No, I had not done so.

While WSL 2 is a fully functional Linux OS, not an emulator, it is command-line only - there is no GUI desktop and no browser. With a addition of an X-server on the Windows 10 side, such as VcXsrv, one can display matplotlib output, in a separate window, generated in VS Code running on WSL side.Which is more than sufficient for scientific computing using numpy/sympy/numba/etc.

[update in following comment]

Answered: Installing CADABRA2

Mon, 30 Mar 2020 11:59:00 +0000

You are building against python3.7 which you installed yourself, right? (since it fetches libpython3.7m.a from /usr/local/lib).

Moreover, you are lacking the shared libraries, since it tries to link to the .a, not the .so. That by itself won't work; you need to link against shared libraries in order to produce the Python cadabra2.so module.

Any chance you can just build against stock python3.6 which comes with Ubuntu 18.04? I just tried that on a clean 18.04 install and it works fine. If that's not an option for you, you'll need to figure out why your python 3.7 installation does not have the shared libraries.

Answered: Installation problem on macOSMojave

Mon, 24 Feb 2020 06:55:42 +0000

What happens if you try to run cadabra-server ? It should produce some output and then sit there until you kill it, but it probably produces an error instead.

Cadabra2-gtk command not found on mac os x

Thu, 23 Jan 2020 08:58:39 +0000

I installed cadabra according to instructions and it says command not found.

Answered: Windows 10 version doesn't work

Sun, 10 Nov 2019 11:18:22 +0000

Please give the new 2.2.7f installer for Windows a shot, availabe at

https://cadabra.science/packages/windows/

and let me know if that works any better.

Answered: Trouble when compiling from the github repository

Mon, 21 Oct 2019 09:20:57 +0000

Those are unrelated. The Gtk error is something the Gtk team left unresolved, but it is harmless.

For the 2nd issue, read the message: you need to run make deduplicate (possibly with sudo) to remove the manual pages installed in an old deprecated location, and then make install will work again.

Answered: Cadabra on Raspberry Pi 3

Mon, 02 Sep 2019 18:39:49 +0000

The Raspberry Pi 3 has CPU architecture 'armv7l', while all the packages I distribute are built for 'amd64'. While it is possible to do a cross-compile, I have never attempted that with Cadabra's build system. I may give it a quick shot by playing with CPACK's parameters, but I don't have time to do much more.

If you have experience cross-compiling, you may want to give that a shot yourself. Or perhaps someone else here has attempted this?

Answered: Build fails on Ubuntu 19.04, unspecified reference to boost::system::generic_category().

Tue, 20 Aug 2019 16:55:25 +0000

I have just pushed a change to github related to boost. Can you give that another shot and let me know?

Answered: Installing Cadabra on mint 18.3 does not work

Mon, 22 Jul 2019 15:35:54 +0000

A recent change uses some features of gtkmm-3.20 or higher.

I have pushed a fix which disables this change if your system is on a lower version of gtkmm. Can you pull again from github, try to build, and let me know the result?

Answered: Fedora 29 rpm cpack error

Mon, 14 Jan 2019 19:06:53 +0000

I have made a few changes to detect Fedora 29 and build the package appropriately (using normal cmake, not cmake3). The resulting package is now available from the download page.

Answered: Fedora 29 rpm is missing

Sat, 12 Jan 2019 12:53:23 +0000

I didn't yet get around to building it, will do so the next few days.

Answered: Homebrew install problem

Mon, 17 Dec 2018 20:26:02 +0000

There is now the option to install directly using homebrew. First install MacTeX, either directly from its website, or using homebrew,

brew tap caskroom/cask
brew cask install mactex

Then install cadabra using

brew tap kpeeters/repo
brew install cadabra2

These instructions are now also on the download page. Please let me know if you run into any trouble; this has not yet received a lot of testing!

Answered: Gtk interface doesn't work.

Tue, 10 Jul 2018 16:51:47 +0000

I have pushed changes to github which (at least on my mac) solve this problem. Let me know if they fix it for you too.

Answered: Unable to run Cadabra after upgrade to Ubuntu 17.10

Sat, 28 Apr 2018 19:13:16 +0000

Did you start from a clean 'build' directory?

The message above indicates that the cadabra2python binary was linked to a libstdc++ which is not the same as the one it picks up when you start it. It may be due to a problem with Cadabra's build process (building against anaconda on Linux does not receive a lot of testing), but it is more likely that you had some leftovers from a build before you upgraded to 17.10.

Answered: Cadabra2 on mint 18.3 is not running

Wed, 18 Apr 2018 11:45:56 +0000

Are you sure it is trying to start the cadabra2-gtk installed by the binary package? That one is linked to version 1.58 of the boost libraries, and should work (all Mint 18.x have version 1.58).

If you previously installed from source, you would have ended up with a cadabra2-gtk linked to version 1.54 (as that's what Mint 17.x uses). So you may need to erase all cadabra related things in /usr/local/bin and /usr/local/lib, i.e.

rm -f /usr/local/bin/cadabra*
rm -f /usr/local/lib/*cadabra*

Let me know if that helps.

Answered: Will be there an installation for Microsoft Windows?

Sun, 08 Apr 2018 12:13:42 +0000

Windows is now officially supported, and an installer is available from the download page.

Answered: Installation in Fedora

Sat, 17 Feb 2018 22:07:07 +0000

Thanks for reporting this. Fedora 27 does a few things a bit differently from earlier versions, which led to the Python module not initialising correctly.

I have just pushed a fix to github; can you try to git pull the latest source and then build again? Let me know if it indeed works as intended.

Answered: Trouble with launching Cadabra2 in Mac

Sun, 11 Feb 2018 23:50:08 +0000

There seems to be some problem with linking to Mathematica on your Mac. Try the cmake configuration stage with

cmake -DENABLE_MATHEMATICA=OFF ..

and try 'make' and 'sudo make install' again.

Problem in Fedora 27

Sat, 27 Jan 2018 09:45:30 +0000

Hello, I installed Cadabra in fedora 27 using the version given in https://cadabra.science/packages/fedora26/ . However when I click to start, the window disappears within milliseconds. Can anyone help me.

Thanks, Leo

Recently installed Cadabra on fedora 26 but it is not running, window disappears immidiately.

Mon, 30 Oct 2017 12:33:19 +0000

Hi; I installed Fedora version of Cadabra from Cadabra website cadabra2-2.1.4-fedora24.rpm. Installed using rpm. However when i click to run it from the installation directory it does not run. Window comes and then disappears within miliseconds. Can anyone help.

Regards,

Ashish Arya

Problem installing Cadabra on Mac OS X 10.10.5

Mon, 11 Sep 2017 17:07:08 +0000

Hi, I'm currently trying to install Cadabra on Mac OS X 10.10.5 from source. But once I arrive at the make step, the following messages show:

Scanning dependencies of target cadabra2python [ 0%] Building CXX object core/CMakeFiles/cadabra2python.dir/cadabra2python.cc.o [ 1%] Building CXX object core/CMakeFiles/cadabra2python.dir/CdbPython.cc.o [ 1%] Linking CXX executable cadabra2python Undefined symbols for architecture x86_64: "boost::re_detail::perl_matcher<char const, std::__1::allocator<boost::sub_match<char const> >, boost::regex_traits<char, boost::cpp_regex_traits > >::construct_init(boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits > > const&, boost::regex_constants::_match_flags)", referenced from: boost::re_detail::perl_matcher<char const, std::__1::allocator<boost::sub_match<char const> >, boost::regex_traits<char, boost::cpp_regex_traits > >::perl_matcher(char const, char const, boost::match_results<char const, std::__1::allocator<boost::sub_match<char const> > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits > > const&, boost::regex_constants::_match_flags, char const) in CdbPython.cc.o "boost::re_detail::get_mem_block()", referenced from: boost::re_detail::perl_matcher<std::1::wrap_iter<char const>, std::1::allocator<boost::sub_match<std::1::wrap_iter<char const*> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::match_imp() in CdbPython.cc.o boost::re_detail::perl_matcher<std::1::wrap_iter<char const*>, std::__1::allocator<boost::sub_match<std::1::wrap_iter<char const*> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::match_all_states() in CdbPython.cc.o boost::re_detail::perl_matcher<std::1::wrap_iter<char const*>, std::__1::allocator<boost::sub_match<std::1::wrap_iter<char const> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::match_startmark() in CdbPython.cc.o boost::re_detail::perl_matcher<std::1::wrap_iter<char const>, std::1::allocator<boost::sub_match<std::1::wrap_iter<char const> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::match_alt() in CdbPython.cc.o boost::re_detail::perl_matcher<std::1::wrap_iter<char const>, std::1::allocator<boost::sub_match<std::1::wrap_iter<char const*> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::match_rep() in CdbPython.cc.o boost::re_detail::perl_matcher<std::1::wrap_iter<char const*>, std::__1::allocator<boost::sub_match<std::1::wrap_iter<char const*> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::match_char_repeat() in CdbPython.cc.o boost::re_detail::perl_matcher<std::1::wrap_iter<char const*>, std::__1::allocator<boost::sub_match<std::1::wrap_iter<char const> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::match_set_repeat() in CdbPython.cc.o ... "boost::re_detail::put_mem_block(void)", referenced from: boost::re_detail::perl_matcher<std::1::wrap_iter<char const*>, std::1::allocator<boost::sub_match<std::1::wrap_iter<char const> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::match_imp() in CdbPython.cc.o boost::re_detail::perl_matcher<std::1::wrap_iter<char const>, std::1::allocator<boost::sub_match<std::1::wrap_iter<char const> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::unwind_extra_block(bool) in CdbPython.cc.o boost::re_detail::perl_matcher<std::1::wrap_iter<char const>, std::1::allocator<boost::sub_match<std::1::wrap_iter<char const> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::find_imp() in CdbPython.cc.o boost::re_detail::perl_matcher<char const, std::1::allocator<boost::sub_match<char const> >, boost::regex_traits<char, boost::cpp_regex_traits > >::match_imp() in CdbPython.cc.o boost::re_detail::perl_matcher<char const, std::__1::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits > >::unwind_extra_block(bool) in CdbPython.cc.o "boost::re_detail::verify_options(unsigned int, boost::regex_constants::_match_flags)", referenced from: boost::re_detail::perl_matcher<std::1::wrap_iter<char const*>, std::__1::allocator<boost::sub_match<std::1::wrap_iter<char const> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::match_imp() in CdbPython.cc.o boost::re_detail::perl_matcher<std::1::wrap_iter<char const>, std::1::allocator<boost::sub_match<std::1::wrap_iter<char const> > >, boost::regex_traits<char, boost::cpp_regex_traits > >::find_imp() in CdbPython.cc.o boost::re_detail::perl_matcher<char const, std::1::allocator<boost::sub_match<char const> >, boost::regex_traits<char, boost::cpp_regex_traits > >::match_imp() in CdbPython.cc.o "boost::re_detail::raise_runtime_error(std::runtime_error const&)", referenced from: void boost::re_detail::raise_error<boost::regex_traits_wrapper<boost::regex_traits<char, boost::cpp_regex_traits > > >(boost::regex_traits_wrapper<boost::regex_traits<char, boost::cpp_regex_traits > > const&, boost::regex_constants::error_type) in CdbPython.cc.o "boost::re_detail::get_default_error_string(boost::regex_constants::error_type)", referenced from: boost::re_detail::cpp_regex_traits_implementation::error_string(boost::regex_constants::error_type) const in CdbPython.cc.o "boost::re_detail::cpp_regex_traits_implementation::transform_primary(char const, char const) const", referenced from: std::1::wrap_iter<char const> boost::re_detail::re_is_set_member<std::1::wrap_iter<char const*>, char, boost::regex_traits<char, boost::cpp_regex_traits >, unsigned int>(std::1::wrap_iter<char const>, std::1::wrap_iter<char const>, boost::re_detail::re_set_long const, boost::re_detail::regex_data<char, boost::regex_traits<char, boost::cpp_regex_traits > > const&, bool) in CdbPython.cc.o char const boost::re_detail::re_is_set_member<char const, char, boost::regex_traits<char, boost::cpp_regex_traits >, unsigned int>(char const, char const, boost::re_detail::re_set_long const, boost::re_detail::regex_data<char, boost::regex_traits<char, boost::cpp_regex_traits > > const&, bool) in CdbPython.cc.o "boost::re_detail::cpp_regex_traits_implementation::transform(char const, char const) const", referenced from: std::1::wrap_iter<char const*> boost::re_detail::re_is_set_member<std::1::wrap_iter<char const*>, char, boost::regex_traits<char, boost::cpp_regex_traits >, unsigned int>(std::1::__wrap_iter<char const>, std::1::wrap_iter<char const>, boost::re_detail::re_set_long const, boost::re_detail::regex_data<char, boost::regex_traits<char, boost::cpp_regex_traits > > const&, bool) in CdbPython.cc.o char const boost::re_detail::re_is_set_member<char const, char, boost::regex_traits<char, boost::cpp_regex_traits >, unsigned int>(char const, char const, boost::re_detail::re_set_long const, boost::re_detail::regex_data<char, boost::regex_traits<char, boost::cpp_regex_traits > > const&, bool) in CdbPython.cc.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: [core/cadabra2python] Error 1 make[1]: [core/CMakeFiles/cadabra2python.dir/all] Error 2 make: *** [all] Error 2

Thank you already for any help!