summaryrefslogtreecommitdiffstats
path: root/meta/recipes-graphics/xorg-xserver
diff options
context:
space:
mode:
authorAleksandar Nikolic <aleksandar.nikolic@zeiss.com>2024-06-11 11:25:57 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2024-06-12 16:08:32 +0100
commit062c289efadc355da8c3dc77bc91f1f47b677b68 (patch)
tree9e967cf15dfae8dd0bb1509eecf85eb8813b0734 /meta/recipes-graphics/xorg-xserver
parentcedb7197cc689c2fc87195697efc01ed784dfce7 (diff)
downloadpoky-062c289efadc355da8c3dc77bc91f1f47b677b68.tar.gz
install-buildtools: fix "test installation" step
The "Test installation" step fails with some harmless error messages (see [1]). This can however make a user think that the buildtools have not been installed correctly. Two reasons for the error messages: - some envvars in the environment-setup-<arch>-pokysdk-linux file start and end with double quotes (e.g., PATH) and are as such written into python os.environ. This leads that their usage is not valid later when testing the installation. This patch removes the double quotes before writing, if they are present. - if installation directory (install_dir), given through the option --directory, is given as a relative path, checking if the path to a tool (e.g., gcc) in buildtools starts it will always fail. This patch converts the install_dir variable to an absolute path. [1] ERROR: Something went wrong: tar not found in ./build-tools ERROR: Something went wrong: installation failed (From OE-Core rev: e4eb0b14ecf9bd2fba13260441c9d86eb348f41e) Signed-off-by: Aleksandar Nikolic <aleksandar.nikolic@zeiss.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-graphics/xorg-xserver')
0 files changed, 0 insertions, 0 deletions