From: "Toralf Förster" <toralf.foerster@gmx.de>
To: trinity@vger.kernel.org
Subject: 32bit compile error w/ v1.6-115-g4a302e2
Date: Sun, 20 Dec 2015 17:05:10 +0100 [thread overview]
Message-ID: <5676D1B6.3060703@gmx.de> (raw)
Happened within a 32 bit KVM of a stable gentoo:
i686-pc-linux-gnu-gcc -O2 -march=i686 -pipe -g -ggdb -Wall -W -I. -Iinclude/ -Wimplicit -D_GNU_SOURCE -D__linux__ -Wdeclaration-after-statement -Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef -Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o ioctls/nvme.o -c ioctls/nvme.c
In file included from ioctls/nvme.c:5:0:
ioctls/nvme.c:11:8: error: ‘NVME_IOCTL_IO_CMD’ undeclared here (not in a function)
IOCTL(NVME_IOCTL_IO_CMD),
^
include/ioctls.h:53:15: note: in definition of macro ‘IOCTL’
{ .request = _request, .name = #_request, }
^
i686-pc-linux-gnu-gcc -O2 -march=i686 -pipe -g -ggdb -Wall -W -I. -Iinclude/ -Wimplicit -D_GNU_SOURCE -D__linux__ -Wdeclaration-after-statement -Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef -Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o ioctls/ozwpan.o -c ioctls/ozwpan.c
ioctls/nvme.c:12:8: error: ‘NVME_IOCTL_RESET’ undeclared here (not in a function)
IOCTL(NVME_IOCTL_RESET),
^
include/ioctls.h:53:15: note: in definition of macro ‘IOCTL’
{ .request = _request, .name = #_request, }
^
Makefile:105: recipe for target 'ioctls/nvme.o' failed
make: *** [ioctls/nvme.o] Error 1
* ERROR: dev-util/trinity-9::local failed (compile phase):
* emake failed
--
Toralf, pgp: C4EACDDE 0076E94E
reply other threads:[~2015-12-20 16:05 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=5676D1B6.3060703@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=trinity@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).