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 2014-06-10
Date: Wed, 11 Jun 2014 13:52:30 +0200	[thread overview]
Message-ID: <20140611135230.6b1d487f@free-electrons.com> (raw)
In-Reply-To: <CANQCQpaiwOhYMyXoQ_7bcHNGApKnVWOmHrxGzzjPHq5P1GSx2w@mail.gmail.com>

Dear Matthew Weber,

On Wed, 11 Jun 2014 06:49:15 -0500, Matthew Weber wrote:

> >       bfin |                  omniorb-4.1.6 | NOK | http://autobuild.buildroot.net/results/de5cdae456d83b0a1ac86cfcddf0c973c2304009/
> 
> posix.cc: In member function 'void omni_thread::start()':
> posix.cc:603:2: error: invalid conversion from 'pthread_t*' to 'pthread_t'
> posix.cc:603:2: error:   initializing argument 1 of 'int
> pthread_detach(pthread_t)'
> posix.cc: In static member function 'static omni_thread* omni_thread::self()':
> posix.cc:800:5: error: too many arguments to function 'void*
> pthread_getspecific(pthread_key_t)'
> 
> This looks like a blackfin uclinux(uclibc) pthread issue, since I have
> tested this with uclibc successfully.  I'm not to familiar with the
> blackfin's uclinux posix implementation completeness and didn't find
> any open bug reports on this package.  So I'll take a look at this and
> see if the best option is to limit the package to not build for
> blackfin or to fix the problem and submit a path to the omni
> maintainers (they are currently not actively taking updates/patches,
> so I would probably go with the first option).

This might also be a NPTL vs. linuxthreads issue.

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

      reply	other threads:[~2014-06-11 11:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-06-10 Thomas Petazzoni
2014-06-11 11:49 ` Matthew Weber
2014-06-11 11:52   ` Thomas Petazzoni [this message]

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=20140611135230.6b1d487f@free-electrons.com \
    --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