From: "Wiles, Roger Keith" <keith.wiles@windriver.com>
To: "CAO, SHUI" <waterman.cao@intel.com>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Build failure on Ubuntu 14.04
Date: Tue, 8 Jul 2014 14:35:27 +0000 [thread overview]
Message-ID: <E1B92792-28F0-4418-BA45-0085D5CC03ED@windriver.com> (raw)
In-Reply-To: <AA3F441F262C58498CD6D0C1801DE7EB0AAC127E@SHSMSX103.ccr.corp.intel.com>
Here is the release information I have, if you want more let me know.
$sudo apt-get update
$sudo apt-get upgrade
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty
$ uname -a
Linux keithw-W2600CR 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ gcc --version
gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2
Copyright (C) 2013 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.
Keith Wiles, Principal Technologist with CTO office, Wind River
mobile 972-213-5533
[Powering 30 Years of Innovation]<http://www.windriver.com/announces/wr30/>
On Jul 7, 2014, at 9:12 PM, Cao, Waterman <waterman.cao@intel.com<mailto:waterman.cao@intel.com>> wrote:
Thanks Keith.
we will try to enable CentOS in our daily build test.
But I has a little concern about Ubuntu 14.
We enabled latest UB14 with kernel 3.13.0-24 at this may.
It seems that UB LTS will upgrade Linux kernel to 3.13.0-30.
But we don’t know when it upgrade, and it will cost a lot of effort to upgrade environment.
Can we indicate specific version for Ubuntu 14.04?
Btw, we met the same issue in RedHat 7.0 Beta version.
Waterman
From: Wiles, Roger Keith [mailto:keith.wiles@windriver.com]
Sent: Monday, July 7, 2014 10:42 PM
To: De Lara Guarch, Pablo
Cc: Cao, Waterman; <dev@dpdk.org<mailto:dev@dpdk.org>>
Subject: Re: [dpdk-dev] Build failure on Ubuntu 14.04
Someone compiling on CentOS kernel 3.13.7 needed the original code. Looks like some other type of ifdef change needs to be done to the kcompat.h file to allow it to compile on Ubuntu 14.04 with kernel 3.13.0-30.
Keith Wiles, Principal Technologist with CTO office, Wind River
mobile 972-213-5533
[Powering 30 Years of Innovation]<http://www.windriver.com/announces/wr30/>
On Jul 7, 2014, at 3:39 AM, De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com<mailto:pablo.de.lara.guarch@intel.com>> wrote:
Hi Keith,
we built the newest dpdk code on my machine, it seems OK,
please see UB14.04 info in my computer.
System: Ubuntu14.04
Kernel: 3.13.0-24 X86_64
Compiler: GCC 4.8.2 x86_64
Can you let me know which kernel version you use?
Apparently, it is this one: 3.13.0-30-generic, from uname -a
Thanks
Waterman
next prev parent reply other threads:[~2014-07-08 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 15:27 Wiles, Roger Keith
2014-07-05 15:28 ` Wiles, Roger Keith
2014-07-05 15:50 ` Wiles, Roger Keith
2014-07-07 8:13 ` Cao, Waterman
2014-07-07 8:39 ` De Lara Guarch, Pablo
2014-07-07 14:41 ` Wiles, Roger Keith
2014-07-07 14:59 ` Wiles, Roger Keith
2014-07-07 15:24 ` Wiles, Roger Keith
2014-07-16 16:48 ` Murugesan, AnbarasanX
2014-07-08 2:12 ` Cao, Waterman
2014-07-08 14:35 ` Wiles, Roger Keith [this message]
2014-07-11 8:00 ` Choi, Sy Jong
2014-07-11 8:43 ` Masaru Oki
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=E1B92792-28F0-4418-BA45-0085D5CC03ED@windriver.com \
--to=keith.wiles@windriver.com \
--cc=dev@dpdk.org \
--cc=waterman.cao@intel.com \
/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).