From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Build failure: drivers/net/wan/wanxlfw.inc
Date: Wed, 7 Nov 2012 09:41:22 +0000 [thread overview]
Message-ID: <20121107094122.GT28327@n2100.arm.linux.org.uk> (raw)
During a randconfig build last night, the following was observed:
BLD FW drivers/net/wan/wanxlfw.inc
/bin/sh: as68k: command not found
In file included from include/linux/kernel.h:10:0,
from include/linux/skbuff.h:17,
from include/linux/hdlc.h:14,
from drivers/net/wan/wanxlfw.S:37:
include/linux/bitops.h:181:2: error: #error BITS_PER_LONG not 32 or 64
In file included from include/linux/string.h:9:0,
from include/linux/dynamic_debug.h:100,
from include/linux/kernel.h:14,
from include/linux/skbuff.h:17,
from include/linux/hdlc.h:14,
from drivers/net/wan/wanxlfw.S:37:
include/uapi/linux/string.h:7:20: fatal error: string.h: No such file or directocompilation terminated.
make[4]: *** [drivers/net/wan/wanxlfw.inc] Error 127
Obviously the lack of as68k doesn't help, but it looks like something is
broken with the includes too.
Full log and config at:
http://www.arm.linux.org.uk/developer/build/result.php?type=build&idx=2640
http://www.arm.linux.org.uk/developer/build/file.php?type=config&idx=2640
reply other threads:[~2012-11-07 9:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121107094122.GT28327@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).