From: keith.busch@intel.com (Keith Busch)
Subject: NVME User Installation
Date: Mon, 21 Jul 2014 15:33:19 -0600 (MDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1407211024060.4703@AMR> (raw)
In-Reply-To: <8838223D960CB945AFF93D316204C6369EB844@CFWEX01.americas.cray.com>
I just tired a SLES11 SP3 install and copied the nvme user api header
from the nvme-compatibility repo's 'include/uapi/linux/nvme.h' to
'/usr/include/linux/', and was able to build the user tools without error.
I'm not sure what else could be different between our two setups that
is causing the errors you're seeing.
On Mon, 21 Jul 2014, Ian Ziemba wrote:
> Hi Keith,
>
> I copied over /uapi/linux/nvme.h into the correct location. The system does
> not seem to have any issues finding it. But, I ran into something else right
> now. Here is the printout from my screen:
>
> iosr30-5:~/iziemba/nvme-user # make
> cc -m64 -O2 -g -pthread -D_GNU_SOURCE -D_REENTRANT -W -m64 -lm nvme_smart.c nvme_identify.o -o nvme_smart
> In file included from /usr/src/linux-3.0.76-0.11/include/linux/nvme.h:22,
> from nvme_smart.c:1:
> /usr/src/linux-3.0.76-0.11/include/linux/types.h:13:2: warning: #warning "Attempt to use kernel headers from user space, see http://kernelnewbies.org/KernelHeaders"
> nvme_smart.c:24: warning: 'struct nvme_smart_log' declared inside parameter list
> nvme_smart.c:24: warning: its scope is only this definition or declaration, which is probably not what you want
> nvme_smart.c: In function 'print_smart_log':
> nvme_smart.c:27: error: dereferencing pointer to incomplete type
> nvme_smart.c:28: error: dereferencing pointer to incomplete type
> nvme_smart.c:30: error: dereferencing pointer to incomplete type
> nvme_smart.c:32: error: dereferencing pointer to incomplete type
> nvme_smart.c:33: error: dereferencing pointer to incomplete type
> nvme_smart.c:34: error: dereferencing pointer to incomplete type
> nvme_smart.c:37: error: dereferencing pointer to incomplete type
> nvme_smart.c:40: error: dereferencing pointer to incomplete type
> nvme_smart.c:43: error: dereferencing pointer to incomplete type
> nvme_smart.c:46: error: dereferencing pointer to incomplete type
> nvme_smart.c:49: error: dereferencing pointer to incomplete type
> nvme_smart.c:52: error: dereferencing pointer to incomplete type
> nvme_smart.c:55: error: dereferencing pointer to incomplete type
> nvme_smart.c:58: error: dereferencing pointer to incomplete type
> nvme_smart.c:61: error: dereferencing pointer to incomplete type
> nvme_smart.c:64: error: dereferencing pointer to incomplete type
> nvme_smart.c: In function 'main':
> nvme_smart.c:79: error: dereferencing pointer to incomplete type
> nvme_smart.c:107: error: dereferencing pointer to incomplete type
> nvme_smart.c:108: error: dereferencing pointer to incomplete type
> nvme_smart.c:124: warning: passing argument 1 of 'print_smart_log' from incompatible pointer type
> nvme_smart.c:139: warning: passing argument 1 of 'print_smart_log' from incompatible pointer type
> make: *** [nvme_smart] Error 1
>
> I have ran into this before and haven't found a way to get around it...
>
> Thanks,
> Ian
next prev parent reply other threads:[~2014-07-21 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 14:53 NVME User Installation Ian Ziemba
2014-07-16 14:39 ` Keith Busch
2014-07-21 16:17 ` Ian Ziemba
2014-07-21 21:33 ` Keith Busch [this message]
2014-07-22 16:14 ` Ian Ziemba
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=alpine.LRH.2.03.1407211024060.4703@AMR \
--to=keith.busch@intel.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