From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Andreas Ziegler <br015@umbiko.net>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] RFC: package/boost: build failure
Date: Mon, 7 Nov 2022 09:24:55 +0100 [thread overview]
Message-ID: <20221107092455.3e4c972e@windsurf> (raw)
In-Reply-To: <a68289a542b9c7e28e8486e4b8b58070@umbiko.net>
On Mon, 07 Nov 2022 06:38:43 +0000
Andreas Ziegler <br015@umbiko.net> wrote:
> The development branch of boost/intrusive contains a fix for this
> failure which, unfortunately, is rather longish [2]. Easy extraction of
> the relevant part of the patch is not possible, due to massive changes
> to the whole code.
>
> I can think of three options to deal with this issue:
>
> (1) Use the commit [2] as is, even if it changes more than the failing
> code
To me the commit [2] is not that large, and would be OK to backport as
an interim solution until 1.81 is released.
Thanks a lot for this investigation work, much appreciated!
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
prev parent reply other threads:[~2022-11-07 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 6:38 [Buildroot] RFC: package/boost: build failure Andreas Ziegler
2022-11-07 8:24 ` 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=20221107092455.3e4c972e@windsurf \
--to=buildroot@buildroot.org \
--cc=br015@umbiko.net \
--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