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 20:42:07 -0700 [thread overview]
Message-ID: <20040612204207.0136b76f.pj@sgi.com> (raw)
In-Reply-To: <40CBC809.3000102@eunet.at>
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.
--
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 3:43 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 [this message]
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=20040612204207.0136b76f.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 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.