Re: compiling libapl for python3

2023-03-01 Thread vvs
> i had upgraded gcc-6.3.0 to gcc-12.2.0 after my original compiling of svn > 1553 > > if i recompile svn 1553 with the current gcc-12.2.0 i get the same above > error (but recompiling with gcc-6.3.0 gives a good lib_gnu_apl.so) > > if i recompile svn 1651 with gcc-6.3.0 i get a good python3 lib_gn

Re: compiling libapl for python3

2023-03-01 Thread enztec
Hi Jürgen, I now get : import gnu_apl ImportError: /usr/local/lib/python3.10/lib-dynload/gnu_apl.cpython-310-x86_64-linux-gnu.so: undefined symbol: __stack_chk_guard i had upgraded gcc-6.3.0 to gcc-12.2.0 after my original compiling of svn 1553 if i recompile svn 1553 with the current gcc-12.

Re: compiling libapl for python3

2023-03-01 Thread Dr . Jürgen Sauermann
Hi again, I believe that I have found the problem. main() was indeed referenced from APL (in Backtrace.cc) and apparently Python 3.10 has become more picky about undefined symbols in shared libraries than e.g. 3.8. As a matter of fa

Re: compiling libapl for python3

2023-03-01 Thread Dr . Jürgen Sauermann
Hi enztec, The error message that you are getting is rather strange since the .so file is not supposed  to contain a main symbol (and the python API for 3.10 looks the same as for 3.8. And none of the other python .so libraries has a symbol 'mai