From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/capnproto: bump version to 1.8.0
Date: Sat, 9 May 2020 23:19:26 +0200 [thread overview]
Message-ID: <20200509231926.543cdf35@windsurf.home> (raw)
In-Reply-To: <20200503063730.GA1839@coltrane>
On Sun, 3 May 2020 08:37:30 +0200
Koen Martens <gmc@sonologic.nl> wrote:
> The new version requires two extra features in the
> toolchain, therefore two new toolchain options are
> added as dependencies:
>
> * BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS
Could you give more details about this new dependency? Which build
failure did you encounter, and with which toolchain/configuration?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-05-09 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 6:37 [Buildroot] [PATCH 1/1] package/capnproto: bump version to 1.8.0 Koen Martens
2020-05-09 21:19 ` Thomas Petazzoni [this message]
2020-05-10 10:32 ` Koen Martens
2020-05-10 12:10 ` Thomas Petazzoni
2020-05-16 7:52 ` Koen Martens
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=20200509231926.543cdf35@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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