From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] package/libabseil-cpp: depend on gcc >= 4.9
Date: Thu, 29 Oct 2020 23:36:38 +0100 [thread overview]
Message-ID: <20201029233638.78c58b98@windsurf.home> (raw)
In-Reply-To: <20201027174046.17157-3-buildroot@heine.tech>
On Tue, 27 Oct 2020 18:40:45 +0100
Michael Nosthoff via buildroot <buildroot@busybox.net> wrote:
> From: Michael Nosthoff <buildroot@heine.tech>
>
> abseil depends on gcc >= 4.9
>
> https://abseil.io/docs/cpp/platforms/platforms#linux
>
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
Is this fixing a build issue ? If so, is this issue reported in the
autobuilders ? If it's not fixing a build issue, what is the
reason/intention behind this change ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-10-29 22:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 17:40 [Buildroot] [PATCH 0/3] fix libabseil-cpp build on older gcc versions buildroot at heine.tech
2020-10-27 17:40 ` [Buildroot] [PATCH 1/3] package/libabseil-cpp: enforce C++11 buildroot at heine.tech
2020-10-29 22:36 ` Thomas Petazzoni
2020-10-30 7:44 ` Michael Nosthoff
2020-10-30 8:15 ` Thomas Petazzoni
2020-10-30 8:47 ` Michael Nosthoff
2020-10-30 9:16 ` Thomas Petazzoni
2020-10-27 17:40 ` [Buildroot] [PATCH 2/3] package/libabseil-cpp: depend on gcc >= 4.9 buildroot at heine.tech
2020-10-29 22:36 ` Thomas Petazzoni [this message]
2020-10-30 7:48 ` Michael Nosthoff
2020-10-30 8:16 ` Thomas Petazzoni
2020-10-27 17:40 ` [Buildroot] [PATCH 3/3] package/grpc: raise (host) gcc dependency to 4.9 buildroot at heine.tech
2020-10-29 22:37 ` Thomas Petazzoni
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=20201029233638.78c58b98@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