From: Fred Pedrisa <fredhps10@hotmail.com>
To: "'Randall Stewart'" <rrs@lakerest.net>, <dev@dpdk.org>
Subject: [dpdk-dev] RES: Attempting to get the DPDK to build for FreeBSD 9.2Release DPDK 1.6.0
Date: Thu, 27 Mar 2014 10:51:11 -0300 [thread overview]
Message-ID: <COL131-DS1F80B08711BFB9E987C7DB0670@phx.gbl> (raw)
In-Reply-To: <02e401cf49af$9bfb35f0$d3f1a1d0$@lakerest.net>
Hello,
Im my first attempt, I had to restart the server :D
-----Mensagem original-----
De: dev [mailto:dev-bounces@dpdk.org] Em nome de Randall Stewart
Enviada em: quinta-feira, 27 de março de 2014 08:26
Para: dev@dpdk.org
Assunto: Re: [dpdk-dev] Attempting to get the DPDK to build for FreeBSD
9.2Release DPDK 1.6.0
Ok
I have figured this one out ;-)
When you do
kldload ./contigmem.ko
It trys to malloc up a chunk of memory (1Gig it looks by default).. and if a
contiguious piece of memory is not available.. it fails.. which causes the
failure back to kldload that says “Exec format error”.
Not very descriptive, turns out you have to dig into /var/log/messages to
figure out what is really happening ;-)
R
On Mar 27, 2014, at 7:05 AM, Randall Stewart <rrs@lakerest.net> wrote:
>
>>
>> Hi all:
>>
>> I have a stock 9.2Release FreeBSD system and am attempting to build
>> the DPDK for it. I have followed the steps i.e:
>>
>> 1) Gotten the ports in:
>> - dialog4ports
>> - gcc 4.8
>> - gmake
>> - coreutils
>> - libexecinfo
>>
>> 2) Ran the make
>> - gmake install T=x86_64-default-bsdapp-gcc CC=gcc48
>>
>> It completes nicely and I have a x86_64-default-bsdapp-gcc directory with
all the goodies.
>> But here is the issue:
>>
>> bash-fastone: cd x86_64-default-bsdapp-gcc/kmod/
>> bash-fastone: su
>> Password:
>> root@fastone:/usr/randall/DPDK-1.6.0/x86_64-default-bsdapp-gcc/kmod # ls
>> contigmem.ko nic_uio.ko
>> root@fastone:/usr/randall/DPDK-1.6.0/x86_64-default-bsdapp-gcc/kmod #
>> kldload ./contigmem.ko
>> kldload: can't load ./contigmem.ko: Exec format error
>> root@fastone:/usr/randall/DPDK-1.6.0/x86_64-default-bsdapp-gcc/kmod #
>>
>>
>>
>> Anyone ever seen this? Per chance am I missing something?
>>
>> I guess my next step is to see if I can build the klm’s individually
>> with a more BSDish setup to see if there is some sort of interaction
>> going on here between gcc and gcc48.. hmmm
>>
>> Any pointers would be appreciated.
>>
>> Thanks
>>
>> R
>
> ------------------------------
> Randall Stewart
> 803-317-4952 (cell)
>
>
------------------------------
Randall Stewart
803-317-4952 (cell)
prev parent reply other threads:[~2014-03-27 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1B57BBB-C669-483F-B063-D377FD6AEF6B@adaranetworks.com>
2014-03-27 11:05 ` [dpdk-dev] Fwd: " Randall Stewart
2014-03-27 11:25 ` [dpdk-dev] " Randall Stewart
[not found] ` <02e401cf49af$9bfb35f0$d3f1a1d0$@lakerest.net>
2014-03-27 13:51 ` Fred Pedrisa [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=COL131-DS1F80B08711BFB9E987C7DB0670@phx.gbl \
--to=fredhps10@hotmail.com \
--cc=dev@dpdk.org \
--cc=rrs@lakerest.net \
/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).