Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-19
Date: Wed, 20 Nov 2013 09:43:08 +0100	[thread overview]
Message-ID: <20131120094308.3fe6ec42@skate> (raw)
In-Reply-To: <CAAXf6LUUzKXe9XiP8BdPvjBguGzAKnzkxDteggsqiFgZBvygvg@mail.gmail.com>

Dear Thomas De Schampheleire,

On Wed, 20 Nov 2013 09:02:56 +0100, Thomas De Schampheleire wrote:

> On Wed, Nov 20, 2013 at 8:30 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> [..]
> >      avr32 | sconeserver-d58f2de88c68193... | NOK | http://autobuild.buildroot.net/results/584d71f91c9a9bc115e49b77be8576cab76a8210/
> 
> Error is:
> 
> Thread.cpp: In member function 'void scx::Thread::set_priority(int)':
> Thread.cpp:117: error: 'pthread_setschedprio' was not declared in this scope
> make[3]: *** [Thread.lo] Error 1
> 
> However, sconeserver already depends on threads. It seems this
> function pthread_setchedprio has not always been available. The man
> page of my system says glibc >= 2.3.4. Could it be that the toolchain
> (uclibc-based) is too 'old'? How to handle this case: depending on the
> toolchain version the package may or may not build...

It is only implemented in the NPTL thread implementation of uClibc,
which AVR32 doesn't support. So it's another instance of
http://patchwork.ozlabs.org/patch/258723/ being needed, I believe.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2013-11-20  8:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-19 Thomas Petazzoni
2013-11-20  8:02 ` Thomas De Schampheleire
2013-11-20  8:21   ` Thomas De Schampheleire
2013-11-20  8:43   ` Thomas Petazzoni [this message]
2013-11-20  9:15     ` Thomas De Schampheleire

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=20131120094308.3fe6ec42@skate \
    --to=thomas.petazzoni@free-electrons.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