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 23:39:37 -0700 [thread overview]
Message-ID: <20040612233937.4367e7fe.pj@sgi.com> (raw)
In-Reply-To: <40CBF29D.3080400@eunet.at>
> okay, I have the "Bad" one. Whatever that means, it seems bad :)
Ok - that's progress.
Then whatever cpumask.h file you are using to compile that code does not
have the fix you think it has.
If you're still stuck, send the output of doing the four commands:
rm -f drivers/perfctr/x86.i
make V=1 drivers/perfctr/x86.i | fmt -s
grep -2 define.CPU_MASK_NONE include/linux/cpumask.h
grep -2 old_mask.= drivers/perfctr/x86.i
By way of example, when I do these four commands, I get:
$ rm -f drivers/perfctr/x86.i
$ make V=1 drivers/perfctr/x86.i | fmt -s
make -f scripts/Makefile.build obj=scripts/basic
make -f scripts/Makefile.build obj=scripts
make -f scripts/Makefile.build obj=drivers/perfctr drivers/perfctr/x86.i
gcc -E -Wp,-MD,drivers/perfctr/.x86.i.d -nostdinc -iwithprefix
include -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes
-Wno-trigraphs -fno-strict-aliasing -fno-common -pipe
-msoft-float -mpreferred-stack-boundary=2 -march=pentium4
-mregparm=3 -Iinclude/asm-i386/mach-default -O2 -fomit-frame-pointer
-DKBUILD_BASENAME=x86 -DKBUILD_MODNAME=x86 -o drivers/perfctr/x86.i
drivers/perfctr/x86.c
$ grep -2 define.CPU_MASK_NONE include/linux/cpumask.h
#endif
#define CPU_MASK_NONE \
((cpumask_t){ { \
[0 ... BITS_TO_LONGS(NR_CPUS)-1] = 0UL \
$ grep -2 old_mask.= drivers/perfctr/x86.i
cpumask_t old_mask;
old_mask = ((cpumask_t){ { [0 ... (((8)+32 -1)/32)-1] = 0UL } });
clear_perfctr_cpus_forbidden_mask();
--
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-13 6:40 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
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 [this message]
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=20040612233937.4367e7fe.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