From: Seth Jennings <sjennings@variantweb.net>
To: Peter Foley <pefoley2@pefoley.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: v3.18-rc5 build failure on ppc64 in Documentation/mic/mpssd/mpssd.o
Date: Wed, 19 Nov 2014 18:07:22 -0600 [thread overview]
Message-ID: <20141120000722.GA10693@cerebellum.variantweb.net> (raw)
One or more in the following commit set in the 3.18 merge window is causing
build failure on ppc64 with the default config:
7b345771ba921361b318e95bf21b257c65ac141c Documentation: update include path for mpssd
8c2b0dc83d9840da4d993a5dbb15c5974ad5a188 Documentation: support glibc versions without htole macros
6ab0e475f1f38b6be90aff4ef3ebf928c4a73dc8 Documentation: fix misc. warnings
adb19fb66eeebac07fe37d968725bb8906dadb8e Documentation: add makefiles for more targets
Building v3.18-rc5 and I have glibc 2.17.
The problem is that for big endian, the htole* macros are not simple compile
time transforms by the precompiler, but rather block code that must be executed
in function context.
Build errors:
===
HOSTCC Documentation/mic/mpssd/mpssd.o
In file included from /usr/include/bits/byteswap.h:34:0,
from /usr/include/endian.h:60,
from /usr/include/bits/waitstatus.h:64,
from /usr/include/stdlib.h:42,
from Documentation/mic/mpssd/mpssd.c:23:
Documentation/mic/mpssd/mpssd.c:93:10: error: braced-group within expression allowed only inside a function
.num = htole16(MIC_VRING_ENTRIES),
^
Documentation/mic/mpssd/mpssd.c:96:10: error: braced-group within expression allowed only inside a function
.num = htole16(MIC_VRING_ENTRIES),
^
Documentation/mic/mpssd/mpssd.c:113:10: error: braced-group within expression allowed only inside a function
.num = htole16(MIC_VRING_ENTRIES),
^
Documentation/mic/mpssd/mpssd.c:116:10: error: braced-group within expression allowed only inside a function
.num = htole16(MIC_VRING_ENTRIES),
^
Documentation/mic/mpssd/mpssd.c:119:3: error: initializer element is not constant
.host_features = htole32(
^
Documentation/mic/mpssd/mpssd.c:119:3: error: (near initialization for ‘virtnet_dev_page.host_features’)
In file included from /usr/include/bits/byteswap.h:34:0,
from /usr/include/endian.h:60,
from /usr/include/bits/waitstatus.h:64,
from /usr/include/stdlib.h:42,
from Documentation/mic/mpssd/mpssd.c:23:
Documentation/mic/mpssd/mpssd.c:146:10: error: braced-group within expression allowed only inside a function
.num = htole16(MIC_VRING_ENTRIES),
^
Documentation/mic/mpssd/mpssd.c:149:3: error: initializer element is not constant
htole32(1<<VIRTIO_BLK_F_SEG_MAX),
^
Documentation/mic/mpssd/mpssd.c:149:3: error: (near initialization for ‘virtblk_dev_page.host_features’)
Documentation/mic/mpssd/mpssd.c:151:3: error: initializer element is not constant
.seg_max = htole32(MIC_VRING_ENTRIES - 2),
^
Documentation/mic/mpssd/mpssd.c:151:3: error: (near initialization for ‘virtblk_dev_page.blk_config.seg_max’)
Documentation/mic/mpssd/mpssd.c:152:3: error: initializer element is not constant
.capacity = htole64(0),
^
Documentation/mic/mpssd/mpssd.c:152:3: error: (near initialization for ‘virtblk_dev_page.blk_config.capacity’)
make[3]: *** [Documentation/mic/mpssd/mpssd.o] Error 1
===
Reverting the commits fixes the issue, however, a more targeted approach could
just skip make on Documentation/mic/mpssd/ until the endianness issue is
resolved. Or something else...
Thanks,
Seth
next reply other threads:[~2014-11-20 0:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 0:07 Seth Jennings [this message]
2014-11-20 10:49 ` Jiri Kosina
2014-12-04 16:01 ` [PATCH] Documentation/mic/mpssd: fix compile error on BE platforms Dan Streetman
2014-12-04 21:33 ` Ashutosh Dixit
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=20141120000722.GA10693@cerebellum.variantweb.net \
--to=sjennings@variantweb.net \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pefoley2@pefoley.com \
/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