> On Nov 17, 2016, at 11:02 AM, David Aldrich <David.Aldrich at EMEA.NEC.COM> > wrote: > > You are all very helpful. Thank you. > > I'm afraid 'make install' isn't working:
I only use ?make install T=${RTE_TARGET} -j? command line, but you can remove the -j. > > # make install > make[1]: Nothing to be done for 'pre_install'. > ================== Installing /usr/local/ > cp: cannot stat 'build/lib/*': No such file or directory > /root/dpdk-2.2.0/mk/rte.sdkinstall.mk:116: recipe for target > 'install-runtime' failed > make[3]: *** [install-runtime] Error 1 > > David > >> -----Original Message----- >> From: Wiles, Keith [mailto:keith.wiles at intel.com] >> Sent: 17 November 2016 17:00 >> To: David Aldrich <David.Aldrich at EMEA.NEC.COM> >> Cc: Pavey, Nicholas <npavey at akamai.com>; Thomas Monjalon >> <thomas.monjalon at 6wind.com>; users at dpdk.org >> Subject: Re: [dpdk-users] Problem building DPDK libraries >> >> >>> On Nov 17, 2016, at 10:56 AM, David Aldrich >> <David.Aldrich at EMEA.NEC.COM> wrote: >>> >>> Thanks. >>> >>> Do I need to do ?make install? or is ?make? sufficient? >> >> I do not really install DPDK, but use it from the source tree. If you want >> to install >> it then look at the docs, it talks about install the binaries. The install >> is handy >> with the T= option only to make sure you build the correct version and ignore >> the warning at the end. >> >>> >>> David >>> >>> From: Pavey, Nicholas [mailto:npavey at akamai.com] >>> Sent: 17 November 2016 16:55 >>> To: David Aldrich <David.Aldrich at EMEA.NEC.COM>; Wiles, Keith >>> <keith.wiles at intel.com> >>> Cc: Thomas Monjalon <thomas.monjalon at 6wind.com>; users at dpdk.org >>> Subject: Re: [dpdk-users] Problem building DPDK libraries >>> >>> Yes, I?ve found that ?j<n> causes problems too. >>> >>> I believe I?ve used both the T=<?> and the environment variable version >> without problems, as long as : >>> >>> ? You don?t use parallel make (-j<n>) >>> ? You completely remove the target directory before building (this >>> has the >> same name as ?T?) >>> o I don?t recall exactly the problem this addressed, but I did find that >>> doing a >> completely clean build is sometimes necessary. >>> >>> Thanks, >>> >>> >>> Nick >>> >>> >>> From: David Aldrich <David.Aldrich at EMEA.NEC.COM> >>> Date: Thursday, November 17, 2016 at 11:47 AM >>> To: David Aldrich <David.Aldrich at EMEA.NEC.COM>, "Wiles, Keith" >>> <keith.wiles at intel.com> >>> Cc: Thomas Monjalon <thomas.monjalon at 6wind.com>, "users at dpdk.org" >>> <users at dpdk.org> >>> Subject: Re: [dpdk-users] Problem building DPDK libraries >>> >>> Hi >>> >>> I find that: >>> >>> make >>> >>> succeeds. >>> >>> But I've been advised to run: >>> >>> make -j T=x86_64-native-linuxapp-gcc install >>> >>> I think '-j' was causing the compiler problems, so I can drop that. >>> >>> Do I need the 'T=' part? >>> >>> How would I do: >>> >>> make install >>> >>> ? That doesn't work currently for me. >>> >>> David >>> >>> -----Original Message----- >>> From: David Aldrich >>> Sent: 17 November 2016 16:29 >>> To: 'David Aldrich' <David.Aldrich at emea.nec.com>; Wiles, Keith >>> <keith.wiles at intel.com> >>> Cc: Thomas Monjalon <thomas.monjalon at 6wind.com>; users at dpdk.org >>> Subject: RE: [dpdk-users] Problem building DPDK libraries The >>> allocation for /tmp is 7.9G, which is almost entirely unused. >>> David >>>> -----Original Message----- >>>> From: users [mailto:users-bounces at dpdk.org] On Behalf Of David >>>> Aldrich >>>> Sent: 17 November 2016 16:25 >>>> To: Wiles, Keith <keith.wiles at intel.com> >>>> Cc: Thomas Monjalon <thomas.monjalon at 6wind.com>; users at dpdk.org >>>> Subject: Re: [dpdk-users] Problem building DPDK libraries >>>> >>>> Hi >>>> >>>> I'm using: >>>> >>>> # gcc --version >>>> gcc (Wind River Linux 5.2.0-8.0-intel-haswell-64) 5.2.0 >>>> >>>> I'll consider the tmp space. >>>> >>>> Thanks >>>> >>>> David >>>> >>>>> -----Original Message----- >>>>> From: Wiles, Keith [mailto:keith.wiles at intel.com] >>>>> Sent: 17 November 2016 16:10 >>>>> To: David Aldrich <David.Aldrich at EMEA.NEC.COM> >>>>> Cc: Thomas Monjalon <thomas.monjalon at 6wind.com>; users at dpdk.org >>>>> Subject: Re: [dpdk-users] Problem building DPDK libraries >>>>> >>>>> >>>>>> On Nov 17, 2016, at 10:05 AM, David Aldrich >>>>> <David.Aldrich at EMEA.NEC.COM> wrote: >>>>>> >>>>>> Thanks, I thought I had installed the kernel headers, but I had >>>>>> done it >>>>> incorrectly. Now fixed. >>>>>> >>>>>> But make is still failing: >>>>>> >>>>>> CC ixgbe_rxtx_vec_sse.o >>>>>> gcc: internal compiler error: Killed (program cc1) Please submit >>>>>> a full bug report, with preprocessed source if appropriate. >>>>>> See <support at windriver.com> for instructions. >>>>>> /root/dpdk-stable-16.07.1/mk/internal/rte.compile-pre.mk:138: >>>>>> recipe for target 'rte_eth_af_packet.o? failed >>>>> >>>>> What version of GCC? >>>>> >>>>> When I see this type of error it is sometimes not enough tmp space >>>>> to compile the file, just a thought. >>>>> >>>>>> make[6]: *** [rte_eth_af_packet.o] Error 4 >>>>>> /root/dpdk-stable-16.07.1/mk/rte.subdir.mk:61: recipe for target >>>>>> 'af_packet' failed >>>>>> make[5]: *** [af_packet] Error 2 >>>>>> make[5]: *** Waiting for unfinished jobs.... >>>>>> >>>>>> Best regards >>>>>> >>>>>> David >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] >>>>>>> Sent: 17 November 2016 16:00 >>>>>>> To: David Aldrich <David.Aldrich at EMEA.NEC.COM> >>>>>>> Cc: users at dpdk.org >>>>>>> Subject: Re: [dpdk-users] Problem building DPDK libraries >>>>>>> >>>>>>> 2016-11-17 15:51, David Aldrich: >>>>>>>> make[6]: *** /lib/modules/4.1.21-rt13-WR8.0.0.10_preempt-rt/build: >>>>>>>> No such >>>>>>> file or directory. Stop. >>>>>>> >>>>>>> You need the kernel headers, or just disable compilation of >>>>>>> kernel >>> modules: >>>>>>> sed -ri 's,(KNI_KMOD=).*,\1n,' build/.config >>>>>>> sed -ri 's,(IGB_UIO=).*,\1n,' build/.config >>>>>>> >>>>>>> >>>>>>> >>>>>>> Click >>>>>>> >>>>> >>>> >>> https://www.mailcontrol.com/sr/MZbqvYs5QwJvpeaetUwhCQ==> >>>>>>> njH0BFwQAIYudV!69Vnv0C8JC0YknPHNppj5zLq66BGWNXYg== to >> report >>>> this >>>>>>> email as spam. >>>>> >>>>> Regards, >>>>> Keith >>> >>> >>> >>> >>> >>> Click here to report this email as spam. >>> >> >> Regards, >> Keith > Regards, Keith