Closed amstewart closed 1 year ago
At the highest level, I think we have a few options to approach this issue. From most-desirable to least-...
capture.sh
is built into the pyrex image, we may have to slightly rearchitect the image. (I'm not sure about this.)BB_ENV_EXTRAWHITE
in the pyrex source with BB_ENV_PASSTHROUGH_ADDITIONS
.
EXTRAWHITE
. But this might be doing them a disservice in the long term by hiding the incompatibility.
When running any bitbake version >= 2.0 within a pyrex container, bitbake will throw a fatal error during recipe parsing and return code
1
.The error source is here, and it was added to enforce restrictions on insufficiently inclusive variables being defined in the environment. Bitbake will error whenever
BB_ENV_EXTRAWHITE
is defined in the execution environment, and it is unconditionally defined by pyrex.https://github.com/garmin/pyrex/blob/bebe3f9c76c3c12f7646ea97aea0de45b7e2219a/pyrex.py#L554-L557
https://github.com/garmin/pyrex/blob/bebe3f9c76c3c12f7646ea97aea0de45b7e2219a/image/capture.sh#L100-L103
Bitbake 2.0 support is needed for pyrex users to build the OE kirkstone release and beyond.