diff options
| author |   Denys Dmytriyenko <denys@ti.com> | 2018-01-10 00:09:00 -0500 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-01-11 23:22:43 +0000 |
| commit | 5f4b54a234ad7a859db8a1e23c6892a8b3bc1b52 (patch) | |
| tree | eab0cb0ccf95d1fe2efa71e52de6c96730220856 /meta/recipes-extended | |
| parent | bead76b50dc60e1b6b39fa5b659a7af44ff91adc (diff) | |
| download | openembedded-core-contrib-5f4b54a234ad7a859db8a1e23c6892a8b3bc1b52.tar.gz | |
perf: depend on native versions of bison and flex
Explicitly depend on bison-native and flex-native for deterministic builds,
as those are required for the build:
| Makefile.config:129: *** Error: flex is missing on this system, please install it. Stop.
| Makefile.perf:205: recipe for target 'sub-make' failed
| make[1]: *** [sub-make] Error 2
| Makefile:68: recipe for target 'all' failed
| make: *** [all] Error 2
| Makefile.config:133: *** Error: bison is missing on this system, please install it. Stop.
| Makefile.perf:205: recipe for target 'sub-make' failed
| make[1]: *** [sub-make] Error 2
| Makefile:68: recipe for target 'all' failed
| make: *** [all] Error 2
In most cases, those dependencies come indirectly via toolchain dependencies,
specifically binutils-cross, which pulls both bison-native and flex-native.
Different setups, such as with external toolchain, would expose this problem,
since correct dependency is not marked explicitly.
The change is build-tested on all qemu architectures.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended')
0 files changed, 0 insertions, 0 deletions