From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-06-05
Date: Tue, 06 Jun 2017 21:16:31 +0200 [thread overview]
Message-ID: <1496776591.3962.3.camel@embedded.rocks> (raw)
In-Reply-To: <20170606063119.BBACB21D14@mail.free-electrons.com>
On Tue, 2017-06-06 at 08:31 +0200, Thomas Petazzoni wrote:
> Hello,
Build statistics for 2017-06-05
================================
powerpc | libupnpp-0.15.2 | NOK | http://autobuild.buildroot.net/results/0bf84f61a72a65a75c5fd0a787680f483cfead26 |
powerpc | libupnpp-0.15.2 | NOK | http://autobuild.buildroot.net/results/2569d7b5049d0bd1da8316d8ac5997d4e68c08ae |
powerpc | libupnpp-0.15.2 | NOK | http://autobuild.buildroot.net/results/ff512f5532011a513b5551428152e600b04a007d |
"""
error: 'yield' is not a member of 'std::this_thread'
"""
Before version 0.15.2 libupnpp used sched_yield() which was replaced by
std::this_thread::yield(). Looking at the thread header file for the
PowerPC toolchain shows that yield() is only enabled if
`_GLIBCXX_USE_SCHED_YIELD` is defined. This macro is only defined if
GCC was built with `--enable-libstdcxx-time`. For GCC 4.7 and below
this option defaults to no, which means sched_yield() is not enabled
though it is available.
"""
#ifdef _GLIBCXX_USE_SCHED_YIELD
/// yield
inline void
yield() noexcept
{ __gthread_yield(); }
#endif
"""
"""
static inline int
__gthread_yield (void)
{
return __gthrw_(sched_yield) ();
}
"""
This issue was discussed on stackoverflow [1]. The issue is resolved in
GCC 4.9 which automatically enables sched_yield() on platforms that are
known to support them.
Therefore, I would suggest to add a dependency on GCC 4.9 for this
package.
[1] https://stackoverflow.com/a/12961816
Best regards,
J?rg Krause
next prev parent reply other threads:[~2017-06-06 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 6:31 [Buildroot] [autobuild.buildroot.net] Build results for 2017-06-05 Thomas Petazzoni
2017-06-06 19:16 ` Jörg Krause [this message]
2017-06-06 20:20 ` Peter Korsgaard
2017-06-07 7:08 ` Jörg Krause
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=1496776591.3962.3.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.