From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt5 fails to compile with gcc 6.1.0
Date: Sat, 7 May 2016 11:51:53 +0200 [thread overview]
Message-ID: <572DBAB9.3060607@gmail.com> (raw)
Same environment of the previous email. Qt5 fails with this error:
> In file included from
> /home/femtotech/dev/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/include/c++/6.1.0/bits/stl_algo.h:59:0,
> from
> /home/femtotech/dev/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/include/c++/6.1.0/algorithm:62,
> from
> ../../include/QtCore/../../src/corelib/global/qglobal.h:85,
> from ../../include/QtCore/qglobal.h:1,
> from accessible/qaccessible.h:34,
> from accessible/qaccessible.cpp:34:
> /home/femtotech/dev/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/include/c++/6.1.0/cstdlib:75:25:
> fatal error: stdlib.h: File o directory non esistente
> #include_next <stdlib.h>
which means: "file or directory not found".
stdlib.h is in sysroot/usr/include:
> /host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/stdlib.h
It seems the same behavior reported here:
https://bugs.musicpd.org/view.php?id=4524
Right now I'm rebuilding once again with an older version of gcc, hoping
this won't trigger the kernel-panic as in gcc 4.8.
next reply other threads:[~2016-05-07 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-07 9:51 Marco Trapanese [this message]
2016-05-07 11:50 ` [Buildroot] Qt5 fails to compile with gcc 6.1.0 Marco Trapanese
2016-05-07 12:01 ` Marco Trapanese
2016-05-07 12:11 ` Thomas Petazzoni
2016-05-07 12:16 ` Marco Trapanese
2016-05-07 12:28 ` Thomas Petazzoni
2016-05-07 13:02 ` Marco Trapanese
2016-05-07 19:27 ` [Buildroot] Kernel panic with glibc Marco Trapanese
2016-05-07 22:08 ` [Buildroot] Qt5 fails to compile with gcc 6.1.0 Arnout Vandecappelle
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=572DBAB9.3060607@gmail.com \
--to=marcotrapanese@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