From: "Changqing Li" <changqing.li@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] buildtools-tarball: add envvars into BB_ENV_PASSTHROUGH_ADDITIONS
Date: Fri, 11 Apr 2025 02:35:56 -0700 [thread overview]
Message-ID: <2395.1744364156005400114@lists.openembedded.org> (raw)
In-Reply-To: <20250408093822.479573-2-changqing.li@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
Hi,
Following error is reported without this commit: "7ed9f4b7aa curl: only set CA bundle in target build"
Cloning into 'protobuf'...
fatal: unable to access 'https://github.com/protocolbuffers/protobuf/': error setting certificate file: /usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-wrlinuxsdk-linux/etc/ssl/certs/ca-certificates.crt
With commit "7ed9f4b7aa curl: only set CA bundle in target build", git clone still failed, but with another error:
fatal: unable to access 'https://github.com/protocolbuffers/protobuf/': SSL certificate problem: unable to get local issuer certificate
For native-curl, if we don't set --with-ca-bundle, since it is not cross-compile, it will detect the default CA cert bundle/path, that is host cert.
but for nativesdk-curl, it is detect as cross-compile(build=x86_64-linux, host=x86_64-pokysdk-linux), so no default CA cert bundle is detect. So report error "unable to get local issuer certificate".
I think we still need to add GIT_SSL_CAINFO/CURL_CA_BUNDLE/REQUESTS_CA_BUNDLE into BB_ENV_PASSTHROUGH_ADDITIONS.
But another patch is needed to try to make curl use host cert by default.
Regards
Changqing
[-- Attachment #2: Type: text/html, Size: 1320 bytes --]
prev parent reply other threads:[~2025-04-11 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 9:38 [PATCH 1/2] buildtools-tarball: move setting of envvars to respective envfile changqing.li
2025-04-08 9:38 ` [PATCH 2/2] buildtools-tarball: add envvars into BB_ENV_PASSTHROUGH_ADDITIONS changqing.li
2025-04-11 9:35 ` Changqing Li [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2395.1744364156005400114@lists.openembedded.org \
--to=changqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox