From: Bob Tracy <rct@gherkin.frus.com>
To: linux-alpha@vger.kernel.org, debian-alpha@lists.debian.org
Cc: mcree@orcon.net.nz, mattst88@gmail.com
Subject: followup: [FTBFS] kernel 4.18-rc7 bitsperlong.h issue on alpha
Date: Mon, 21 Jan 2019 10:19:28 -0600 [thread overview]
Message-ID: <20190121161928.GA12984@gherkin.frus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
July 30, 2018 I reported the following to linux-kernel, linux-alpha, etc.:
On an alpha system, got the following build error on the 4.18-rc7
mainline kernel source tree:
HOSTCC net/bpfilter/main.o
In file included from tools/include/uapi/asm/bitsperlong.h:17,
from /usr/include/asm-generic/int-ll64.h:12,
from /usr/include/alpha-linux-gnu/asm/types.h:24,
from tools/include/linux/types.h:10,
from ./include/uapi/linux/bpf.h:11,
from net/bpfilter/main.c:9:
tools/include/asm-generic/bitsperlong.h:14:2: error: #error Inconsistent word size. Check asm/bitsperlong.h
#error Inconsistent word size. Check asm/bitsperlong.h
^~~~~
scripts/Makefile.host:107: recipe for target 'net/bpfilter/main.o' failed
make[2]: *** [net/bpfilter/main.o] Error 1
scripts/Makefile.build:558: recipe for target 'net/bpfilter' failed
make[1]: *** [net/bpfilter] Error 2
Makefile:1029: recipe for target 'net' failed
make: *** [net] Error 2
I implemented a crap workaround at the time in
"linux/tools/include/asm-generic/bitsperlong.h", similar to what some
frustrated person did for the x86-64 case in
"linux/include/asm-generic/bitsperlong.h". Never sent that in because I
knew it was the wrong approach.
The proper fix is attached. If needed, consider this my official
"signed off by" and/or "tested by". This applies cleanly to at least
all kernel mainline source trees from 4.18 to current.
Thanks.
--Bob
[-- Attachment #2: patch18_bitsperlong --]
[-- Type: text/plain, Size: 458 bytes --]
--- a/tools/include/uapi/asm/bitsperlong.h 2019-01-20 14:40:32.522422998 -0600
+++ b/tools/include/uapi/asm/bitsperlong.h 2019-01-21 09:51:45.336938260 -0600
@@ -13,6 +13,8 @@
#include "../../arch/mips/include/uapi/asm/bitsperlong.h"
#elif defined(__ia64__)
#include "../../arch/ia64/include/uapi/asm/bitsperlong.h"
+#elif defined(__alpha__)
+#include "../../arch/alpha/include/uapi/asm/bitsperlong.h"
#else
#include <asm-generic/bitsperlong.h>
#endif
next reply other threads:[~2019-01-21 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 16:19 Bob Tracy [this message]
2019-01-21 21:42 ` [PATCH] 4.18-rc7 on alpha: bitsperlong issue Bob Tracy
2019-01-22 7:35 ` Matt Turner
2019-01-22 9:21 ` Philippe Mathieu-Daudé
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=20190121161928.GA12984@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=linux-alpha@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
/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