From: Ingo Molnar <mingo@elte.hu>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: [ERROR] perf build failure on current tip:perf/core
Date: Sun, 8 Jan 2012 16:00:12 +0100 [thread overview]
Message-ID: <20120108150012.GA7570@elte.hu> (raw)
In-Reply-To: <1326034208.1508.15.camel@leonhard>
* Namhyung Kim <namhyung@gmail.com> wrote:
> Putting the debug lines told me __USE_UNIX98 is not defined
> for the file. It's because ctype.h gets included without
> _GNU_SOURCE and then it includes feature.h AFAICS.
> Encompassing ctype.h with #define/#undef _GNU_SOURCE or just
> adding __USE_UNIX98 before unistd.h makes the file compiled,
> but it seems like an improper solution. What is the right way?
Could you just remove the ctype.h include? AFAICS it's not
needed in that file.
Thanks,
Ingo
next prev parent reply other threads:[~2012-01-08 15:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 15:42 [ERROR] perf build failure on current tip:perf/core Namhyung Kim
2012-01-07 17:35 ` Arnaldo Carvalho de Melo
2012-01-08 9:00 ` Ingo Molnar
2012-01-08 9:41 ` Namhyung Kim
2012-01-08 11:34 ` Ingo Molnar
2012-01-08 12:30 ` Namhyung Kim
2012-01-08 14:03 ` Ingo Molnar
2012-01-08 14:50 ` Namhyung Kim
2012-01-08 15:00 ` Ingo Molnar [this message]
2012-01-08 15:10 ` [PATCH] perf tools: Fix compile error on x86_64 Ubuntu Namhyung Kim
2012-01-08 15:12 ` Arnaldo Carvalho de Melo
2012-01-08 15:32 ` Ingo Molnar
2012-01-08 15:49 ` Namhyung Kim
2012-01-09 7:29 ` [tip:perf/core] " tip-bot for Namhyung Kim
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=20120108150012.GA7570@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.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.