automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw42248[v4, 10/16] doc: remove unneeded deprecation notice
Date: 05 Jul 2018 20:26:21 -0700	[thread overview]
Message-ID: <0590c7$236nq1@orsmga001.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 5607 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/42248

_Compilation issues_

Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: 2018-07-04 08:51:48
DPDK git baseline: Repo:dpdk-master, CommitID: 05e0eee0001cb19671eb7e8d3dd68680a695fea2

Build Summary: 15 Builds Done, 14 Successful, 1 Failures

Test environment and configuration as below:

OS: FC25
	Kernel Version: 4.9.13-100.fc24.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
	Clang Version: 3.8.0 (tags/RELEASE_380/final)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc-debug

OS: FC24
	Kernel Version: 4.9.13-100.fc24.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
	Clang Version: 3.8.0 (tags/RELEASE_380/final)
	i686-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc-shared
	x86_64-native-linuxapp-clang

OS: CENTOS
	Kernel Version: 3.10.0-514.10.2.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
	Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
	i686-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc-shared

OS: UB1604
	Kernel Version: 4.4.0-78-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
	Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc-shared
	i686-native-linuxapp-gcc

OS: FreeBSD
	Kernel Version: 10.3-RELEASE
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.76-MHz K8-class CPU)
	GCC Version: gcc (FreeBSD Ports Collection) 4.8.5
	Clang Version: 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
	x86_64-native-bsdapp-clang
	x86_64-native-bsdapp-gcc

*Failed Build #1:
OS: FC24
Target: i686-native-linuxapp-gcc
  SYMLINK-FILE include/rte_cpuflags.h
  SYMLINK-FILE include/rte_cycles.h
In file included from /usr/include/features.h:392:0,
                 from /usr/include/stdio.h:27,
                 from /tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/lib/librte_cfgfile/rte_cfgfile.c:5:
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
 # include <gnu/stubs-32.h>
                           ^
compilation terminated.
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for target 'rte_cfgfile.o' failed
make[5]: *** [rte_cfgfile.o] Error 1
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/mk/rte.subdir.mk:35: recipe for target 'librte_cfgfile' failed
make[4]: *** [librte_cfgfile] Error 2
make[4]: *** Waiting for unfinished jobs....
  SYMLINK-FILE include/rte_memcpy.h
  SYMLINK-FILE include/rte_io.h
  SYMLINK-FILE include/rte_pause.h
--
  SYMLINK-FILE include/exec-env/rte_kni_common.h
  CC eal.o
In file included from /usr/include/features.h:392:0,
                 from /usr/include/stdio.h:27,
                 from /tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/lib/librte_eal/linuxapp/eal/eal.c:6:
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
 # include <gnu/stubs-32.h>
                           ^
compilation terminated.
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for target 'eal.o' failed
make[7]: *** [eal.o] Error 1
make[7]: *** Waiting for unfinished jobs....
  CC eal_cpuflags.o
In file included from /usr/include/features.h:392:0,
                 from /usr/include/elf.h:22,
                 from /tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/lib/librte_eal/linuxapp/eal/eal_cpuflags.c:5:
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
 # include <gnu/stubs-32.h>
                           ^
compilation terminated.
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for target 'eal_cpuflags.o' failed
make[7]: *** [eal_cpuflags.o] Error 1
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/mk/rte.subdir.mk:35: recipe for target 'eal' failed
make[6]: *** [eal] Error 2
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/mk/rte.subdir.mk:35: recipe for target 'linuxapp' failed
make[5]: *** [linuxapp] Error 2
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/mk/rte.subdir.mk:35: recipe for target 'librte_eal' failed
make[4]: *** [librte_eal] Error 2
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/mk/rte.sdkbuild.mk:49: recipe for target 'lib' failed
make[3]: *** [lib] Error 2
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
make[2]: *** [all] Error 2
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/mk/rte.sdkinstall.mk:57: recipe for target 'pre_install' failed
make[1]: *** [pre_install] Error 2
/tmp/FC24_K4.5.5_GCC6.1.1/i686-native-linuxapp-gcc/9e85eda74d8448f5a399f83f835104b8/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
make: *** [install] Error 2

DPDK STV team

                 reply	other threads:[~2018-07-06  3:26 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='0590c7$236nq1@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=test-report@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).