Thread (39 messages) 39 messages, 7 authors, 2016-07-25

Re: linux-next: build failure after merge of the luto-misc tree

From: Peter Zijlstra <peterz@infradead.org>
Date: 2016-07-15 07:31:30
Also in: lkml

On Fri, Jul 15, 2016 at 09:22:43AM +0200, Peter Zijlstra wrote:
On Fri, Jul 15, 2016 at 05:06:54PM +1000, Stephen Rothwell wrote:
quoted
interacting with commit

  2a00f026a15d ("tools: Fix up BITS_PER_LONG setting")

from the tip tree.
Yuck.. that thing is horrid :/

What's wrong with so?

And if you really want to retain CONFIG_64BIT (because other headers
might want it, and they currently do not) then do something like:

#ifdef __LP64__
#define CONFIG_64BIT
#else
#define CONFIG_32BIT
#endif

All GCC versions I checked have __CHAR_BIT__ and __SIZEOF_LONG__.

(and I checked most everything from 4.4 - 6.1)
clang-3.8 also defines all three of those, and I don't consider that a
usable compiler as it doesn't even build a kernel.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help