public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Schwaighofer <schwaigl@eunet.at>
To: Paul Jackson <pj@sgi.com>
Cc: gullevek@gullevek.org, linux-kernel@vger.kernel.org, cs@tequila.co.jp
Subject: Re: compile error with 2.6.7-rc3-mm1
Date: Sun, 13 Jun 2004 13:04:33 +0900	[thread overview]
Message-ID: <40CBD251.4000601@eunet.at> (raw)
In-Reply-To: <20040612204207.0136b76f.pj@sgi.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Jackson wrote:

| Try doing the make with V=1
|
|   make V=1 drivers/perfctr/x86.o
|
| Determine the exact compilation line (perhaps a couple hundred chars
| long) that issues the error, then manually repeat that line manually
| (cut+paste), adding the option "-save-temps".
|
| This will look something similar to the following, which I generated for
| a different file, different compilation environment (I added the wrapping
| and backslashes for display purposes here):
|
|     gcc -save-temps -Wp,-MD,kernel/.cpuset.o.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=cpuset -DKBUILD_MODNAME=cpuset -c -o
kernel/cpuset.o \
|     kernel/cpuset.c
|
| Then look at the ./x86.i file (in top directory), which is the
| preprocessor output, to see if the (cpumask_t) cast is present.
|

yeah I have the cputmask_t here:

typedef struct { unsigned long bits[(((1)+32 -1)/32)]; } cpumask_t;
extern cpumask_t _unused_cpumask_arg_;

...
a lot of static .. cpu_set, call, etc
...
# 259 "include/linux/cpumask.h"
...
2 more cpumask_ ...
...
# 338 "include/linux/cpumask.h"
extern cpumask_t cpu_possible_map;
extern cpumask_t cpu_online_map;
extern cpumask_t cpu_present_map;

lg, clemens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAy9JRJwwYX0IeBp8RAhV4AJ9HZdmP06+8xZYVqoYb8gGPzsfcOACcCoW5
/OEinuTlAEFiyTzXKyBmm6I=
=XgdM
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-06-13  4:02 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 [this message]
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=40CBD251.4000601@eunet.at \
    --to=schwaigl@eunet.at \
    --cc=cs@tequila.co.jp \
    --cc=gullevek@gullevek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    /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