* [dpdk-dev] make install and RTE_KERNELDIR in dpdk 2.2
@ 2015-12-16 14:14 Piotr Bartosiewicz
2015-12-16 23:26 ` Thomas Monjalon
0 siblings, 1 reply; 4+ messages in thread
From: Piotr Bartosiewicz @ 2015-12-16 14:14 UTC (permalink / raw)
To: dev
A new 'make install' wrongly assumes that the output module name is
always 'uname -r' even if RTE_KERNELDIR is passed.
# make install T=... DESTDIR=/tmp/dpdk
RTE_KERNELDIR=/lib/modules/3.16.0-4-amd64/build
...
# ls /tmp/dpdk/lib/modules/
4.2.0-18-generic
--
Regards
Piotr Bartosiewicz
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] make install and RTE_KERNELDIR in dpdk 2.2
2015-12-16 14:14 [dpdk-dev] make install and RTE_KERNELDIR in dpdk 2.2 Piotr Bartosiewicz
@ 2015-12-16 23:26 ` Thomas Monjalon
2015-12-17 11:11 ` Piotr Bartosiewicz
0 siblings, 1 reply; 4+ messages in thread
From: Thomas Monjalon @ 2015-12-16 23:26 UTC (permalink / raw)
To: Piotr Bartosiewicz; +Cc: dev
2015-12-16 15:14, Piotr Bartosiewicz:
> A new 'make install' wrongly assumes that the output module name is
> always 'uname -r' even if RTE_KERNELDIR is passed.
No it does not assume anything, it is just a default value.
How can you find the directory based on RTE_KERNELDIR?
You can set kerneldir=something-else on the "make install" command line.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] make install and RTE_KERNELDIR in dpdk 2.2
2015-12-16 23:26 ` Thomas Monjalon
@ 2015-12-17 11:11 ` Piotr Bartosiewicz
2015-12-17 11:18 ` Thomas Monjalon
0 siblings, 1 reply; 4+ messages in thread
From: Piotr Bartosiewicz @ 2015-12-17 11:11 UTC (permalink / raw)
To: Thomas Monjalon; +Cc: dev
W dniu 17.12.2015 o 00:26, Thomas Monjalon pisze:
> 2015-12-16 15:14, Piotr Bartosiewicz:
>> A new 'make install' wrongly assumes that the output module name is
>> always 'uname -r' even if RTE_KERNELDIR is passed.
> No it does not assume anything, it is just a default value.
> How can you find the directory based on RTE_KERNELDIR?
>
> You can set kerneldir=something-else on the "make install" command line.
OK, I understand kerneldir in general can't be guessed from RTE_KERNELDIR,
but maybe there should be some hint in docs to pass kerneldir when
RTE_KERNELDIR is used.
In my case the working command is:
make install T=... DESTDIR=...
RTE_KERNELDIR=/lib/modules/3.16.0-4-amd64/build
kerneldir=/lib/modules/3.16.0-4-amd64/extra/dpdk
Thanks
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] make install and RTE_KERNELDIR in dpdk 2.2
2015-12-17 11:11 ` Piotr Bartosiewicz
@ 2015-12-17 11:18 ` Thomas Monjalon
0 siblings, 0 replies; 4+ messages in thread
From: Thomas Monjalon @ 2015-12-17 11:18 UTC (permalink / raw)
To: Piotr Bartosiewicz; +Cc: dev
2015-12-17 12:11, Piotr Bartosiewicz:
> W dniu 17.12.2015 o 00:26, Thomas Monjalon pisze:
> > 2015-12-16 15:14, Piotr Bartosiewicz:
> >> A new 'make install' wrongly assumes that the output module name is
> >> always 'uname -r' even if RTE_KERNELDIR is passed.
> > No it does not assume anything, it is just a default value.
> > How can you find the directory based on RTE_KERNELDIR?
> >
> > You can set kerneldir=something-else on the "make install" command line.
>
> OK, I understand kerneldir in general can't be guessed from RTE_KERNELDIR,
> but maybe there should be some hint in docs to pass kerneldir when
> RTE_KERNELDIR is used.
Yes you are right, it can be better documented.
> In my case the working command is:
> make install T=... DESTDIR=...
> RTE_KERNELDIR=/lib/modules/3.16.0-4-amd64/build
> kerneldir=/lib/modules/3.16.0-4-amd64/extra/dpdk
Please, feel free to update the doc.
Thanks
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-12-17 11:19 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-12-16 14:14 [dpdk-dev] make install and RTE_KERNELDIR in dpdk 2.2 Piotr Bartosiewicz
2015-12-16 23:26 ` Thomas Monjalon
2015-12-17 11:11 ` Piotr Bartosiewicz
2015-12-17 11:18 ` Thomas Monjalon
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).