From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f45.google.com (mail-wr1-f45.google.com [209.85.221.45]) by dpdk.org (Postfix) with ESMTP id 361951B99A for ; Thu, 20 Dec 2018 09:03:57 +0100 (CET) Received: by mail-wr1-f45.google.com with SMTP id t6so679871wrr.12 for ; Thu, 20 Dec 2018 00:03:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:mime-version; bh=su6EKu1y0Wm/ui6paRSiygMoOqduWFtBVNvyKmx8dLE=; b=WEHv+hvzv1QnfMhkak3NHvQvQPvuVOVnZ/R+u6yXQrJXZr4aOmDbSuEjvefzcNd/oP kr4VyduDHrBLPZARQzjmgP9onZYDM5/IXofThAbN9zWAQNWR2ueQnskcPGS7mtWYBu0F tMd6QMuLOljG+JSC2be3CTc3FVKj7A1oIaY+PMi/p29XIRrF4FT2aj7qh+Hz3aFMPXar L6SzrXO3EFGuTHMpM6SKTkTz/U1KaRXHyJ6Ftu8LtoGFtzNC+OFqWCgma7/GGpDELnCy YbUHRlivE1lbkQ5hhwfTqq/cHeOAiDyxbfHI9ymzmW2kipEx8eNV/gKmi4MPqOqb97rt bfAg== X-Gm-Message-State: AA+aEWaG2c008OO6VZv7UVsUg2NKnhmu35KXtO5wTBOOey+rT0y54qim FUbHLQ0pj2Gw2Ze3S5mXmJU= X-Google-Smtp-Source: AFSGD/XL+uu1SJ259ep1IzE0fSMlYwuUw30kyNuRnzi3SkDBqiVLhDxrdEp8x12Djn/mHc/7uCeEtA== X-Received: by 2002:adf:8143:: with SMTP id 61mr20911886wrm.47.1545293036934; Thu, 20 Dec 2018 00:03:56 -0800 (PST) Received: from localhost ([46.183.103.8]) by smtp.gmail.com with ESMTPSA id j33sm11888476wre.91.2018.12.20.00.03.55 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 20 Dec 2018 00:03:56 -0800 (PST) Message-ID: <1545293033.9718.12.camel@debian.org> From: Luca Boccassi To: Ferruh Yigit , dev@dpdk.org, John McNamara , Marko Kovacevic Cc: Kevin Traynor , Yongseok Koh , Neil Horman Date: Thu, 20 Dec 2018 09:03:53 +0100 In-Reply-To: <20181219125253.77398-1-ferruh.yigit@intel.com> References: <20181219125253.77398-1-ferruh.yigit@intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Subject: Re: [dpdk-dev] [RFC 1/2] doc: clean ABI/API policy guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 08:03:57 -0000 On Wed, 2018-12-19 at 12:52 +0000, Ferruh Yigit wrote: > +=C2=A0=C2=A0=C2=A0 Application > +=C2=A0=C2=A0=C2=A0 \-> LibA.old > +=C2=A0=C2=A0=C2=A0 \-> LibB.new -> LibA.new > + > +That is a conflict which can be avoided by setting > ``CONFIG_RTE_MAJOR_ABI``. > +If set, the value of ``CONFIG_RTE_MAJOR_ABI`` overwrites all - > otherwise per > +library - versions defined in the libraries ``LIBABIVER``. > +An example might be ``CONFIG_RTE_MAJOR_ABI=3D16.11`` which will make > all libraries > +``librte.so.16.11`` instead of ``librte.so.``. This is not related to your reorganisation, but to solve this problem properly should we start considering ABI bumps as "sticky", so that in the example above _both_ libA and libB would get an ABI bump? --=20 Kind regards, Luca Boccassi