Age | Commit message (Collapse) | Author | Files | Lines |
|
Needed to avoid mixing package name with soversion
(lintian package-name-doesnt-match-sonames).
Change-Id: Ic00208cf8b0568d027306d487abae827b03dbabd
Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org>
|
|
Since libdpdk-dev.dirs was removed, we need to manually create the
correct includes path for libdpdk-dev.
Change-Id: I9abd78ed4567623590a1d5480df488a74787156a
Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org>
|
|
Change-Id: Ief0486ccabc1244f123fee7af03ccbfd1c67a5f2
Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org>
|
|
*updates in v2*
updated to adapt to changes we made when integrating earlier changes
This is a cleanup from the early days of dpdk packaging.
They are no more needed and not recommended if not needed according to
https://www.debian.org/doc/manuals/maint-guide/dother.en.html#dirs
The only remaining is a mkdir -p for dpdk_nic_bind which is much better
in d/rules close to the remove and relink that is done there.
Change-Id: Ife69e3fa23e5f061c86dec03d4b71d76a441e29d
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Signed-off-by: C.J. Collier <cjcollier@linuxfoundation.org>
|
|
*updates in v2*
rebased to match merge conflicts due to changes earlier in the series
make the use of tab/spaces consistent throughout the file without
discussinf or deciding which way it better (current majority wins).
Change-Id: I86de3ffff1e25b3c31d8e909896e3e8c7f771912
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
The DPKG build system adds a -Wl, to and EXTRA_LDFLAGS, by that the
flags provided by dpkg-buildflags become -Wl,-Wl,option which fails to
build.
Fix by filtering the -Wl, prefix before exporting.
Note: filtering with make text functions is hard if the pattern contains
a comma, so sed was chosen.
Change-Id: I9b91b86c80529855dfb1c5a52725c0d07a95e5c8
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
DPDK build ignores the usual way of dpdk-buildflag exports.
We have to set EXTRA_CFLAFS and EXTRA_LDFLAGS properly after setting up
and including dpdk-buildflags properly to have the control over flags a
debian package should have.
LDFLAG fPIC is now added via DEB_CFLAGS_MAINT_APPEND and fPIE disabled from
the default hardening set (incompatibility with fPIC on shared libraries)
Change-Id: I74febe97da99c338e6c3e0992c65ca4a007f381c
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
This can be very useful in the buildlog to analyze how certain flags
were set.
Change-Id: I2d80f5f5721516516c8418b7cb449ee3ac02b1d8
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
With so many changes to linking, flags and also our plan for further
optimization along the way it is useful to make the build more verbose
by default to spot issues right in the main build log.
Change-Id: I0c41d232bc7b353b9e8a91e7e3934a9b4a3a46cc
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Signed-off-by: C.J. Collier <cjcollier@linuxfoundation.org>
|
|
Following policy and fixing the warning regarding
https://lintian.debian.org/tags/package-name-doesnt-match-sonames.html
Change-Id: Ib946075ff64c0f1c30e32f7998a3aa99256ebce5
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
By using := instead of = users that rebuild our packaging can overwrite
the following via environment variables:
DPDK_CONFIG
RTE_MACHINE
RTE_TARGET
That is already used by some consumers of the Ubuntu packaging to get
optimized build, but would allow them to go on without a patch on top.
Also since it is a no-op, as long as the variables are not set, it is
fairly safe.
Change-Id: I26265c09c90d33a6e4cd37f8c26ac0ef5baac0c4
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
As discussed this shall be our initial baseline.
If history is needed for any sort of debugging or analysis it can be
found at https://code.launchpad.net/~ubuntu-server/dpdk/+git/dpdk
Change-Id: Ie95c7effbbea34d723df14f6451c1f782000cbc1
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|