py-shiboken fails on Rosetta on shibokenmodule: malloc: *** error for object 0xa0f15754: pointer being freed was not allocated

[barracuda156]

Identical failure with py27-shiboken and py310-shiboken.

[ 95%] Built target shiboken
make  -f shibokenmodule/CMakeFiles/shibokenmodule.dir/build.make shibokenmodule/CMakeFiles/shibokenmodule.dir/depend
make[2]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py310-shiboken/work/build'
[ 96%] Running generator for 'shiboken'...
cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py310-shiboken/work/Shiboken-1.2.4/shibokenmodule && /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py310-shiboken/work/build/generator/shiboken --project-file=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py310-shiboken/work/build/shibokenmodule/shibokenmodule.txt
shiboken(63722,0xa0bcc620) malloc: *** error for object 0xa0f15754: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
shiboken(63722,0xa0bcc620) malloc: *** error for object 0xa0f157c4: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Detecting inconsistencies in typesystem...   [OK]
/bin/sh: line 1: 63722 Bus error               /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py310-shiboken/work/build/generator/shiboken --project-file=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py310-shiboken/work/build/shibokenmodule/shibokenmodule.txt
make[2]: *** [shibokenmodule/shiboken/shiboken_module_wrapper.cpp] Error 138
make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py310-shiboken/work/build'
make[1]: *** [shibokenmodule/CMakeFiles/shibokenmodule.dir/all] Error 2

[kencu (Ken)]

looks like probably yet another example of the libgcc ABI error we have been seeing these past five years or so.

when it happens during the build using a generated tool like this it can be harder to fix by binwrapping.

maybe you could force the dyld lib path for the build to libgcc, or link in libgcc statically maybe.

hopefully someone fixes this properly someday

[barracuda156]

Tried adding via legacysupport PG:

platform darwin powerpc {
    PortGroup       legacysupport 1.1

    configure.cxx_stdlib \
                    macports-libstdc++
}

But while malloc error line is not there now, Bus error persists:

[ 96%] Running generator for 'shiboken'...
cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py27-shiboken/work/Shiboken-1.2.4/shibokenmodule && /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py27-shiboken/work/build/generator/shiboken --project-file=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py27-shiboken/work/build/shibokenmodule/shibokenmodule.txt
Detecting inconsistencies in typesystem...   [OK]
/bin/sh: line 1: 33267 Bus error               /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py27-shiboken/work/build/generator/shiboken --project-file=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py27-shiboken/work/build/shibokenmodule/shibokenmodule.txt
make[2]: *** [shibokenmodule/shiboken/shiboken_module_wrapper.cpp] Error 138
make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-shiboken/py27-shiboken/work/build'
make[1]: *** [shibokenmodule/CMakeFiles/shibokenmodule.dir/all] Error 2

[barracuda156]

Replying to kencu:

looks like probably yet another example of the libgcc ABI error we have been seeing these past five years or so.

when it happens during the build using a generated tool like this it can be harder to fix by binwrapping.

maybe you could force the dyld lib path for the build to libgcc, or link in libgcc statically maybe.

hopefully someone fixes this properly someday

How to do it though? I have a same problem with Rawstudio, and tried this:

        build.env-append \
                DYLD_LIBRARY_PATH=${prefix}/lib/libgcc

To no effect.

[barracuda156]

Replying to kencu:

Hmm, I just commented out these lines in portfile:

#    compiler.cxx_standard 2011
#    configure.cxxflags-append -std=c++11

And py27-shiboken has built fine with gcc-4.2. Maybe C++11 is needed for py3x versions, but apparently not for py27 one.

[barracuda156]

16. S. Are there some non-obvious reasons to set C++11 for py-shiboken generally, instead of its py3- versions?

[kencu (Ken)]

you would normally look through the commit history and comments to answer that question.

sometimes there is no good reason, and things get added out of expediency because it happened to work on one person’s system, either hackishly or from inexperience of users (which you see me constantly pushing back against in the PR queue)