public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Daniel Lehne <daniel.lehne@amk-drives.bg>
Cc: crossgcc@sourceware.org
Subject: Re: OSELAS.Toolchain-2011.03.0: PTHREAD_PRIO_INHERIT undeclared for arm-1136jfs-linux-gcc
Date: Thu, 05 Jan 2012 18:08:00 -0000	[thread overview]
Message-ID: <CAMKF1soDbWBr+R1puopk3zU1aOtVQgCBWtvXNPUKXbJHLnXfyg@mail.gmail.com> (raw)
In-Reply-To: <4F0543B5.5010306@amk-drives.bg>

On Wed, Jan 4, 2012 at 10:31 PM, Daniel Lehne
<daniel.lehne@amk-drives.bg> wrote:
> On 04.1.2012 г. 20:06, Khem Raj wrote:
>>
>> On (04/01/12 13:34), Daniel Lehne wrote:
>>>
>>> Hello,
>>>
>>> Why this protocol is only for __USE_UNIX98 allowed? Is there a
>>> solution to use this protocol PTHREAD_PRIO_INHERIT  with gcc?
>>
>> add #define _GNU_SOURCE
>> at the top of your source file.
>>
>>
> I've tried it already __GNU_SOURCE don't works because of _XOPEN_SOURCE =
> 600. I don't want to make changes in features.h. May i will set __USE_UNIX98
> directly in source before the usage of phtread.h. Your answer shows me, this
> PTHREAD_PRIO_INHERIT should be available also for c source (gcc).
>

take your source add
#define _GNU_SOURCE to it on top
or add it on cmdline like below

-D_GNU_SOURCE

is that too hard ?

> Thanks!
>

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2012-01-05 18:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 11:34 Daniel Lehne
2012-01-04 18:06 ` Khem Raj
2012-01-05  6:31   ` Daniel Lehne
2012-01-05 18:08     ` Khem Raj [this message]
2012-01-06  6:24       ` Daniel Lehne

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=CAMKF1soDbWBr+R1puopk3zU1aOtVQgCBWtvXNPUKXbJHLnXfyg@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=daniel.lehne@amk-drives.bg \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).