Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Michael Nosthoff via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/boost: bump to version 1.80.0
Date: Thu, 11 Aug 2022 22:24:01 +0200	[thread overview]
Message-ID: <20220811222401.0163576a@windsurf> (raw)
In-Reply-To: <20220811095221.1226557-1-buildroot@heine.tech>

Hello Michael,

On Thu, 11 Aug 2022 11:52:22 +0200
Michael Nosthoff via buildroot <buildroot@buildroot.org> wrote:

> - drop upstreamed patches
> 
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>

How many reverse dependencies of boost did you build with this new
version? Major Boost versions tend to break stuff :-/

Also, are there new Boost modules/libs that would require new options
in package/boost/Config.in? By default, Boost enables all its
modules/libs by default, so if we don't handle them explicitly, to be
able to add them to the BOOST_WITHOUT_FLAGS variable of boost.mk, those
new modules/libs will be enabled by default. Apparently
https://www.boost.org/users/history/version_1_80_0.html, seems to say
"No new libraries.".

Thanks!

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

  reply	other threads:[~2022-08-11 20:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11  9:52 [Buildroot] [PATCH] package/boost: bump to version 1.80.0 Michael Nosthoff via buildroot
2022-08-11 20:24 ` Thomas Petazzoni via buildroot [this message]
2022-08-15 20:22 ` Thomas Petazzoni 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=20220811222401.0163576a@windsurf \
    --to=buildroot@buildroot.org \
    --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