Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

As stated in the log the buildfarm is not able to find the tool "pkg-config" which is called to find compiler and linker flags for packages. When your package depends on i.e. "ros" it should pull in that dependency automatically. Can you provide a link to the exact repository state you are trying to build? May be from a look to that it becomes clear why there is no transitive dependency to pkg-config.

As stated in the log the buildfarm is not able to find the tool "pkg-config" which is called to find compiler and linker flags for packages. When your package depends on i.e. "ros" it should pull in that dependency automatically. automatically.

Can you provide a link to the exact repository state you are trying to build? May be from a look to that it becomes clear why there is no transitive dependency to pkg-config.

I have to correct my previous answer: since "ros" is the build dependency of your stack you will only get it's runtime dependencies. Therefore you do not get pkg-config as a dependency of your stack. After that I looked further where the need for pkg-config came from. Actually std_msgs is using pkg-config via backticks in the manifest.xml to fetch the compiler and linker flags. But it does not state that dependency in it's stack.xml. Therefore I have added that missing dependency to std_msgs and just released std_msgs-0.4.11 (as always: it takes some time for the debian packages to appear in shadow-fixed and than public).

As stated in the log the buildfarm is not able to find the tool "pkg-config" which is called to find compiler and linker flags for packages. When your package depends on i.e. "ros" it should pull in that dependency automatically.

Can you provide a link to the exact repository state you are trying to build? May be from a look to that it becomes clear why there is no transitive dependency to pkg-config.

--

I have to correct my previous answer: since "ros" is the build dependency of your stack you will only get it's runtime dependencies. Therefore you do not get pkg-config as a dependency of your stack. After that I looked further where the need for pkg-config came from. Actually std_msgs is using pkg-config via backticks in the manifest.xml to fetch the compiler and linker flags. But it does not state that dependency in it's stack.xml. Therefore I have added that missing dependency to std_msgs and just released std_msgs-0.4.11 (as always: it takes some time for the debian packages to appear in shadow-fixed and than public).