From: Bo Chen <glbrt.chen@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] build failed on dpdk-1.2.3r2
Date: Tue, 11 Jun 2013 12:59:45 +0800 [thread overview]
Message-ID: <CAESsnAQ2EzvRoakx3fVa402h6m4egbEOmiL8MJptOdoOhuisQg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
When I run the make command on dpdk-1.2.3r2, it show me the following, but
it works on dpdk-1.2.3r1:
== Build lib/librte_eal/linuxapp/igb_uio
LD
/opt/dpdk-1.2.3r2/build/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
CC [M]
/opt/dpdk-1.2.3r2/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
cc1: warnings being treated as errors
/opt/dpdk-1.2.3r2/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c: In
function ‘igbuio_pci_probe’:
include/linux/slab.h:349: error: inlining failed in call to
‘kzalloc.clone.0’: --param max-inline-insns-single limit reached
/opt/dpdk-1.2.3r2/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:267:
error: called from here
make[8]: ***
[/opt/dpdk-1.2.3r2/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o]
Error 1
make[7]: ***
[_module_/opt/dpdk-1.2.3r2/build/build/lib/librte_eal/linuxapp/igb_uio]
Error 2
make[6]: *** [sub-make] Error 2
make[5]: *** [igb_uio.ko] Error 2
make[4]: *** [igb_uio] Error 2
make[3]: *** [linuxapp] Error 2
make[2]: *** [librte_eal] Error 2
make[1]: *** [lib] Error 2
make: *** [all] Error 2
And I noticed there is a warning from gcc: --param max-inline-insns-single
limit reached
So I changed the file: lib/librte_eal/linuxapp/igb_uio/Makefile from 50 to
100.
MODULE_CFLAGS += -I$(SRCDIR) --param max-inline-insns-single=100
It works.
And the question is: Is there any change on dpdk-1.2.3r2 let the parameter
max-inline-insns-single not big enough, or there is something wrong at my
env.
Thanks & BR
Bo
[-- Attachment #2: Type: text/html, Size: 1810 bytes --]
reply other threads:[~2013-06-11 4:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAESsnAQ2EzvRoakx3fVa402h6m4egbEOmiL8MJptOdoOhuisQg@mail.gmail.com \
--to=glbrt.chen@gmail.com \
--cc=dev@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).