DPDK patches and discussions
 help / color / mirror / Atom feed
From: Victor Detoni <victordetoni@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Install DPDK on FreeBSD ports is crashing
Date: Mon, 25 May 2015 09:54:14 -0300	[thread overview]
Message-ID: <CANpwN=tz-Y7cVWvvJv-GB84GeEHrn-r0V8jVrnPVi9f2CN4j3g@mail.gmail.com> (raw)
In-Reply-To: <20150525094941.GA1656@bricha3-MOBL3>

Hi Bruce,

Thanks for your answer. The complete output is attached.

On Mon, May 25, 2015 at 6:49 AM, Bruce Richardson <
bruce.richardson@intel.com> wrote:

> On Sat, May 23, 2015 at 10:20:46PM -0300, Victor Detoni wrote:
> > Hi,
> >
> > I'm trying to install dpdk through freebsd's ports and the error is shown
> > bellow. Please, someone knows if it can install on FreeBSD 10.1? And what
> > means these errors?
> >
> > If I compile with gcc48 it works fine.
>
> Thanks for the report.
> I've tried installing from ports on my FreeBSD 10.1 system and all went
> fine for
> me. However, I'm going to install a fresh 10.1 VM and try there, in case
> I've
> missed something - as this system I've been doing DPDK development on for
> some
> time. In the meantime, can you please send me on the complete output of
> running the command: "make install clean" in /usr/ports/net/dpdk on your
> system.
>
> Thanks,
> /Bruce
>
> >
> > *  CC test_lpm.o*
> > *clang: error: unable to execute command: Killed*
> > *clang: error: clang frontend command failed due to signal (use -v to see
> > invocation)*
> > *FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032)
> 20140512*
> > *Target: x86_64-unknown-freebsd10.1*
> > *Thread model: posix*
> > *clang: note: diagnostic msg: PLEASE submit a bug report to
> > https://bugs.freebsd.org/submit/ <https://bugs.freebsd.org/submit/> and
> > include the crash backtrace, preprocessed source, and associated run
> > script.*
> > *clang: note: diagnostic msg: *
> > **********************
> >
> > *PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:*
> > *  eprocessed source(s) and associated run script(s) are located at:*
> > *?lang: note: diagnostic msg: /tmp/test_lpm-441ce1.c*
> > *clang: note: diagnostic msg: /tmp/test_lpm-441ce1.sh*
> > *clang: note: diagnostic msg: *
> >
> > **********************
> > */usr/ports/net/dpdk/work/dpdk-2.0.0/mk/internal/rte.compile-pre.mk:126
> > <http://rte.compile-pre.mk:126>: recipe for target 'test_lpm.o' failed*
> > *gmake[6]: *** [test_lpm.o] Error 254*
> > */usr/ports/net/dpdk/work/dpdk-2.0.0/mk/rte.subdir.mk:61
> > <http://rte.subdir.mk:61>: recipe for target 'test' failed*
> > *gmake[5]: *** [test] Error 2*
> > */usr/ports/net/dpdk/work/dpdk-2.0.0/mk/rte.sdkbuild.mk:93
> > <http://rte.sdkbuild.mk:93>: recipe for target 'app' failed*
> > *gmake[4]: *** [app] Error 2*
> > */usr/ports/net/dpdk/work/dpdk-2.0.0/mk/rte.sdkroot.mk:124
> > <http://rte.sdkroot.mk:124>: recipe for target 'all' failed*
> > *gmake[3]: *** [all] Error 2*
> > */usr/ports/net/dpdk/work/dpdk-2.0.0/mk/rte.sdkinstall.mk:58
> > <http://rte.sdkinstall.mk:58>: recipe for target
> > 'x86_64-native-bsdapp-clang_install' failed*
> > *gmake[2]: *** [x86_64-native-bsdapp-clang_install] Error 2*
> > */usr/ports/net/dpdk/work/dpdk-2.0.0/mk/rte.sdkroot.mk:102
> > <http://rte.sdkroot.mk:102>: recipe for target 'install' failed*
> > *gmake[1]: *** [install] Error 2*
> > *gmake[1]: Leaving directory '/usr/ports/net/dpdk/work/dpdk-2.0.0'*
> > *===> Compilation failed unexpectedly.*
> > *Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure
> > to*
> > *the maintainer.*
> > **** Error code 1*
> >
> > *Stop.*
> > *make: stopped in /usr/ports/net/dpdk*
>

  reply	other threads:[~2015-05-25 12:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24  1:20 Victor Detoni
2015-05-25  9:49 ` Bruce Richardson
2015-05-25 12:54   ` Victor Detoni [this message]
2015-05-25 13:45     ` Bruce Richardson
2015-05-29 13:44       ` Victor Detoni

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='CANpwN=tz-Y7cVWvvJv-GB84GeEHrn-r0V8jVrnPVi9f2CN4j3g@mail.gmail.com' \
    --to=victordetoni@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@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).