linux-kernel - Re: [PATCH] drivers/base/node.c: fix compilation error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4EC62B2A.5080606@evidence.eu.com>
Date:	Fri, 18 Nov 2011 10:53:46 +0100
From:	Claudio Scordino <claudio@...dence.eu.com>
To:	Greg KH <gregkh@...e.de>
CC:	Andrew Morton <akpm@...ux-foundation.org>, viro@...iv.linux.org.uk,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	David Rientjes <rientjes@...gle.com>
Subject: Re: [PATCH] drivers/base/node.c: fix compilation error

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/