which SVN version worked on your side? And does it still work?
I suppose that the python callling conventions for modules have changed in
the meantime, since there never was a main() function in python_apl.cc.
Best Regards,
Jürgen
On 2/27/23 10:35 PM, enz...@gmx.com
wrote:
Hi Jürgenimport gnu_aplTraceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: /usr/local/lib/python3.10/lib-dynload/gnu_apl.cpython-310-x86_64-linux-gnu.so: undefined symbol: maina gnu_apl.so from an earlier svn compile works fine - so nothing has changed at this end thanks On Sun, 26 Feb 2023 18:18:27 +0100 Dr. Jürgen Sauermann <m...@xn--jrgen-sauermann-zvb.de> wrote:Hi enztec, thanks, fixed in SVN 1650. Best Regards, Jürgen On 2/25/23 1:01 AM, enz...@gmx.com wrote: when compiling libapl for python3 i get following make problem python_apl.cc: In function 'PyObject* apl_exec(PyObject*, PyObject*)': python_apl.cc:198:64: error: no matching function for call to 'Workspace::SI_top_error()' 198 | if (const StateIndicator * si = Workspace::SI_top_error()) | ~~~~~~~~~~~~~~~~~~~~~~~^~ In file included from python_apl.cc:15: Workspace.hh:212:28: note: candidate: 'static StateIndicator* Workspace::SI_top_error(bool)' 212 | static StateIndicator * SI_top_error(bool quad_LRX);