You are not logged in.

#1 2019-07-14 09:03:33

tommy3001
Member
Registered: 2019-07-14
Posts: 2

AUR shiboken 1.2.4-4 build terminates with segmentation fault

Hallo.
I want to install shiboken 1.2.4-4  from AUR.

But it terminates with:

[ 90%] Building CXX object generator/CMakeFiles/shiboken.dir/shiboken/shibokennormalize.cpp.o
[ 91%] Building CXX object generator/CMakeFiles/shiboken.dir/main.cpp.o
[ 93%] Building CXX object generator/CMakeFiles/shiboken.dir/qtdoc/qtdocgenerator.cpp.o
[ 95%] Linking CXX executable shiboken
[ 95%] Built target shiboken
[ 96%] Running generator for 'shiboken'...
Detecting inconsistencies in typesystem...   [OK]
make[2]: *** [shibokenmodule/CMakeFiles/shibokenmodule.dir/build.make:62: shibokenmodule/shiboken/shiboken_module_wrapper.cpp]
Speicherzugriffsfehler (Speicherauszug erstellt)
make[1]: *** [CMakeFiles/Makefile2:370: shibokenmodule/CMakeFiles/shibokenmodule.dir/all] Fehler 2
make: *** [Makefile:130: all] Fehler 2
==> FEHLER: Ein Fehler geschah in build().
    Breche ab...


"Error in build()"

"Speicherzugriffsfehler (Speicherauszug erstellt) "
Is a segmentation fault.


Any idea? .. and where I can find the core dump?
Its a  Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz Notebook.

THX.

Offline

#2 2019-07-14 11:21:38

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: AUR shiboken 1.2.4-4 build terminates with segmentation fault

That's an old version AND requires qt4 .
Are you sure yoiu can't use shiboken2 from repos instead ?


for info about coredumps and how to find/view them

$ man systemd-coredump
$ man coredumpctl

You did build in a clean chroot, right ?

Please  post full build log somewhere
https://wiki.archlinux.org/index.php/Li … in_clients

Last edited by Lone_Wolf (2019-07-14 11:23:03)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2019-07-15 12:12:10

tommy3001
Member
Registered: 2019-07-14
Posts: 2

Re: AUR shiboken 1.2.4-4 build terminates with segmentation fault

For me it is obvious that I need it for AUR ros-melodic-qt-gui-cpp  0.3.11-3
I followed Building_in_a_clean_chroot Wiki to build in a clean chroot environment.
But I got the same issue.

Build log:
https://pastebin.com/11i6FuhH

gdb backtrace with coredumpctl gdb <PID>:

https://pastebin.com/98u07nXB

But I must say, that I have to go a long way to get ros running on arch...

Offline

#4 2019-07-15 12:54:22

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: AUR shiboken 1.2.4-4 build terminates with segmentation fault

There have been several ros-related threads the past months, you're not the only one.
Maybe ros is transitioning from python2 + qt4 to python3 + qt5 ?

ros-melodic-qt-gui-cpp lists qt5-base as dependency so doesn't need qt4 .
I have a feeling you may not need shiboken, but now it's clear you want ros-melodic-qt-gui-cpp let's analyse what you need to build .

The aur dependencies of ros-melodic-qt-gui-cpp are :
    ros-melodic-pluginlib
    ros-melodic-qt-gui
    ros-build-tools (ros-build-tools-py3) (make)
    ros-melodic-catkin (make)
    ros-melodic-cmake-modules (make)
    ros-melodic-pluginlib (make)
    ros-melodic-python-qt-binding (make)


ros-melodic-pluginlib, ros-melodic-qt-gui , ros-melodic-cmake-modules and ros-melodic-python-qt-binding all  list ros-build-tools as dep,
Let's start with that one.

ros-build-tools (ros-build-tools-py3) (make)

That line indicates we have 2 alternatives that provide ros-build-tools : ros-build-tools and ros-build-tools-py3


python2 is almost end of life , so we don't want python2 versions unless there's no other choice.
Try building ros-build-tools-py3 .

If succesfull, continue following the dependency tree down.
When there are alternatives for a dependency , check what they need
If they use deprecated /end-of-live or close to end-of-live stuff , look further.
Also keep in mind repo packages are preferred over aur packages.

Last edited by Lone_Wolf (2019-07-15 12:55:26)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

Board footer

Powered by FluxBB