From: Muhammad Zain-ul-Abideen <zain2294@gmail.com>
To: santosh kumar <mail4santosh@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] need help: Compiling Dpdk on Ubuntu 14.04.1 "gcc: error: : No such file or directory" .
Date: Tue, 15 May 2018 08:53:04 +0500 [thread overview]
Message-ID: <CAN7yQ2ryuF3qMRKPpHfk5mmVR4b+=387jbHTzsTqaDrn=GkJnA@mail.gmail.com> (raw)
In-Reply-To: <CABPOvZWDw224Ruzzxynfwp+wZ7X1RfM4rB5Y3M9LQ8AD6R35yg@mail.gmail.com>
hey,
i noticed you are mixing i686 and x86. kindly share the output of
"uname -a". if its not 32 bit use 14 option.
Regards:
Zain ul Abideen
Disclaimer: The information contained in this e-mail and any
attachments is confidential; it is intended only for use of the
individual or entity named above. If the reader of this message is not
the intended recipient, you are notified that any dissemination,
distribution or use of this information is strictly prohibited. If you
have received this communication in error, please delete it and email
confirmation to the sender. Thank You.
On Mon, May 14, 2018 at 8:12 PM, santosh kumar <mail4santosh@gmail.com> wrote:
> Hi folks,
>
> could ypu please provide info for below error.
>
> while building dpdk through running ./usertools/dpdk-setup.sh , hitting
> below error
>
>
> [8] i686-native-linuxapp-gcc
>
> [9] i686-native-linuxapp-icc
>
> [10] ppc_64-power8-linuxapp-gcc
>
> [11] x86_64-native-bsdapp-clang
>
> [12] x86_64-native-bsdapp-gcc
>
> [13] x86_64-native-linuxapp-clang
>
> [14] x86_64-native-linuxapp-gcc
>
> [15] x86_64-native-linuxapp-icc
>
> [16] x86_x32-native-linuxapp-gcc
>
>
> Option: 8
>
>
> Configuration done using x86_64-native-linuxapp-gcc
> == Build lib/librte_compat
>
> == Build lib/librte_eal
>
> == Build lib/librte_eal/common
>
> == Build lib/librte_eal/linuxapp
>
> == Build lib/librte_eal/linuxapp/eal
>
> CC eal.o
>
> gcc: error: : No such file or directory
>
> make[7]: *** [eal.o] Error 1
>
> make[6]: *** [eal] Error 2
>
> make[5]: *** [linuxapp] Error 2
>
> make[4]: *** [librte_eal] Error 2
>
> make[3]: *** [lib] Error 2
>
> make[2]: *** [all] Error 2
>
> make[1]: *** [pre_install] Error 2
>
> make: *** [install] Error 2
>
> ------------------------------------------------------------------------------
>
> RTE_TARGET exported as i686-native-linuxapp-gcc
>
> ------------------------------------------------------------------------------
>
>
> Set Up :
>
> 1. Dpdk Version : dpdk-stable-17.11.2
>
> Uname -a
>
> Linux ubuntu 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:18:00
> UTC 2015 i686 i686 i686 GNU/Linux
>
> *Selected Adapter Types: Intel PRO/1000MT Server 82545EM (Virtual Box on
> Mac)*
>
>
> Regards,
>
> *Santosh Jeergi *
next prev parent reply other threads:[~2018-05-15 3:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 15:12 santosh kumar
2018-05-15 3:53 ` Muhammad Zain-ul-Abideen [this message]
2018-05-15 3:53 ` Muhammad Zain-ul-Abideen
2018-05-15 4:51 ` santosh kumar
2018-05-15 5:05 ` Muhammad Zain-ul-Abideen
2018-05-15 5:10 ` Muhammad Zain-ul-Abideen
2018-05-15 14:55 ` santosh kumar
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='CAN7yQ2ryuF3qMRKPpHfk5mmVR4b+=387jbHTzsTqaDrn=GkJnA@mail.gmail.com' \
--to=zain2294@gmail.com \
--cc=mail4santosh@gmail.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).