Re: [Buildroot] [PATCH 23/29 v2] package/boost: bump to version 1.87.0

From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Michael Nosthoff <buildroot@heine.tech>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 23/29 v2] package/boost: bump to version 1.87.0
Date: Tue, 15 Apr 2025 21:46:57 +0200	[thread overview]
Message-ID: <Z_63sTGxwXvJJhEp@landeda> (raw)
In-Reply-To: <56bc8-67fe2d80-1-26168cc0@111660538>

Michael, All,

On 2025-04-15 11:56 +0200, Michael Nosthoff spake thusly:
> On Wednesday, April 09, 2025 22:03 CEST, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> Great that you took the time to clean up the boost package and bump it.

And just right after I sent the series, they released boost 1.88.0!

I guess I'll have to eat my own dog food to prove that my cleanups and
rework do indeed make it easier to bump. ;-]

> I had the bumping on my list for some time now but didn't manage to
> finish it due to the many C++03 deprecations in the last releases.
> I discovered some issues with some boost internal dependencies.
> Especially troublesome was using a gcc < 6.0 where C++11 is not
> set as default mode and the package pulling in the header dependency
> that required C++11 wasn't setting C++11 mode.
> 
> As I don't see any new BR2_TOOLCHAIN_GCC_AT_LEAST_* lines in the
> patch I assume you didn't look at this?

Indeed I did not.

I first wanted to make it easier to test boost, but this package is just
insane.

Currently, to update the dependencies of libraries is very difficult,
especially to drop no-longer needed dependencies. For example, since
1.72.0, contract no longer needs system. With the current Config.in,
this is totally impossible to detect, so much so that it has lingered in
Buildroot up until now.

To properly detect that, we need to manually edit the Config.in, remove
all dependencies, and build (configure is enough) libs one by one until
one breaks, at which point we can add the required dependencies, and so
on and so forth until all libs are covered. Given the amount of libs in
1.87 and beyond, this is just an insane work...

And when we have a solution for that problem, then it becomes easier to
pass boost through the ./utils/test-pkg harness, to test-build libs one
by one to check whether they get new toolchain dependencies...

> Here my list of packages that now require a newer C++ version (taken
> from the release notes):
[--SNIP--]

Thanks, that's very useful information! I'll have a look at 1.88.0 to
update that list...

Thanks for the feedback! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot