All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: Strange header file error
Date: Mon, 14 Jul 2008 19:06:11 -0700	[thread overview]
Message-ID: <1216087571.10214.10.camel@isis> (raw)
In-Reply-To: <3972542e0807141258i256cab38kb2023270a0aa14e9@mail.gmail.com>



On Mon, 2008-07-14 at 14:58 -0500, E Robertson wrote:
> Hi All,
> I'm trying to explain this pthread.h header file error.
> I include this header file in my program. The snip of interest is this:
> 
> #ifndef _PTHREAD_H
> #define _PTHREAD_H  1
> 
> #include <features.h>
> 
> #include <sched.h>
> #include <time.h>
> 
> #define __need_sigset_t
> #include <signal.h>
> #include <bits/pthreadtypes.h>
> #include <bits/initspin.h>
> 
> __BEGIN_DECLS
> 
> /* Initializers.  */
> 
> #define PTHREAD_MUTEX_INITIALIZER \
>   {0, 0, 0, PTHREAD_MUTEX_ADAPTIVE_NP, __LOCK_INITIALIZER}
> #ifdef __USE_GNU
> # define PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP \
>   {0, 0, 0, PTHREAD_MUTEX_RECURSIVE_NP, __LOCK_INITIALIZER}
> # define PTHREAD_ERRORCHECK_MUTEX_INITIALIZER_NP \
>   {0, 0, 0, PTHREAD_MUTEX_ERRORCHECK_NP, __LOCK_INITIALIZER}
> # define PTHREAD_ADAPTIVE_MUTEX_INITIALIZER_NP \
>   {0, 0, 0, PTHREAD_MUTEX_ADAPTIVE_NP, __LOCK_INITIALIZER}
> #endif
> 
> 
> This is included in another header file where I place some #ifdef
> statements for  _PTHREAD_H,
> PTHREAD_MUTEX_INITIALIZER, PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP, and
> __USE_GNU.
> I also defined __USE_GNU just before the header file and none of these
> are redefined anywhere else.
> 
> >From this I notice all these defines are valid and present _except_
> PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP.
> I haven't figured out why this is so wired I don't see any possible
> reason how this could be possible.
> Am I out of my mind here? Is this really possible? Unless my
> arm-uclibc is doing something strange, I don't see how this could be.
> Anyone seen this before?  Thanks much.
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




Its not clear from your email what you might be facing. You can
preprocess your source file with -E and see whats getting included

what happens when you use  -D_GNU_SOURCE ?

Thx

-Khem




  reply	other threads:[~2008-07-15  2:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 19:58 Strange header file error E Robertson
2008-07-15  2:06 ` Khem Raj [this message]
2008-07-15 15:06   ` E Robertson
2008-07-15 15:22     ` Khem Raj
2008-07-15 16:08       ` E Robertson

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=1216087571.10214.10.camel@isis \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /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.