From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/drogon: fix optional TLS dependency
Date: Tue, 27 Oct 2026 17:26:35 +0100 [thread overview]
Message-ID: <auDQqsk_xf6qlrXo@windsurf> (raw)
In-Reply-To: <20261027144159.1097876-1-dario.binacchi@amarulasolutions.com>
On Tue, Oct 27, 2026 at 03:41:57PM +0100, Dario Binacchi wrote:
> The trantor library bundled in drogon looks for a TLS library at
> configure time, and uses OpenSSL or Botan if it finds one. Since
> drogon.mk does not declare any dependency on them, TLS support ends up
> depending on whether OpenSSL or Botan happens to be built before
> drogon.
>
> Select the TLS library explicitly, following the same order as trantor,
> so that OpenSSL is preferred over Botan.
>
> host-drogon only provides drogon_ctl, which does not need TLS, so
> disable it there to avoid picking up the TLS libraries of the build
> machine.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Applied to master after adding a Fixes: tag pointing to the commit
that added the drogon package. Thanks!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-27 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 14:41 [Buildroot] [PATCH 1/2] package/drogon: fix optional TLS dependency Dario Binacchi
2026-10-27 14:41 ` [Buildroot] [PATCH 2/2] package/drogon: fix build with LibreSSL Dario Binacchi
2026-10-27 16:27 ` Thomas Petazzoni via buildroot
2026-10-29 9:58 ` Dario Binacchi
2026-10-29 12:18 ` Thomas Petazzoni via buildroot
2026-10-27 16:26 ` Thomas Petazzoni via buildroot [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=auDQqsk_xf6qlrXo@windsurf \
--to=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.com \
/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