From: Takuya ASADA <syuu@cloudius-systems.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC PATCH 5/7] add OSv support
Date: Sat, 21 Mar 2015 12:23:56 +0900 [thread overview]
Message-ID: <CAPWdggigT_qy8Mq4QrziAxtkQPXy2kD-=9fi2=EdVdK0rpL77w@mail.gmail.com> (raw)
In-Reply-To: <20150316224259.GA28909@neilslaptop.think-freely.org>
I forgot to copied rte_eal_version.map, added on new patchset.
OSv supports shared libraries, but I found that DPDK shared libraries
causes an error on OSv:
https://github.com/cloudius-systems/osv/issues/599
I'll fix it shortly.
On Tue, Mar 17, 2015 at 7:42 AM, Neil Horman <nhorman@tuxdriver.com> wrote:
> On Mon, Mar 16, 2015 at 01:21:53PM -0700, Stephen Hemminger wrote:
> > On Sun, 15 Mar 2015 08:01:22 -0400
> > Neil Horman <nhorman@tuxdriver.com> wrote:
> >
> > > On Fri, Mar 13, 2015 at 06:05:46AM +0900, Takuya ASADA wrote:
> > > > Adding OSv support.
> > > > Based on Linux/FreeBSD EAL, but calling OSv kernel APIs to access
> devices, allocate contiguous memory, etc.
> > > ><snip>
> > > > +
> > > > +include $(RTE_SDK)/mk/rte.vars.mk
> > > > +
> > > > +LIB = librte_eal.a
> > > > +
> > > > +EXPORT_MAP := rte_eal_version.map
> > > > +
> > > You never coppied over the version map. How does this build for shared
> > > libraries?
> >
> > OSv probably doesn't do shared libraries.
> >
> Ah, then do we need to add a check to prevent trying to configure shared
> libraries then?
>
> Neil
>
>
next prev parent reply other threads:[~2015-03-21 3:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 21:05 [dpdk-dev] [RFC PATCH 0/7] " Takuya ASADA
2015-03-12 21:05 ` [dpdk-dev] [RFC PATCH 1/7] mk: support compiling C++ code Takuya ASADA
2015-03-12 21:05 ` [dpdk-dev] [RFC PATCH 2/7] eal: Add extern C on eal_hugepages.h Takuya ASADA
2015-03-12 21:05 ` [dpdk-dev] [RFC PATCH 3/7] eal: Add extern C on eal_thread.h Takuya ASADA
2015-03-12 21:05 ` [dpdk-dev] [RFC PATCH 4/7] eal: Add extern C on eal_private.h Takuya ASADA
2015-03-12 21:05 ` [dpdk-dev] [RFC PATCH 5/7] add OSv support Takuya ASADA
2015-03-15 12:01 ` Neil Horman
2015-03-16 20:21 ` Stephen Hemminger
2015-03-16 22:42 ` Neil Horman
2015-03-21 3:23 ` Takuya ASADA [this message]
2015-03-12 21:05 ` [dpdk-dev] [RFC PATCH 6/7] virtio: enable MSI-X on OSv Takuya ASADA
2015-03-12 21:05 ` [dpdk-dev] [RFC PATCH 7/7] app/test: support OSv Takuya ASADA
2015-03-13 10:00 ` [dpdk-dev] [RFC PATCH 0/7] add OSv support Bruce Richardson
2015-03-13 19:00 ` Takuya ASADA
2015-03-21 3:25 ` Takuya ASADA
2015-03-13 13:42 ` Neil Horman
2015-03-13 19:39 ` Takuya ASADA
2015-03-21 3:22 ` [dpdk-dev] [RFC PATCHv2 0/8] " Takuya ASADA
2015-03-21 3:22 ` [dpdk-dev] [RFC PATCHv2 1/8] mk: support compiling C++ code Takuya ASADA
2015-03-21 3:22 ` [dpdk-dev] [RFC PATCHv2 2/8] eal: Add extern C on eal_hugepages.h Takuya ASADA
2015-03-21 3:23 ` [dpdk-dev] [RFC PATCHv2 3/8] eal: Add extern C on eal_thread.h Takuya ASADA
2015-03-21 3:23 ` [dpdk-dev] [RFC PATCHv2 4/8] eal: Add extern C on eal_private.h Takuya ASADA
2015-03-21 3:23 ` [dpdk-dev] [RFC PATCHv2 5/8] add OSv support Takuya ASADA
2015-03-24 13:52 ` Neil Horman
2015-04-06 19:01 ` Takuya ASADA
2015-03-21 3:23 ` [dpdk-dev] [RFC PATCHv2 6/8] virtio: enable MSI-X on OSv Takuya ASADA
2015-03-21 3:23 ` [dpdk-dev] [RFC PATCHv2 7/8] app/test: support OSv Takuya ASADA
2015-03-21 3:23 ` [dpdk-dev] [RFC PATCHv2 8/8] doc: Add Getting Started Guide for OSv Takuya ASADA
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='CAPWdggigT_qy8Mq4QrziAxtkQPXy2kD-=9fi2=EdVdK0rpL77w@mail.gmail.com' \
--to=syuu@cloudius-systems.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).