From: Ravi Kerur <rkerur@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Cross-compilation of bsdapp on Ubuntu
Date: Thu, 15 Jan 2015 12:30:02 -0800 [thread overview]
Message-ID: <CAFb4SLD3NjxBjHewVJnyAk-8xAdGAKXbH2OuiW+Fnghbx81ONw@mail.gmail.com> (raw)
In-Reply-To: <20150112135128.GA23467@hmsreliant.think-freely.org>
Thanks folks for the information.
On Mon, Jan 12, 2015 at 5:51 AM, Neil Horman <nhorman@tuxdriver.com> wrote:
> On Mon, Jan 12, 2015 at 11:21:32AM +0000, Bruce Richardson wrote:
> > On Fri, Jan 09, 2015 at 09:14:16AM -0800, Ravi Kerur wrote:
> > > Hi,
> > >
> > > Has anyone successfully cross compiled bsdapp on Ubuntu or other linux
> > > flavor? From the Linux documentation I see
> > >
> > > "To compile all 64-bit targets using gcc, use:
> > >
> > > make install T=x86_64*gcc"
> > >
> > > which makes me believe that bsdapp can be cross-compiled.
> >
> > Actually, I think it's just that that bit got missed in the
> documentation update
> > when we added bsd support. :-)
> > I'm not aware of anyone who has successfully built a bsdapp dpdk
> application on
> > linux or vice-version.
> >
> You're not going to be able to cross compile bsd on a linux system or vice
> versa
> unless you install system level compat libs to handle all the OS-specific
> library calls. Those exist, but its usually not worth the effort to do so.
> Just as easy/easier to install a virt guest with the appropriate operating
> system.
>
> Neil
>
> > /Bruce
> >
> > >
> > > I am trying to understand what GNU libraries and other toolchain
> > > related installation has to be done on Linux in order to get bsd
> > > successfully compiled. Inputs appreciated.
> > >
> > > Thanks,
> > >
> > > Ravi
> >
>
prev parent reply other threads:[~2015-01-15 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 17:14 Ravi Kerur
2015-01-12 11:21 ` Bruce Richardson
2015-01-12 13:51 ` Neil Horman
2015-01-15 20:30 ` Ravi Kerur [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=CAFb4SLD3NjxBjHewVJnyAk-8xAdGAKXbH2OuiW+Fnghbx81ONw@mail.gmail.com \
--to=rkerur@gmail.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.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).