From: Julian Vetter via buildroot <buildroot@buildroot.org>
To: bernd@kuhls.net
Cc: buildroot@buildroot.org, julian@outer-limits.org
Subject: Re: [Buildroot] [PATCH] package/php: Add parth to ca-cert
Date: Mon, 16 Feb 2026 10:29:33 +0100 [thread overview]
Message-ID: <85c4070c-551a-4586-80b1-0f43b454ec69@outer-limits.org> (raw)
In-Reply-To: <20260122161116.885373-1-julian@outer-limits.org>
On 1/22/26 5:11 PM, Julian Vetter via buildroot wrote:
> If BR2_PACKAGE_CA_CERTIFICATES is present, add the ca-certificates.crt
> to the php.ini, to not get SSL errors when using PHP.
>
> Signed-off-by: Julian Vetter <julian@outer-limits.org>
> ---
> package/php/php.mk | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/package/php/php.mk b/package/php/php.mk
> index 2c91ef7b63..3c79ae4589 100644
> --- a/package/php/php.mk
> +++ b/package/php/php.mk
> @@ -362,6 +362,14 @@ endef
>
> PHP_POST_INSTALL_TARGET_HOOKS += PHP_INSTALL_FIXUP
>
> +ifeq ($(BR2_PACKAGE_CA_CERTIFICATES),y)
> +define PHP_CERTIFICATES_FIXUP
> +$(SED) 's%;openssl.cafile=%openssl.cafile=/etc/ssl/certs/ca-certificates.crt%' \
> + $(TARGET_DIR)/etc/php.ini
> +endef
> +PHP_POST_INSTALL_TARGET_HOOKS += PHP_CERTIFICATES_FIXUP
> +endif
> +
> PHP_CONF_ENV += CFLAGS="$(PHP_CFLAGS)" CXXFLAGS="$(PHP_CXXFLAGS)"
>
> HOST_PHP_CONF_OPTS = \
Hello,
I might have forgotten to add you Bernd. I think I have just sent it to
the mailinglist.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-16 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 16:11 [Buildroot] [PATCH] package/php: Add parth to ca-cert Julian Vetter via buildroot
2026-02-16 9:29 ` Julian Vetter via buildroot [this message]
2026-03-07 9:20 ` Julian Vetter via buildroot
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=85c4070c-551a-4586-80b1-0f43b454ec69@outer-limits.org \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=julian@outer-limits.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