DPDK patches and discussions
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Jan Blunck <jblunck@infradead.org>
Cc: dev <dev@dpdk.org>,
	 "cjcollier @ linuxfoundation . org"
	<cjcollier@linuxfoundation.org>,
	ricardo.salveti@linaro.org,
	Luca Boccassi <luca.boccassi@gmail.com>
Subject: Re: [dpdk-dev] [PATCH] mk: Provide option to set Major ABI version
Date: Wed, 1 Mar 2017 10:31:19 +0100	[thread overview]
Message-ID: <CAATJJ0+1axb8aWOb30qoRB2LMNHNU4KNOPLbsgMVxfPdEvq15g@mail.gmail.com> (raw)
In-Reply-To: <CALe+Z00fkiaQ5uspGZ1kE9gnOvDPLZ5h=vgDswL3nM85pEPGQA@mail.gmail.com>

On Tue, Feb 28, 2017 at 9:34 AM, Jan Blunck <jblunck@infradead.org> wrote:

> In case CONFIG_RTE_NEXT_ABI=y is set this is actually generating
> shared objects with suffix:
>
>   .so.$(CONFIG_RTE_MAJOR_ABI).1
>
> I don't think that this is the intention.
>

You are right, thanks for the catch Jan!
The fix is a trivial extra ifeq - a V2 is on the way soon.


-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

  reply	other threads:[~2017-03-01  9:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 10:52 [dpdk-dev] Further fun with ABI tracking Christian Ehrhardt
2017-02-14 16:19 ` Bruce Richardson
2017-02-14 20:31 ` Jan Blunck
2017-02-22 13:12   ` Christian Ehrhardt
2017-02-22 13:24     ` [dpdk-dev] [PATCH] mk: Provide option to set Major ABI version Christian Ehrhardt
2017-02-28  8:34       ` Jan Blunck
2017-03-01  9:31         ` Christian Ehrhardt [this message]
2017-03-01  9:34           ` [dpdk-dev] [PATCH v2] " Christian Ehrhardt
2017-03-01 14:35             ` Jan Blunck
2017-03-16 17:19               ` Thomas Monjalon
2017-03-17  8:27                 ` Christian Ehrhardt
2017-03-17  9:16                   ` Jan Blunck
2017-02-23 18:48     ` [dpdk-dev] Further fun with ABI tracking Ferruh Yigit
2017-02-24  7:32       ` Christian Ehrhardt

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=CAATJJ0+1axb8aWOb30qoRB2LMNHNU4KNOPLbsgMVxfPdEvq15g@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=cjcollier@linuxfoundation.org \
    --cc=dev@dpdk.org \
    --cc=jblunck@infradead.org \
    --cc=luca.boccassi@gmail.com \
    --cc=ricardo.salveti@linaro.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).