From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Nagaraj Trivedi <nagaraj.trivedi@tcs.com>,
"Wiles, Keith" <keith.wiles@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Compilation errors with msg sys/cdef.h: No such file or directory
Date: Wed, 13 Jan 2016 08:53:44 +0000 [thread overview]
Message-ID: <56961098.3050505@intel.com> (raw)
In-Reply-To: <OF365E26F4.43B1F42C-ON65257F38.0038AB5F-65257F38.003B9C3A@tcs.com>
Hi Nagaraj,
It looks like you are running on a 64 bit Linux distro but you are
building 32 bits DPDK app.
You are probably missing 32-bit glibc library/headers.
Thanks,
Sergio
On 12/01/2016 10:50, Nagaraj Trivedi wrote:
> Hi Keith, cdefs.h is located under the directory
>
> /usr/include/x86-64-linux-gnu/sys/cdefs.h
>
> I have fixed this by modifying Makefile
> <path-to-dpdk>/dpdk/lib/librte_eal/linuxapp/eal/Makefile as
>
> CFLAGS += -I/usr/include/x86-64-linux-gnu/
>
> But it is throwing error other files not found
>
> fatal error: gnu/stubs-32.h: No such file or directory
>
> Is there a way that by modifying in only one place will fix these type of
> issues
>
>
> Thanks & Regards
> Nagaraj Trivedi
>
> ____________________________________________
> Experience certainty. IT Services
> Business Solutions
> Consulting
> ____________________________________________
>
>
>
>
> From: "Wiles, Keith" <keith.wiles@intel.com>
> To: Nagaraj Trivedi <nagaraj.trivedi@tcs.com>, "users@dpdk.org"
> <users@dpdk.org>
> Date: 01/11/2016 08:27 PM
> Subject: Re: [dpdk-users] Compilation errors with msg sys/cdef.h:
> No such file or directory
>
>
>
> On 1/10/16, 11:52 PM, "users on behalf of Nagaraj Trivedi"
> <users-bounces@dpdk.org on behalf of nagaraj.trivedi@tcs.com> wrote:
>
>> Hi All, as part of DPDK compilation I have executed the following command
>>
>> make install T=i686-native-linuxapp-gcc
>>
>> It is throwing error message saying
>>
>> In file included from /usr/include/stdio.h:27:0,
>> from
>> /<path-to-dpdk-dir>/dpdk/lib/librte_eal/linuxapp/eal/eal.c:35:
>> /usr/include/features.h:374:25: fatal error: sys/cdefs.h: No such file or
>> directory
>>
>> # include <sys/cdefs.h>
>>
>> Compilation terminated
>>
>> Please let me know what could be the reasons
> Hi Niagara,
>
> Please give us a bit more information like the Linux version and distro.
>
> Eg.
> rkwiles@rkwiles-supermicro:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 15.10
> Release: 15.10
> Codename: wily
>
> I am going to assume your Linux distribution does not have sys/cdefs.h in
> the same location as other distros. Please run a find on your system and
> see if cdefs.h is located some place else in the system then
> /usr/include/sys/cdefs.h
>
>
> Thanks
> ++Keith
>> Thanks & Regards
>> Nagaraj Trivedi
>>
>> ____________________________________________
>> Experience certainty. IT Services
>> Business Solutions
>> Consulting
>> ____________________________________________
>> =====-----=====-----=====
>> Notice: The information contained in this e-mail
>> message and/or attachments to it may contain
>> confidential or privileged information. If you are
>> not the intended recipient, any dissemination, use,
>> review, distribution, printing or copying of the
>> information contained in this e-mail message
>> and/or attachments to it are strictly prohibited. If
>> you have received this communication in error,
>> please notify us by reply e-mail or telephone and
>> immediately and permanently delete the message
>> and any attachments. Thank you
>>
>>
>>
>
> Regards,
> Keith
>
>
>
>
>
prev parent reply other threads:[~2016-01-13 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 5:52 Nagaraj Trivedi
2016-01-11 14:57 ` Wiles, Keith
2016-01-12 10:50 ` Nagaraj Trivedi
2016-01-12 19:55 ` Wiles, Keith
2016-01-13 8:53 ` Sergio Gonzalez Monroy [this message]
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=56961098.3050505@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=keith.wiles@intel.com \
--cc=nagaraj.trivedi@tcs.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).