From: David Aldrich <David.Aldrich@EMEA.NEC.COM>
To: David Aldrich <David.Aldrich@EMEA.NEC.COM>,
"Wiles, Keith" <keith.wiles@intel.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Problem building DPDK libraries
Date: Thu, 17 Nov 2016 16:47:58 +0000 [thread overview]
Message-ID: <107d574f4cd141808d2cfdc4dbe04644@EUX13SRV1.EU.NEC.COM> (raw)
In-Reply-To: <4a5fff2a23cb4ebdb04a03662708c662@EUX13SRV1.EU.NEC.COM>
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@emea.nec.com>; Wiles, Keith
> <keith.wiles@intel.com>
> Cc: Thomas Monjalon <thomas.monjalon@6wind.com>; users@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@dpdk.org] On Behalf Of David Aldrich
> > Sent: 17 November 2016 16:25
> > To: Wiles, Keith <keith.wiles@intel.com>
> > Cc: Thomas Monjalon <thomas.monjalon@6wind.com>; users@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@intel.com]
> > > Sent: 17 November 2016 16:10
> > > To: David Aldrich <David.Aldrich@EMEA.NEC.COM>
> > > Cc: Thomas Monjalon <thomas.monjalon@6wind.com>; users@dpdk.org
> > > Subject: Re: [dpdk-users] Problem building DPDK libraries
> > >
> > >
> > > > On Nov 17, 2016, at 10:05 AM, David Aldrich
> > > <David.Aldrich@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@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@6wind.com]
> > > >> Sent: 17 November 2016 16:00
> > > >> To: David Aldrich <David.Aldrich@EMEA.NEC.COM>
> > > >> Cc: users@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/4ZSg1SI7T87GX2PQPOmvUstiqgZjxB51m1JQqZ
> > > >> njH0BFwQAIYudV!69Vnv0C8JC0YknPHNppj5zLq66BGWNXYg== to report
> > this
> > > >> email as spam.
> > >
> > > Regards,
> > > Keith
next prev parent reply other threads:[~2016-11-17 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 15:51 David Aldrich
2016-11-17 15:59 ` Thomas Monjalon
2016-11-17 16:05 ` David Aldrich
2016-11-17 16:09 ` Wiles, Keith
2016-11-17 16:24 ` David Aldrich
2016-11-17 16:28 ` David Aldrich
2016-11-17 16:47 ` David Aldrich [this message]
2016-11-17 16:54 ` Pavey, Nicholas
2016-11-17 16:56 ` David Aldrich
2016-11-17 16:58 ` Pavey, Nicholas
2016-11-17 17:00 ` Wiles, Keith
2016-11-17 17:02 ` David Aldrich
2016-11-17 17:16 ` Wiles, Keith
2016-11-17 17:23 ` David Aldrich
2016-11-17 17:31 ` Thomas Monjalon
2016-11-17 17:27 ` Thomas Monjalon
2016-11-17 18:38 ` Pavey, Nicholas
2016-11-17 16:56 ` Wiles, Keith
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=107d574f4cd141808d2cfdc4dbe04644@EUX13SRV1.EU.NEC.COM \
--to=david.aldrich@emea.nec.com \
--cc=keith.wiles@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=users@dpdk.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 NNTP newsgroup(s).