From: Andrew Rybchenko <arybchenko@solarflare.com>
To: <dev@dpdk.org>, Anatoly Burakov <anatoly.burakov@intel.com>
Subject: [dpdk-dev] Build failure on RHEL 7.4
Date: Wed, 11 Apr 2018 22:09:23 +0300 [thread overview]
Message-ID: <cd189dd0-67b4-4431-b709-366009ed8e12@solarflare.com> (raw)
Hello,
build fails on RHEL 7.4. I've not tried to dig it.
lib/librte_eal/linuxapp/eal/eal_memalloc.c: In function ‘resize_hugefile’:
librte_eal/linuxapp/eal/eal_memalloc.c:343:27: error:
‘FALLOC_FL_PUNCH_HOLE’ undeclared (first use in this function)
int flags = grow ? 0 : FALLOC_FL_PUNCH_HOLE |
^
lib/librte_eal/linuxapp/eal/eal_memalloc.c:343:27: note: each undeclared
identifier is reported only once for each function it appears in
lib/librte_eal/linuxapp/eal/eal_memalloc.c:344:6: error:
‘FALLOC_FL_KEEP_SIZE’ undeclared (first use in this function)
FALLOC_FL_KEEP_SIZE;
^
make[6]: *** [eal_memalloc.o] Error 1
make[6]: *** Waiting for unfinished jobs....
make[5]: *** [eal] Error 2
make[4]: *** [linuxapp] Error 2
make[3]: *** [librte_eal] Error 2
make[2]: *** [lib] Error 2
make[1]: *** [all] Error 2
make: *** [all] Error 2
$ gcc --version
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ uname -r
3.10.0-693.el7.x86_64
Andrew.
next reply other threads:[~2018-04-11 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 19:09 Andrew Rybchenko [this message]
2018-04-11 19:40 ` Thomas Monjalon
2018-04-11 19:46 ` Pavan Nikhilesh
2018-04-11 19:56 ` Thomas Monjalon
2018-04-11 20:14 ` Thomas Monjalon
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=cd189dd0-67b4-4431-b709-366009ed8e12@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=anatoly.burakov@intel.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).