public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH] package/bctoolbox: disable mbedtls support
Date: Fri, 29 Aug 2025 23:55:11 +0200	[thread overview]
Message-ID: <20250829235511.1fd98d89@windsurf> (raw)
In-Reply-To: <20250710081059.482390-1-thomas.perale@mind.be>

Hello Thomas,

On Thu, 10 Jul 2025 10:10:58 +0200
Thomas Perale via buildroot <buildroot@buildroot.org> wrote:

> They did add support for mbedtls 3.6 in commit [1]. I would prefer to not
> deprecate it on the LTS branch so I tried to bump to the latest version but I
> get the following error linked to mbedtls:
> 
> crypto/mbedtls.cc: In constructor ‘bctoolbox::{anonymous}::mbedtlsStaticContexts::mbedtlsStaticContexts()’:
> crypto/mbedtls.cc:83:17: error: ‘mbedtls_threading_set_alt’ was not declared in this scope; did you mean ‘mbedtls_threading_mutex_t’?
>    83 |                 mbedtls_threading_set_alt(threading_mutex_init_cpp, threading_mutex_free_cpp, threading_mutex_lock_cpp,
>       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~
>       |                 mbedtls_threading_mutex_t
> crypto/mbedtls.cc: In destructor ‘bctoolbox::{anonymous}::mbedtlsStaticContexts::~mbedtlsStaticContexts()’:
> crypto/mbedtls.cc:95:17: error: ‘mbedtls_threading_free_alt’ was not declared in this scope; did you mean ‘mbedtls_threading_mutex_t’?
>    95 |                 mbedtls_threading_free_alt();
>       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~
>       |                 mbedtls_threading_mutex_t
> 
> If anyone could look into this, I would appreciate it. I tried to change the
> mbedtls_config.h to enable the ALT threading function but without success.

Nobody stepped up to fix this issue, so I suggest that we apply my
patch disabling MbedTLS support in bctoolbox for the time being. If
someone, one day, needs MbedTLS support in bctoolbox, that someone can
always fix it up.

I'm personally not interested in bctoolbox/C++/MbedTLS debugging, so I
won't investigate this build issue.

Best regards,

Thomas
-- 
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

  parent reply	other threads:[~2025-08-29 21:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 21:16 [Buildroot] [PATCH] package/bctoolbox: disable mbedtls support Thomas Petazzoni via buildroot
2025-07-10  8:10 ` Thomas Perale via buildroot
2025-07-10  8:28   ` Thomas Petazzoni via buildroot
2025-08-29 21:55   ` Thomas Petazzoni via buildroot [this message]
2025-08-29 21:59     ` Thomas Petazzoni via buildroot
2025-08-30  7:16       ` Thomas Perale 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=20250829235511.1fd98d89@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.perale@mind.be \
    --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