@bionade24 the latest Boost version removed a header used by aseba. I've reported the issue upstream: https://github.com/Mobsya/aseba/issues/984
You can use the Flatpak in the meantime: https://github.com/Mobsya/aseba/blob/master/flatpak/README.md
Git Clone URL: | https://aur.archlinux.org/aseba-git.git (read-only, click to copy) |
---|---|
Package Base: | aseba-git |
Description: | A set of tools which allow beginners to program robots easily and efficiently. |
Upstream URL: | https://github.com/Mobsya/aseba |
Keywords: | aseba thymio vpl |
Licenses: | LGPL3 |
Provides: | aseba |
Submitter: | THS |
Maintainer: | THS |
Last Packager: | THS |
Votes: | 4 |
Popularity: | 0.000000 |
First Submitted: | 2016-10-05 07:25 (UTC) |
Last Updated: | 2020-07-15 10:52 (UTC) |
@bionade24 the latest Boost version removed a header used by aseba. I've reported the issue upstream: https://github.com/Mobsya/aseba/issues/984
You can use the Flatpak in the meantime: https://github.com/Mobsya/aseba/blob/master/flatpak/README.md
Package doesn't build:
from /tmp/makepkg/aseba-git/src/aseba/aseba/thymio-device-manager/aseba_device.cpp:1: [52/2757]
/usr/include/boost/asio/impl/executor.hpp: In instantiation of 'void boost::asio::executor::impl< <template-parameter-1-1>, <template-paramet
er-1-2> >::on_work_started() [with Executor = boost::asio::any_io_executor; Allocator = std::allocator<void>]':
/usr/include/boost/asio/impl/executor.hpp:76:8: required from here
/usr/include/boost/asio/impl/executor.hpp:78:15: error: 'class boost::asio::any_io_executor' has no member named 'on_work_started'
78 | executor_.on_work_started();
| ~~~~~~~~~~^~~~~~~~~~~~~~~
/usr/include/boost/asio/impl/executor.hpp: In instantiation of 'void boost::asio::executor::impl< <template-parameter-1-1>, <template-paramet
er-1-2> >::on_work_finished() [with Executor = boost::asio::any_io_executor; Allocator = std::allocator<void>]':
/usr/include/boost/asio/impl/executor.hpp:81:8: required from here
/usr/include/boost/asio/impl/executor.hpp:83:15: error: 'class boost::asio::any_io_executor' has no member named 'on_work_finished'
83 | executor_.on_work_finished();
| ~~~~~~~~~~^~~~~~~~~~~~~~~~
/usr/include/boost/asio/impl/executor.hpp: In instantiation of 'void boost::asio::executor::impl< <template-parameter-1-1>, <template-paramet
er-1-2> >::dispatch(boost::asio::executor::function&&) [with Executor = boost::asio::any_io_executor; Allocator = std::allocator<void>; boost
::asio::executor::function = boost::asio::detail::executor_function]':
/usr/include/boost/asio/impl/executor.hpp:91:8: required from here
/usr/include/boost/asio/impl/executor.hpp:93:15: error: 'class boost::asio::any_io_executor' has no member named 'dispatch'
93 | executor_.dispatch(BOOST_ASIO_MOVE_CAST(function)(f), allocator_);
| ~~~~~~~~~~^~~~~~~~
/usr/include/boost/asio/impl/executor.hpp: In instantiation of 'void boost::asio::executor::impl< <template-parameter-1-1>, <template-paramet
er-1-2> >::post(boost::asio::executor::function&&) [with Executor = boost::asio::any_io_executor; Allocator = std::allocator<void>; boost::as
io::executor::function = boost::asio::detail::executor_function]':
/usr/include/boost/asio/impl/executor.hpp:96:8: required from here
/usr/include/boost/asio/impl/executor.hpp:98:15: error: 'class boost::asio::any_io_executor' has no member named 'post'
98 | executor_.post(BOOST_ASIO_MOVE_CAST(function)(f), allocator_);
| ~~~~~~~~~~^~~~
/usr/include/boost/asio/impl/executor.hpp: In instantiation of 'void boost::asio::executor::impl< <template-parameter-1-1>, <template-paramet
er-1-2> >::defer(boost::asio::executor::function&&) [with Executor = boost::asio::any_io_executor; Allocator = std::allocator<void>; boost::a
sio::executor::function = boost::asio::detail::executor_function]':
/usr/include/boost/asio/impl/executor.hpp:101:8: required from here
/usr/include/boost/asio/impl/executor.hpp:103:15: error: 'class boost::asio::any_io_executor' has no member named 'defer'; did you mean 'pref
er'?
103 | executor_.defer(BOOST_ASIO_MOVE_CAST(function)(f), allocator_);
| ~~~~~~~~~~^~~~~
| prefer
[15/120] Building CXX object aseba/targets/playground/CMakeFiles/asebaplayground.dir/asebaplayground_autogen/mocs_compilation.cpp.o
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
Aborting...
I updated aseba to use the maintained fork from Mobsya which now integrated into the Thymio suite.
You might need to update the firmware on your Thymio to use this version.
@meberlei this should be fixed.
@paoda and @SonGokuJ dependencies should be fixed. gcc is part of base-devel and it can be assumed that this package is installed.
Hey there, aseba-git currently always tries to update to a new version even if there is none. Could you change up your pckver() Method so it either incorporates the Package Version Number or PkgRel Number, so that it doesn't get rebuilt every time especially since the building process on this app takes pretty long. Would be nice, thanks. Greetings, meberlei
in addition to @paoda `s comment, that cmake is needed for the build, please also add gcc and qwt to the dependencies. That would help a lot, as it took quite some time to find them as the reason for the build error. thank you
since this package won't compile w/out cmake, it should be listed as a dependency, I think.
@Jojo_Linux glad that your issue is solved. I'll pin your comment but I think there is no good workaround that I can implement to solve this issue automatically.
Here is the solution : https://www.thymio.org/forum/t-4982325/aseba-et-archlinux#post-4099117 (in french).
It is a problem with locale. I had only fr_FR.UTF-8 enabled. Way to fix :
Uncomment en_US.UTF-8 in /etc/locale.gen
Run locale-gen
@THS This is why you didn't have this bug ;-)
Thanks
@THS I've tried with Aseba Playground and I have the error too.
Way to reproduce : - Launch asebastudio - Choose VPL - Add an event, then an action.
But if I add a second event before I add an action, it's ok. But in this case I can't download the program in the Thymio :) And if I add a second action, VPL crashes again.
Like you, I updated my system and rebuilt aseba-git. Maybe a dependance is missing... I've tried to build aseba-git on two other updated Arch systems, with the same error.
Thanks for your help.
@THS Thank you for your answer. I've tried to compile from https://github.com/Mobsya/aseba with your PKGBUILD. But :
error: Le serveur n'autorise pas de requête pour l'objet 872666f0633635797f698da42198e7a2d1c97a0b non annoncé Chemin de sous-module 'enki' récupéré, mais il ne contenait pas 872666f0633635797f698da42198e7a2d1c97a0b. La récupération directe de ce commit a échoué.
It is very strange because I've used Aseba many times between january and july with no problem.
Pinned Comments
THS commented on 2020-07-15 10:59 (UTC) (edited on 2020-07-15 10:59 (UTC) by THS)
I updated aseba to use the maintained fork from Mobsya which now integrated into the Thymio suite.
You might need to update the firmware on your Thymio to use this version.
@meberlei this should be fixed.
@paoda and @SonGokuJ dependencies should be fixed. gcc is part of base-devel and it can be assumed that this package is installed.