From: Claudio Scordino <claudio@evidence.eu.com>
To: Greg KH <gregkh@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
viro@zeniv.linux.org.uk,
Linux Kernel <linux-kernel@vger.kernel.org>,
David Rientjes <rientjes@google.com>
Subject: Re: [PATCH] drivers/base/node.c: fix compilation error
Date: Fri, 18 Nov 2011 10:53:46 +0100 [thread overview]
Message-ID: <4EC62B2A.5080606@evidence.eu.com> (raw)
In-Reply-To: <20111117175210.GE13208@suse.de>
Il 17/11/2011 18:52, Greg KH ha scritto:
> On Thu, Nov 17, 2011 at 11:08:32AM +0100, Claudio Scordino wrote:
>> Hi all,
>>
>> the current mainline kernel gives a "directives may not be used
>> inside a macro argument" error message when compiled for the
>> cris architecture.
>
> Is this because cris is using an older version of gcc, or is it due to
> something else?
Hi Greg.
The compiler I used it's still the same I used in the past (i.e., gcc 3.2.1):
/usr/local/cris/bin/cris-axis-linux-gnu-gcc -v
Reading specs from /usr/local/cris/lib/gcc-lib/cris-axis-linux-gnu/3.2.1/specs
Configured with: /home/cii/cris-dist/./gnu-toplev/configure --enable-version-specific-runtime-libs --disable-nls --target=cris-axis-linux-gnu --without-newlib --with-headers=installed --enable-languages=c,c++ --enable-shared --enable-threads=posix --prefix=/usr/local/cris
Thread model: posix
gcc version 3.2.1 Axis release R64/1.64
It's contained inside the cris-dist_1.64-1_i386.deb package. I don't
know if a newer compiler has been made available by the Axis group.
However, I never found this issue when compiling /fs/proc/meminfo.c in
the past. Therefore, I couldn't find the same error in
drivers/base/node.c either.
I suspect that /fs/proc/meminfo.c has been recently changed, and then the
same (old) compiler started complaining.
The two patches I have sent are very trivial, but allow to fix those
build problems.
Best regards,
Claudio
next prev parent reply other threads:[~2011-11-18 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 10:08 Claudio Scordino
2011-11-17 17:52 ` Greg KH
2011-11-17 21:38 ` David Rientjes
2011-11-18 9:53 ` Claudio Scordino [this message]
2011-11-17 21:34 ` David Rientjes
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=4EC62B2A.5080606@evidence.eu.com \
--to=claudio@evidence.eu.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome