From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, dpdk@stormmq.com, bruce.richardson@intel.com,
stephen@networkplumber.org
Subject: Re: [PATCH v3 0/7] Improve core EAL musl compatibility
Date: Mon, 22 Oct 2018 11:33:38 +0200 [thread overview]
Message-ID: <2217631.WZYK2fGq3V@xps> (raw)
In-Reply-To: <cover.1538648134.git.anatoly.burakov@intel.com>
04/10/2018 12:20, Anatoly Burakov:
> This patchset fixes numerous issues with musl compatibility
> in the core EAL libraries. It does not fix anything beyond
> core EAL (so, PCI driver is still broken, so are a few other
> drivers), but it's a good start.
>
> Tested on container with Alpine Linux. Alpine dependencies:
>
> build-base bsd-compat-headers libexecinfo-dev linux-headers numactl-dev
>
> For numactl-dev, testing repository needs to be enabled:
>
> echo "http://dl-cdn.alpinelinux.org/alpine/edge/testing" >> /etc/apk/repositories
>
> If successful (using a very broad definition of "success"),
> the build should fail somewhere in PCI bus driver in UIO.
>
> v3 -> v2:
> - Made _GNU_SOURCE unconditional for all DPDK targets
> - Fixed usage of __USE_GNU and _GNU_SOURCE accross DPDK
>
> v2 -> v1:
> - Fixed patch 2 to use existing define if available
> - Fixed patch 7 to use proper format specifier and
> cast pthread ID to unsigned pointer type
>
> Anatoly Burakov (7):
> mk: build with _GNU_SOURCE defined by default
> pci/vfio: improve musl compatibility
> fbarray: improve musl compatibility
> eal/hugepage_info: improve musl compatibility
> mem: improve musl compatibility
> string_fns: improve musl compatibility
> eal: improve musl compatibility
Applied, thanks
Hope the _GNU_SOURCE source won't bring too much compilation surprises.
next prev parent reply other threads:[~2018-10-22 9:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 11:56 [PATCH 0/7] Improve core EAL musl compatibility Anatoly Burakov
2018-08-29 11:56 ` [PATCH 1/7] linuxapp: build with _GNU_SOURCE defined by default Anatoly Burakov
2018-08-29 11:56 ` [PATCH 2/7] pci/vfio: improve musl compatibility Anatoly Burakov
2018-08-29 12:35 ` Bruce Richardson
2018-08-29 14:08 ` Burakov, Anatoly
2018-08-29 11:56 ` [PATCH 3/7] fbarray: " Anatoly Burakov
2018-08-29 11:56 ` [PATCH 4/7] eal/hugepage_info: " Anatoly Burakov
2018-08-29 11:56 ` [PATCH 5/7] mem: " Anatoly Burakov
2018-08-29 11:56 ` [PATCH 6/7] string_fns: " Anatoly Burakov
2018-08-29 11:56 ` [PATCH 7/7] eal: " Anatoly Burakov
2018-08-29 12:39 ` Bruce Richardson
2018-08-29 12:40 ` Bruce Richardson
2018-08-29 14:09 ` Burakov, Anatoly
2018-08-29 16:47 ` Stephen Hemminger
2018-08-30 9:13 ` Burakov, Anatoly
2018-08-29 16:43 ` Stephen Hemminger
2018-09-20 15:27 ` [PATCH v2 0/7] Improve core EAL " Anatoly Burakov
2018-09-20 15:27 ` [PATCH v2 1/7] linuxapp: build with _GNU_SOURCE defined by default Anatoly Burakov
2018-09-20 15:27 ` [PATCH v2 2/7] pci/vfio: improve musl compatibility Anatoly Burakov
2018-09-20 15:27 ` [PATCH v2 3/7] fbarray: " Anatoly Burakov
2018-09-20 15:27 ` [PATCH v2 4/7] eal/hugepage_info: " Anatoly Burakov
2018-09-20 15:27 ` [PATCH v2 5/7] mem: " Anatoly Burakov
2018-09-20 15:27 ` [PATCH v2 6/7] string_fns: " Anatoly Burakov
2018-09-20 15:27 ` [PATCH v2 7/7] eal: " Anatoly Burakov
2018-10-04 10:20 ` [PATCH v3 0/7] Improve core EAL " Anatoly Burakov
2018-10-04 10:20 ` [PATCH v3 1/7] mk: build with _GNU_SOURCE defined by default Anatoly Burakov
2018-10-04 10:20 ` [PATCH v3 2/7] pci/vfio: improve musl compatibility Anatoly Burakov
2018-10-04 10:20 ` [PATCH v3 3/7] fbarray: " Anatoly Burakov
2018-10-04 10:20 ` [PATCH v3 4/7] eal/hugepage_info: " Anatoly Burakov
2018-10-04 10:20 ` [PATCH v3 5/7] mem: " Anatoly Burakov
2018-10-04 10:20 ` [PATCH v3 6/7] string_fns: " Anatoly Burakov
2018-10-04 10:20 ` [PATCH v3 7/7] eal: " Anatoly Burakov
2018-10-22 9:33 ` Thomas Monjalon [this message]
2018-09-28 15:25 ` [PATCH 0/7] Improve core EAL " Bruce Richardson
2018-10-03 22:56 ` Thomas Monjalon
2018-10-04 9:15 ` Burakov, Anatoly
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=2217631.WZYK2fGq3V@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dpdk@stormmq.com \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.