Created attachment 4369 [details] devtool build log error Yocto v2.3.4, Ubuntu 16.04.5 I have a recipe which builds the Linux kernel from current linux-next. Recently it seems it got included in to the extensible SDK (which is fine) and it brings back old problem with devtool - lack of ca-certificates. After devtool update: devtool build XXX fatal: unable to access 'https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/': Problem with the SSL CA cert (path? access rights?) The GIT_SSL_CAINFO points to non-existing /home/krzk/proceq17_sdk/buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/certs/ca-certificates.crt. Running devtool with GIT_SSL_CAINFO="/etc/ssl/certs/ca-certificates.crt" helps... but this is annoying workaround. I already have to use it for the same error happening with devtool sdk-update (my sdk-update URL is https). Installing new SDK also fails with the same error.
Created attachment 4370 [details] SDK install error
New eSDK installs can be fixed by adding to machine conf file: TOOLCHAIN_HOST_TASK += "nativesdk-ca-certificates" However the updated SDK still fails because as usual the sdk-update does not properly populates sysroots with new changes. Anyway, probably the nativesdk-ca-certificates should be part of default SDK packages.
Would you be able to test this with a newer release than 2.3.4?
I setup a Yocto with different, minimal configuration, without any custom machine... and I cannot reproduce the error. I tried v2.3.4, v2.4.3 and v2.5.1. In this new setup, in eSDK the file buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/certs/ca-certificates.crt exists. There must be something different between the setups.
OK, I reproduced it also on v2.5.1 so no problem of testing it also later with a new release. While trying to reproduce it on more vanilla-like configuration, I narrowed it to the presence of following in distro or machine conf: TOOLCHAIN_HOST_TASK += "nativesdk-u-boot-mkimage" Without this line - works. I compared for example the glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-2.3.4.testdata.json between such cases. Working (without TOOLCHAIN_HOST_TASK above): "SDK_REQUIRED_UTILITIES": "patch diffstat bzip2 gawk cpio perl file which gcc g++", Broken (with TOOLCHAIN_HOST_TASK above): "SDK_REQUIRED_UTILITIES": "patch diffstat makeinfo git bzip2 tar gzip gawk chrpath wget cpio perl file which gcc g++",
TOOLCHAIN_HOST_TASK is lazy assigned so if you want to extend it, use TOOLCHAIN_HOST_TASK_append.
Krzysztof, can you test as I said in comment 6? I believe that will solve this issue but if not we need to reopen the bug.
Some more background - it seems that problem in my setup was caused by improper use of TOOLCHAIN_HOST_TASK at the first place. In my image recipe I had: TOOLCHAIN_HOST_TASK += "nativesdk-cmake" Using TOOLCHAIN_HOST_TASK_append helps in such case. Moving TOOLCHAIN_HOST_TASK from image recipe to machine file (and using +=) solves the problem as well, without the need to add "nativesdk-ca-certificates" manually. Therefore I think this bug should be marked invalid (unless something could be added to bitbake to warn about such case). Best regards, Krzysztof