Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stderr ignition-fuel_tools6 while building #202

Open
ggiulian opened this issue Aug 28, 2021 · 7 comments
Open

stderr ignition-fuel_tools6 while building #202

ggiulian opened this issue Aug 28, 2021 · 7 comments
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@ggiulian
Copy link

ggiulian commented Aug 28, 2021

Environment

  • OS Version: Ubuntu 20.04

  • Source or binary build?
    source: ROS2 Galactic and Ignition Edifice

    When building there is this stderr referred to developers and authors of ignition fuel tools

# paste log here
```stderr: ignition-fuel_tools6             
CMake Warning (dev) at /home/ggiuliano/edifice_ws/install/share/cmake/ignition-cmake2/cmake2/IgnUtils.cmake:385 (message):
   -- THIS MESSAGE IS INTENDED FOR IGNITION-FUEL_TOOLS AUTHORS --
      (IF YOU SEE THIS, PLEASE REPORT IT)

  Could not find pkg-config information for YAML.  It was not provided by the
  find-module for the package, nor was it explicitly passed into the call to
  ign_find_package(~).  This is most likely an error in this project's use of
  ign-cmake.
Call Stack (most recent call first):
  CMakeLists.txt:42 (ign_find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

---
Finished <<< ignition-fuel_tools6 [6min 10s]







@ggiulian ggiulian added the bug Something isn't working label Aug 28, 2021
@chapulina
Copy link
Contributor

Do you have libyaml installed? What version is it?

@ggiulian
Copy link
Author

Yes, the version is the newest: 0.2.2-1

@chapulina
Copy link
Contributor

Interesting, I have the same version and it works for me, and it also works on CI.

We'll need more information about what steps you took to get to this problem.

@ggiulian
Copy link
Author

Mainly, I followed this documentation: https://ignitionrobotics.org/docs/edifice/install_ubuntu_src.
leaving out the installations of generic tools, vcs and colcon from pip or apt (because already installed) and git. So I created the workspace on the home, after that I followed the instructions of the documentation. I have left out the installation of gcc and g ++, since I work on Focal. Eventually I built everything with colcon build --merge-install

@ggiulian
Copy link
Author

I tried with different build like colcon build --cmake-args -DBUILD_TESTING=OFF --merge-install and colcon build --packages-select PACKAGE_NAME but i had the same stderr

@chapulina chapulina added the help wanted Extra attention is needed label Nov 17, 2021
@bperseghetti
Copy link
Member

@azeey @j-rivero appears this might still be a lingering issue:

--- stderr: gz-fuel_tools9                                                                                                                                                  
CMake Warning (dev) at /home/user/git/harmonic/install/share/cmake/gz-cmake3/cmake3/GzFindPackage.cmake:456 (message):
   -- THIS MESSAGE IS INTENDED FOR GZ-FUEL_TOOLS AUTHORS --
      (IF YOU SEE THIS, PLEASE REPORT IT)

  Could not find pkg-config information for YAML.  It was not provided by the
  find-module for the package, nor was it explicitly passed into the call to
  gz_find_package(~).  This is most likely an error in this project's use of
  gz-cmake.
Call Stack (most recent call first):
  CMakeLists.txt:44 (gz_find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

---
Finished <<< gz-fuel_tools9 [26.1s]

@azeey
Copy link
Contributor

azeey commented Jun 18, 2024

I was able to reproduce this if I source a ROS humble installation with ros-humble-libyaml-vendor installed. I suspect this is fixed in Jazzy since the libyaml_vendor package has been updated to use ament_cmake_vendor_package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants