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: Tue, 15 Jul 2008 08:22:59 -0700 [thread overview]
Message-ID: <1216135379.22877.3.camel@isis> (raw)
In-Reply-To: <3972542e0807150806v67d607bbx5a43f147fa6f1c31@mail.gmail.com>
On Tue, 2008-07-15 at 10:06 -0500, E Robertson wrote:
> > 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 ?
>
> I've always used -D_GNU_SOURCE to get around the problem but "why?" is
> the question I'm trying to answer.
These are Non Posix noticed (_NP) ? thats why you need _GNU_SOURCE which
tells compiler that you want this code.
> Clearly USE_GNU is defined so the only way I can try to determine
> problem is to dig deeper.
Can you formulate the problem once again
> I must point out however that if I use I define _GNU_SOURCE just
> before the pthread.h header file is included
> I get the same result (as oppose to -D_GNU_SOURCE in the cc path).
having this define on GCC commandline is correct thing to do.
>
> I tried the -E option and it appears that all the necessary files are
> included. I don't see anything unusual.
Khem
next prev parent reply other threads:[~2008-07-15 15:23 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
2008-07-15 15:06 ` E Robertson
2008-07-15 15:22 ` Khem Raj [this message]
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=1216135379.22877.3.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.