Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/empty - fix build failure
Date: Thu, 6 Aug 2015 20:59:56 +0200	[thread overview]
Message-ID: <20150806185956.GK8475@waldemar-brodkorb.de> (raw)
In-Reply-To: <1438703581-25996-1-git-send-email-brendanheading@gmail.com>

Hi Brendan,
Brendan Heading wrote,

> Fixes http://autobuild.buildroot.net/results/e07/e07aec9a839e89b7452b13bf5445164530e27414/
> 
> "empty" fails to build if _POSIX_SEMAPHORES is not defined, which is the
> case on a toolchain with no threading support.

Threads are not required for SysV semaphores. I have sent a patch
fixing the build with a toolchain without threads, but I got no
response on that.

http://patchwork.ozlabs.org/patch/493343/

best regards
 Waldemar

  reply	other threads:[~2015-08-06 18:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 15:53 [Buildroot] [PATCH 1/1] package/empty - fix build failure Brendan Heading
2015-08-06 18:59 ` Waldemar Brodkorb [this message]
2015-08-06 19:51   ` Brendan Heading

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=20150806185956.GK8475@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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