From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results
Date: Sun, 23 Feb 2020 00:48:38 +0100 [thread overview]
Message-ID: <93002ccc-73ca-d4ff-81d9-bf524a16840a@gmail.com> (raw)
In-Reply-To: <20200220034343.2370e4e4@windsurf>
Hello,
Le 20/02/2020 ? 03:43, Thomas Petazzoni a ?crit?:
> Hello,
>
> On Wed, 19 Feb 2020 07:48:39 -0000
> Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
>
>> master | 92 | 67 | 0 | 159 |
>
> These results are not really good, so we need to put some effort into
> reducing the number of build failures in the autobuilders. See below
> for an analysis of the different build failures. Your help is
> appreciated to fix those issues.
>
>
>> arm | efl-1.22.3 | NOK | http://autobuild.buildroot.net/results/4d7861fd5908c59546de19f6af3c27d061fed60b |
>
> /data/buildroot/buildroot-test/instance-0/output/host/bin/../arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/poppler/cpp/poppler-page.h:39:22: error: expected ',' or '...' before '&&' token
>
> Some C++ mess it seems. Romain, any idea ?
This is an issue related to poppler dependency that is built with C++11 standard:
sysroot/usr/include/poppler/cpp/poppler-page.h:70:10:
"error: 'unique_ptr' in namespace 'std' does not name a template type"
But with this toolchain based on gcc-5, the default C++ standard is gnu++98 [2].
The efl libraries should be built with -std=c++11 in CFLAGS (see [1] for similar
issue).
Or maybe we should bump the poppler's package gcc dependency (gcc 5 to gcc 6)
[3]. Doing so, the C++ standard for poppler and efl are the same (C++14).
Otherwise, I don't see how the efl package can know the C++ standard to use.
[1]
https://git.buildroot.net/buildroot/commit/?id=995fb9a4ebca3acb5dc6eb22edee039b67bf5303
[2] https://gcc.gnu.org/gcc-6/changes.html
[3]
https://git.buildroot.net/buildroot/tree/package/poppler/Config.in?h=2020.02-rc1#n7
Best regards,
Romain
> Thomas
>
next prev parent reply other threads:[~2020-02-22 23:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 7:48 [Buildroot] [autobuild.buildroot.net] Daily results for 2020-02-18 Thomas Petazzoni
[not found] ` <20200220034343.2370e4e4@windsurf>
2020-02-20 13:36 ` [Buildroot] Analysis of build results Giulio Benetti
2020-02-21 8:23 ` Romain Naour
[not found] ` <94c8edad-773d-2b36-5daf-b6ee60dd747f@micronovasrl.com>
[not found] ` <3e7b016b-eca6-b768-3fca-8fd7e44d0299@micronovasrl.com>
[not found] ` <20200220190807.505b4fb2@windsurf>
[not found] ` <00751b5d-ca05-fe42-0e9b-6a1005a09e6d@micronovasrl.com>
[not found] ` <20200220192344.03785f04@windsurf>
[not found] ` <bcc10a0e-c54e-5b75-9b77-8922b85a925a@micronovasrl.com>
[not found] ` <fe7d07df-71a0-e317-6b91-ade479545ec4@smile.fr>
[not found] ` <28258465-4f79-3f47-189d-bb066b0aa9f7@micronovasrl.com>
2020-02-22 19:10 ` Romain Naour
2020-02-22 19:44 ` Giulio Benetti
2020-02-22 21:11 ` Fabrice Fontaine
2020-02-22 21:48 ` Giulio Benetti
2020-02-22 22:00 ` Fabrice Fontaine
2020-02-22 23:48 ` Romain Naour [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-27 9:31 [Buildroot] [autobuild.buildroot.net] Daily results for 2020-02-26 Thomas Petazzoni
2020-02-27 22:49 ` [Buildroot] Analysis of build results Thomas Petazzoni
2020-02-27 23:06 ` Max Filippov
2020-02-27 23:18 ` Giulio Benetti
2020-02-28 8:03 ` Thomas Petazzoni
2020-02-28 18:06 ` Giulio Benetti
2020-02-28 6:21 ` Heiko Thiery
2020-02-28 7:56 ` Sergio Prado
2020-02-28 8:01 ` Thomas Petazzoni
2020-02-28 7:32 ` Romain Naour
2020-02-28 15:02 ` Peter Seiderer
2020-02-29 21:15 ` Romain Naour
2020-02-29 23:17 ` Peter Seiderer
2014-11-11 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-10 Thomas Petazzoni
2014-11-11 22:49 ` [Buildroot] Analysis of build results Thomas Petazzoni
2014-11-11 23:41 ` Gustavo Zacarias
2014-11-12 2:30 ` Nathaniel Roach
2014-11-12 14:09 ` Jörg Krause
2014-11-16 10:07 ` Yann E. MORIN
2014-11-22 11:10 ` Bernd Kuhls
2014-08-30 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-08-29 Thomas Petazzoni
2014-08-30 9:07 ` [Buildroot] Analysis of build results Thomas Petazzoni
2014-08-25 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-08-24 Thomas Petazzoni
2014-08-25 16:16 ` [Buildroot] Analysis of build results Thomas Petazzoni
2014-08-25 16:26 ` Phil Eichinger
2014-08-25 17:47 ` Thomas Petazzoni
2014-08-25 21:07 ` Peter Korsgaard
2014-08-25 21:13 ` Jörg Krause
2014-08-26 6:17 ` Alexander Lukichev
2014-08-28 12:52 ` Ezequiel Garcia
2014-08-31 16:58 ` Frank Bergmann
2014-08-31 21:13 ` Ezequiel Garcia
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=93002ccc-73ca-d4ff-81d9-bf524a16840a@gmail.com \
--to=romain.naour@gmail.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