| Git Clone URL: | https://aur.archlinux.org/gazebo.git (read-only, click to copy) |
|---|---|
| Package Base: | gazebo |
| Description: | A multi-robot simulator for outdoor environments |
| Upstream URL: | https://classic.gazebosim.org/ |
| Licenses: | Apache |
| Submitter: | None |
| Maintainer: | acxz |
| Last Packager: | acxz |
| Votes: | 35 |
| Popularity: | 0.007356 |
| First Submitted: | 2008-10-18 22:59 (UTC) |
| Last Updated: | 2023-12-11 14:35 (UTC) |
Hello !
This package ships a GAZEBO_CXX_FLAGS with '-std=c++11'. This is breaking downstream packages that require C++14 or C++17, which should work by default with Arch's GCC 11 as it defaults to C++17.
Could we patch this ? a "sed -i '/-std=c++11/d' cmake/gazebo-config.cmake.in" seems to be enough :)
No that's ok! Let's leave it there for posterity.
I've done the same kind of thing myself, so dw about it :-)
@billypilgrim Sorry you are completely right. It seemed to be my fault somehow but I still don't why the package did not install as dep during the process. Nevermind I'll try to figure out want went wrong there. Should I delete my previous comment?
@t00manysecrets ruby-mustache is a dependency of ruby-ronn-ng which already is a dependency. Is ruby-mustache installed on your machine and is it up to date? It seems like ruby is trying to use an old version; might you have installed it as a gem before?
When I wanted to install gazebo today I received the error below while executing the package()-Step DESTDIR="${pkgdir}" ninja install for nearly all 8 components. As far as I can tell gazebo needs the ruby-mustache package so I would suggest adding it to the dependency list because installing the package beforehand avoids this issue. Has anyone noticed a similar problem?
-- Install configuration: "Release"
[1/8] Generating gzprop.1
FAILED: tools/gzprop.1
cd /tmp/gazebo/gazebo-11.6.0/build/tools && /usr/bin/ronn -r --pipe /tmp/gazebo/gazebo-11.6.0/tools/gzprop.1.ronn > /tmp/gazebo/gazebo-11.6.0/build/tools/gzprop.1
/usr/lib/ruby/3.0.0/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'mustache' (~> 1.0) among 125 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/home/frederik/.local/share/gem/ruby/3.0.0:/usr/lib/ruby/gems/3.0.0' at: /usr/lib/ruby/gems/3.0.0/specifications/ronn-ng-0.9.1.gemspec, execute `gem env` for more information
from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1401:in `block in activate_dependencies'
from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1390:in `each'
from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1390:in `activate_dependencies'
from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1372:in `activate'
from /usr/lib/ruby/3.0.0/rubygems.rb:302:in `block in activate_bin_path'
from /usr/lib/ruby/3.0.0/rubygems.rb:301:in `synchronize'
from /usr/lib/ruby/3.0.0/rubygems.rb:301:in `activate_bin_path'
from /usr/bin/ronn:23:in `<main>'
/usr/lib/ruby/3.0.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'mustache' (~> 1.0) - did find: [mustache-0.99.8] (Gem::MissingSpecVersionError)
Checked in 'GEM_PATH=/home/frederik/.local/share/gem/ruby/3.0.0:/usr/lib/ruby/gems/3.0.0' , execute `gem env` for more information
from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1402:in `block in activate_dependencies'
from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1390:in `each'
from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1390:in `activate_dependencies'
from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1372:in `activate'
from /usr/lib/ruby/3.0.0/rubygems.rb:302:in `block in activate_bin_path'
from /usr/lib/ruby/3.0.0/rubygems.rb:301:in `synchronize'
from /usr/lib/ruby/3.0.0/rubygems.rb:301:in `activate_bin_path'
from /usr/bin/ronn:23:in `<main>'
EDIT:
Could this dependency be missing in ruby-ronn instead?
Is there any particular reason why Gazebo still use ancient libxml package rather than libxml2 ? I have successfully build gazebo with libxml2.
@petersill PSA that packages should ONLY be flagged out of date if there is a new upstream version of the software available. If the PKGBUILD is broken, then please just leave a comment.
@AchmadFathoni Thank you for pointing this out. The root cause is that ignition-common-3 doesn't have ignition-common in its provides array. I've posted a message about this: https://aur.archlinux.org/packages/ignition-common-3/#comment-808324
gazebo depends on ignition-fuel_tools-4 which is depends on ignition-common-3. But gazebo itself depends on ignition-common. Replace ignition-common>=3 with ignition-common-3 may solve this problem.
got
:: Resolving dependencies...
:: There are 3 providers available for gazebo:
:: Repository AUR:
1) gazebo 2) gazebo-10 3) gazebo-git
Enter a number (default=1):
:: Calculating conflicts...
:: Calculating inner conflicts...
:: Marked out of date: ignition-common
Aur (4) ignition-common-3.9.0-1 ignition-common-3-3.13.1-1 ignition-fuel_tools-4-4.3.0-1 gazebo-11.5.1-1
:: Proceed to review? [Y/n]: n
The double ignition-common and ignition-common-3 lead to package exists in the filesystem error
11.5.0 is released in https://github.com/osrf/gazebo/releases. Should this AUR be updated?
Pinned Comments
billypilgrim commented on 2022-05-09 16:04 (UTC)
Development is on Github: https://github.com/acxz/gazebo-arch Please open issues and PRs there instead of commenting.