Re: [bitbake-devel] [PATCH v2] fetch2/wget : reuse cached HTTPS  connections

Richard Purdie <[email protected]>
Newsgroups org.openembedded.lists.bitbake-devel
Message-ID <22dc23fea8c881c3ae8e7a1c2379a53590b89c39.camel@linuxfoundation.org>
On Mon, 2026-08-17 at 06:55 +0000, Fredrik Svensson (svsvenss) wrote:
> Thanks, the new output makes the problem clearer.
> 
> 
> The buildtools OpenSSL is trying to load its configuration from the
> original SDK build path:
> 
> 
> /usr/local/oe-sdk-hardcoded-buildpath/.../openssl.cnf
> 
> 
> It looks like enable_tools_tarball() adds the buildtools binaries to
> PATH, but does not source the scripts under environment-setup.d. The
> OPENSSL_CONF value is set by environment-setup.d/openssl.sh, so
> OpenSSL falls back to its compiled-in path instead.
> 
> 
> I reproduced the same error with the 5.1 buildtools tarball when
> using its OpenSSL without sourcing the complete environment. It works
> when the environment is sourced normally.
> 
> 
> I think the proper fix is for enable_tools_tarball() to import the
> complete sourced environment, including the environment-setup.d
> scripts.
> 
> 
> That would also explain why running the test manually over SSH works.
> I think this is an issue with how yocto-autobuilder-helper imports
> the buildtools environment, rather than with the BitBake HTTPS cache
> change.

Agreed, I was coming to the same conclusion. The issue is that code in
the autobuilder helper... :/

Cheers,

Richard
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.