* compile nvme 4.13 appear error
@ 2017-09-18 13:02 Tony Yang
2017-09-18 17:27 ` Keith Busch
0 siblings, 1 reply; 7+ messages in thread
From: Tony Yang @ 2017-09-18 13:02 UTC (permalink / raw)
Dear All
I at redhat 6.5 ,kernel is 2.6.32-431.el6.x86_64?I comile nvme 4.13
appear this error:
[root at cescel03 nvme-nvme-4.13]# make
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/bounds.h
CHK include/generated/timeconst.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
CHK scripts/mod/devicetable-offsets.h
CHK include/generated/compile.h
AR drivers/nvme/host/built-in.o
CC [M] drivers/nvme/host/core.o
drivers/nvme/host/core.c: In function ?nvme_alloc_mpath_ns?:
drivers/nvme/host/core.c:3111: error: ?NVME_FAILOVER_RETRIES?
undeclared (first use in this function)
drivers/nvme/host/core.c:3111: error: (Each undeclared identifier is
reported only once
drivers/nvme/host/core.c:3111: error: for each function it appears in.)
drivers/nvme/host/core.c: In function ?nvme_trigger_failover?:
drivers/nvme/host/core.c:3277: error: ?NVME_FAILOVER_RETRIES?
undeclared (first use in this function)
make[3]: *** [drivers/nvme/host/core.o] Error 1
make[2]: *** [drivers/nvme/host] Error 2
make[1]: *** [drivers/nvme] Error 2
make: *** [drivers] Error 2
[root at cescel03 nvme-nvme-4.13]#
Could you tell me how to solve this problem?Thanks
^ permalink raw reply [flat|nested] 7+ messages in thread
* compile nvme 4.13 appear error
2017-09-18 13:02 compile nvme 4.13 appear error Tony Yang
@ 2017-09-18 17:27 ` Keith Busch
2017-09-19 1:57 ` Tony Yang
0 siblings, 1 reply; 7+ messages in thread
From: Keith Busch @ 2017-09-18 17:27 UTC (permalink / raw)
On Mon, Sep 18, 2017@09:02:15PM +0800, Tony Yang wrote:
> Dear All
>
> I at redhat 6.5 ,kernel is 2.6.32-431.el6.x86_64?I comile nvme 4.13
> appear this error:
>
> [root at cescel03 nvme-nvme-4.13]# make
> CHK include/config/kernel.release
> CHK include/generated/uapi/linux/version.h
> CHK include/generated/utsrelease.h
> CHK include/generated/bounds.h
> CHK include/generated/timeconst.h
> CHK include/generated/asm-offsets.h
> CALL scripts/checksyscalls.sh
> CHK scripts/mod/devicetable-offsets.h
> CHK include/generated/compile.h
> AR drivers/nvme/host/built-in.o
> CC [M] drivers/nvme/host/core.o
> drivers/nvme/host/core.c: In function ?nvme_alloc_mpath_ns?:
> drivers/nvme/host/core.c:3111: error: ?NVME_FAILOVER_RETRIES?
> undeclared (first use in this function)
> drivers/nvme/host/core.c:3111: error: (Each undeclared identifier is
> reported only once
> drivers/nvme/host/core.c:3111: error: for each function it appears in.)
> drivers/nvme/host/core.c: In function ?nvme_trigger_failover?:
> drivers/nvme/host/core.c:3277: error: ?NVME_FAILOVER_RETRIES?
> undeclared (first use in this function)
> make[3]: *** [drivers/nvme/host/core.o] Error 1
> make[2]: *** [drivers/nvme/host] Error 2
> make[1]: *** [drivers/nvme] Error 2
> make: *** [drivers] Error 2
Not sure where you got this source. The 4.13 kernel doesn't contain an
nvme driver with such errors, so it looks like whoever packaged up your
source really botched it up from applying out-of-tree stuff.
^ permalink raw reply [flat|nested] 7+ messages in thread
* compile nvme 4.13 appear error
2017-09-18 17:27 ` Keith Busch
@ 2017-09-19 1:57 ` Tony Yang
2017-09-19 2:10 ` Keith Busch
0 siblings, 1 reply; 7+ messages in thread
From: Tony Yang @ 2017-09-19 1:57 UTC (permalink / raw)
Hi, I from http://git.infradead.org/nvme.git to get 4.13 version
I want to compile with nvme new kernel, So I use 4.13 version to compile.
I would like to ask, how can I compile a new kernel for a successful
nvme? Thanks
2017-09-19 1:27 GMT+08:00 Keith Busch <keith.busch at intel.com>:
> On Mon, Sep 18, 2017@09:02:15PM +0800, Tony Yang wrote:
>> Dear All
>>
>> I at redhat 6.5 ,kernel is 2.6.32-431.el6.x86_64?I comile nvme 4.13
>> appear this error:
>>
>> [root at cescel03 nvme-nvme-4.13]# make
>> CHK include/config/kernel.release
>> CHK include/generated/uapi/linux/version.h
>> CHK include/generated/utsrelease.h
>> CHK include/generated/bounds.h
>> CHK include/generated/timeconst.h
>> CHK include/generated/asm-offsets.h
>> CALL scripts/checksyscalls.sh
>> CHK scripts/mod/devicetable-offsets.h
>> CHK include/generated/compile.h
>> AR drivers/nvme/host/built-in.o
>> CC [M] drivers/nvme/host/core.o
>> drivers/nvme/host/core.c: In function ?nvme_alloc_mpath_ns?:
>> drivers/nvme/host/core.c:3111: error: ?NVME_FAILOVER_RETRIES?
>> undeclared (first use in this function)
>> drivers/nvme/host/core.c:3111: error: (Each undeclared identifier is
>> reported only once
>> drivers/nvme/host/core.c:3111: error: for each function it appears in.)
>> drivers/nvme/host/core.c: In function ?nvme_trigger_failover?:
>> drivers/nvme/host/core.c:3277: error: ?NVME_FAILOVER_RETRIES?
>> undeclared (first use in this function)
>> make[3]: *** [drivers/nvme/host/core.o] Error 1
>> make[2]: *** [drivers/nvme/host] Error 2
>> make[1]: *** [drivers/nvme] Error 2
>> make: *** [drivers] Error 2
>
> Not sure where you got this source. The 4.13 kernel doesn't contain an
> nvme driver with such errors, so it looks like whoever packaged up your
> source really botched it up from applying out-of-tree stuff.
^ permalink raw reply [flat|nested] 7+ messages in thread
* compile nvme 4.13 appear error
2017-09-19 1:57 ` Tony Yang
@ 2017-09-19 2:10 ` Keith Busch
2017-09-19 15:27 ` Tony Yang
0 siblings, 1 reply; 7+ messages in thread
From: Keith Busch @ 2017-09-19 2:10 UTC (permalink / raw)
On Tue, Sep 19, 2017@09:57:08AM +0800, Tony Yang wrote:
> Hi, I from http://git.infradead.org/nvme.git to get 4.13 version
>
> I want to compile with nvme new kernel, So I use 4.13 version to compile.
I have the same one, and "nvme_alloc_mpath_ns" that you're producing an
error on doesn't exist in that tree. You've done something to your tree
to break it.
> I would like to ask, how can I compile a new kernel for a successful
> nvme? Thanks
Try using it as-is.
> 2017-09-19 1:27 GMT+08:00 Keith Busch <keith.busch at intel.com>:
> > On Mon, Sep 18, 2017@09:02:15PM +0800, Tony Yang wrote:
> >> Dear All
> >>
> >> I at redhat 6.5 ,kernel is 2.6.32-431.el6.x86_64?I comile nvme 4.13
> >> appear this error:
> >>
> >> [root at cescel03 nvme-nvme-4.13]# make
> >> CHK include/config/kernel.release
> >> CHK include/generated/uapi/linux/version.h
> >> CHK include/generated/utsrelease.h
> >> CHK include/generated/bounds.h
> >> CHK include/generated/timeconst.h
> >> CHK include/generated/asm-offsets.h
> >> CALL scripts/checksyscalls.sh
> >> CHK scripts/mod/devicetable-offsets.h
> >> CHK include/generated/compile.h
> >> AR drivers/nvme/host/built-in.o
> >> CC [M] drivers/nvme/host/core.o
> >> drivers/nvme/host/core.c: In function ?nvme_alloc_mpath_ns?:
> >> drivers/nvme/host/core.c:3111: error: ?NVME_FAILOVER_RETRIES?
> >> undeclared (first use in this function)
> >> drivers/nvme/host/core.c:3111: error: (Each undeclared identifier is
> >> reported only once
> >> drivers/nvme/host/core.c:3111: error: for each function it appears in.)
> >> drivers/nvme/host/core.c: In function ?nvme_trigger_failover?:
> >> drivers/nvme/host/core.c:3277: error: ?NVME_FAILOVER_RETRIES?
> >> undeclared (first use in this function)
> >> make[3]: *** [drivers/nvme/host/core.o] Error 1
> >> make[2]: *** [drivers/nvme/host] Error 2
> >> make[1]: *** [drivers/nvme] Error 2
> >> make: *** [drivers] Error 2
> >
> > Not sure where you got this source. The 4.13 kernel doesn't contain an
> > nvme driver with such errors, so it looks like whoever packaged up your
> > source really botched it up from applying out-of-tree stuff.
^ permalink raw reply [flat|nested] 7+ messages in thread
* compile nvme 4.13 appear error
2017-09-19 2:10 ` Keith Busch
@ 2017-09-19 15:27 ` Tony Yang
2017-09-19 17:33 ` Keith Busch
0 siblings, 1 reply; 7+ messages in thread
From: Tony Yang @ 2017-09-19 15:27 UTC (permalink / raw)
Hi,
I Once again downloaded the nvme 4.13 in
http://git.infradead.org/nvme.git, and then recompile the kernel, the
error occurred, how can I solve it, I hope to get your help, thank you
very much?
CC [M] drivers/nvme/host/core.o
drivers/nvme/host/core.c: In function 'nvme_alloc_mpath_ns':
drivers/nvme/host/core.c:3111:34: error: 'NVME_FAILOVER_RETRIES'
undeclared (first use in this function)
if (nvme_set_ns_active(nsa, ns, NVME_FAILOVER_RETRIES)) {
^
drivers/nvme/host/core.c:3111:34: note: each undeclared identifier is
reported only once for each function it appears in
drivers/nvme/host/core.c: In function 'nvme_trigger_failover':
drivers/nvme/host/core.c:3277:50: error: 'NVME_FAILOVER_RETRIES'
undeclared (first use in this function)
if (nvme_set_ns_active(standby_ns, mpath_ns, NVME_FAILOVER_RETRIES)) {
^
make[3]: *** [drivers/nvme/host/core.o] Error 1
make[2]: *** [drivers/nvme/host] Error 2
make[1]: *** [drivers/nvme] Error 2
make: *** [drivers] Error 2
[root at scst1 nvme-nvme-4.13]#
[root at scst1 nvme-nvme-4.13]# cat /proc/version
Linux version 3.10.0-327.el7.x86_64
(mockbuild at x86-034.build.eng.bos.redhat.com) (gcc version 4.8.3
20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Thu Oct 29 17:29:29 EDT 2015
2017-09-19 10:10 GMT+08:00 Keith Busch <keith.busch at intel.com>:
> On Tue, Sep 19, 2017@09:57:08AM +0800, Tony Yang wrote:
>> Hi, I from http://git.infradead.org/nvme.git to get 4.13 version
>>
>> I want to compile with nvme new kernel, So I use 4.13 version to compile.
>
> I have the same one, and "nvme_alloc_mpath_ns" that you're producing an
> error on doesn't exist in that tree. You've done something to your tree
> to break it.
>
>> I would like to ask, how can I compile a new kernel for a successful
>> nvme? Thanks
>
> Try using it as-is.
>
>> 2017-09-19 1:27 GMT+08:00 Keith Busch <keith.busch at intel.com>:
>> > On Mon, Sep 18, 2017@09:02:15PM +0800, Tony Yang wrote:
>> >> Dear All
>> >>
>> >> I at redhat 6.5 ,kernel is 2.6.32-431.el6.x86_64?I comile nvme 4.13
>> >> appear this error:
>> >>
>> >> [root at cescel03 nvme-nvme-4.13]# make
>> >> CHK include/config/kernel.release
>> >> CHK include/generated/uapi/linux/version.h
>> >> CHK include/generated/utsrelease.h
>> >> CHK include/generated/bounds.h
>> >> CHK include/generated/timeconst.h
>> >> CHK include/generated/asm-offsets.h
>> >> CALL scripts/checksyscalls.sh
>> >> CHK scripts/mod/devicetable-offsets.h
>> >> CHK include/generated/compile.h
>> >> AR drivers/nvme/host/built-in.o
>> >> CC [M] drivers/nvme/host/core.o
>> >> drivers/nvme/host/core.c: In function ?nvme_alloc_mpath_ns?:
>> >> drivers/nvme/host/core.c:3111: error: ?NVME_FAILOVER_RETRIES?
>> >> undeclared (first use in this function)
>> >> drivers/nvme/host/core.c:3111: error: (Each undeclared identifier is
>> >> reported only once
>> >> drivers/nvme/host/core.c:3111: error: for each function it appears in.)
>> >> drivers/nvme/host/core.c: In function ?nvme_trigger_failover?:
>> >> drivers/nvme/host/core.c:3277: error: ?NVME_FAILOVER_RETRIES?
>> >> undeclared (first use in this function)
>> >> make[3]: *** [drivers/nvme/host/core.o] Error 1
>> >> make[2]: *** [drivers/nvme/host] Error 2
>> >> make[1]: *** [drivers/nvme] Error 2
>> >> make: *** [drivers] Error 2
>> >
>> > Not sure where you got this source. The 4.13 kernel doesn't contain an
>> > nvme driver with such errors, so it looks like whoever packaged up your
>> > source really botched it up from applying out-of-tree stuff.
^ permalink raw reply [flat|nested] 7+ messages in thread* compile nvme 4.13 appear error
2017-09-19 15:27 ` Tony Yang
@ 2017-09-19 17:33 ` Keith Busch
0 siblings, 0 replies; 7+ messages in thread
From: Keith Busch @ 2017-09-19 17:33 UTC (permalink / raw)
On Tue, Sep 19, 2017@11:27:39PM +0800, Tony Yang wrote:
> Hi,
>
> I Once again downloaded the nvme 4.13 in
> http://git.infradead.org/nvme.git, and then recompile the kernel, the
> error occurred, how can I solve it, I hope to get your help, thank you
> very much?
>
> CC [M] drivers/nvme/host/core.o
> drivers/nvme/host/core.c: In function 'nvme_alloc_mpath_ns':
> drivers/nvme/host/core.c:3111:34: error: 'NVME_FAILOVER_RETRIES'
> undeclared (first use in this function)
> if (nvme_set_ns_active(nsa, ns, NVME_FAILOVER_RETRIES)) {
> ^
> drivers/nvme/host/core.c:3111:34: note: each undeclared identifier is
> reported only once for each function it appears in
> drivers/nvme/host/core.c: In function 'nvme_trigger_failover':
> drivers/nvme/host/core.c:3277:50: error: 'NVME_FAILOVER_RETRIES'
> undeclared (first use in this function)
> if (nvme_set_ns_active(standby_ns, mpath_ns, NVME_FAILOVER_RETRIES)) {
> ^
> make[3]: *** [drivers/nvme/host/core.o] Error 1
> make[2]: *** [drivers/nvme/host] Error 2
> make[1]: *** [drivers/nvme] Error 2
> make: *** [drivers] Error 2
Like I said before, those errors do not exist in an unmodified version
of the git repo you're linking to. You've out-of-tree stuff in your
source, so you or whoever set it up broke it.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Compile nvme 4.13 appear error
@ 2017-09-15 14:08 Tony Yang
0 siblings, 0 replies; 7+ messages in thread
From: Tony Yang @ 2017-09-15 14:08 UTC (permalink / raw)
Dear All
I use make to Compile nvme 4.13, Appear this error
CC drivers/acpi/acpica/nsxfname.o
make[3]: *** No rule to make target `drivers/acpi/acpica/nsxfobj.o',
needed by `drivers/acpi/acpica/acpi.o'. Stop.
make[2]: *** [drivers/acpi/acpica] Error 2
make[1]: *** [drivers/acpi] Error 2
make: *** [drivers] Error 2
[root at cescel03 nvme-nvme-4.13]# uname -r
2.6.32-431.el6.x86_64
[root at cescel03 nvme-nvme-4.13]# pwd
/u01/soft/nvme-nvme-4.13
Could you tell me how to solve this problem? I checked, The nsxfobj.o
file does not exist nvme 4.13 package.
Thanks
---Tony
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2017-09-19 17:33 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-09-18 13:02 compile nvme 4.13 appear error Tony Yang
2017-09-18 17:27 ` Keith Busch
2017-09-19 1:57 ` Tony Yang
2017-09-19 2:10 ` Keith Busch
2017-09-19 15:27 ` Tony Yang
2017-09-19 17:33 ` Keith Busch
-- strict thread matches above, loose matches on Subject: below --
2017-09-15 14:08 Compile " Tony Yang
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.