Sha256: a050ec8f81f7ba34b0b032c749d28e44ccf08c86b0d0c34ca2558a7dc1b5da52
Contents?: true
Size: 1.71 KB
Versions: 27
Compression:
Stored size: 1.71 KB
Contents
---
title: Understanding autoproj error messages
sort_info: 90
---
I know nothing about a prepackaged package called 'XXXX', ...
------------------------------------------
_Short explanation_: an OS dependency is listed by one of the packages, but no
definition exists in one of the osdeps files.
_Long explanation_: XXXX is listed as an operating system dependency by one of
the packages that you requested to build. Two solutions: (i) the package should
*not* depend on it, and you should modify the [package's
manifest.xml](package_sets/manifest-xml.html) file. (ii)
the package should depend on it and you should list the OS package in [the
relevant osdeps file](package_sets/osdeps.html)
XXX depends on YYY, which is excluded from the build {#exclusions}
----------------------------------------------------
The layout requires the XXX package to be built, but this package depends on YYY
and YYY has explicitely been excluded from the build.
There are two cases.
In the first case, the package has been listed in [the exclude_packages section
of autoproj/manifest](customization.html#exclude_packages). So, you will have to
find out why and either remove it from there, or add XXX to the same section.
In the second case, the package is disabled on your operating system version.
This is done in the package set's autobuild files by using the [not_on and
only_on statements](package_sets/autobuild.html#not_on_and_only_on). You will
have to either exclude the XXX package as well (either by including it in the
same not_on/only_on block, or by adding it to [the exclude_packages section
of autoproj/manifest](customization.html#exclude_packages)), or to make it so
that YYY builds on your OS, an thus remove it from the not_on/only_on block.
Version data entries
27 entries across 27 versions & 1 rubygems