From: Paul Jackson <pj@sgi.com>
To: Clemens Schwaighofer <schwaigl@eunet.at>
Cc: gullevek@gullevek.org, linux-kernel@vger.kernel.org, cs@tequila.co.jp
Subject: Re: compile error with 2.6.7-rc3-mm1
Date: Sat, 12 Jun 2004 03:44:30 -0700 [thread overview]
Message-ID: <20040612034430.72a8207e.pj@sgi.com> (raw)
In-Reply-To: <40CA6835.2070405@eunet.at>
> nono, that part is already fixed in my patch (from mm-1).
But the error you report:
drivers/perfctr/x86.c: In function `finalise_backpatching':
drivers/perfctr/x86.c:1137: error: parse error before '{' token
is _exactly_ the error you reported before, and it occurs on a line that
assigns CPU_MASK_NONE (via a #define of perfctr_cpus_forbidden_mask) to
a local variable, and this is exactly the error one gets when assigning
the broken version of CPU_MASK_NONE, which was missing the (cpumask_t)
cast, to a local variable.
Somehow, something you are reporting is incorrect. Or else I am more
mistaken than I am accustomed to being.
Please verify that the above error is indeed the one you are seeing,
and that doing the following command in this build tree:
grep -1 define.CPU_MASK_NONE include/linux/cpumask.h
produces the following output, including the (cpumask_t) cast:
#define CPU_MASK_NONE \
((cpumask_t){ { \
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-06-12 10:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 13:10 compile error with 2.6.7-rc3-mm1 Clemens Schwaighofer
2004-06-11 13:28 ` Paul Jackson
2004-06-12 2:19 ` Clemens Schwaighofer
2004-06-12 10:44 ` Paul Jackson [this message]
2004-06-13 3:20 ` Clemens Schwaighofer
2004-06-13 3:42 ` Paul Jackson
2004-06-13 4:04 ` Clemens Schwaighofer
2004-06-13 4:20 ` Paul Jackson
2004-06-13 6:22 ` Clemens Schwaighofer
2004-06-13 6:39 ` Paul Jackson
2004-06-13 6:45 ` Paul Jackson
2004-06-13 6:08 ` Sam Ravnborg
2004-06-13 6:03 ` Paul Jackson
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=20040612034430.72a8207e.pj@sgi.com \
--to=pj@sgi.com \
--cc=cs@tequila.co.jp \
--cc=gullevek@gullevek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwaigl@eunet.at \
/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