From: Thomas Monjalon <thomas@monjalon.net>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: david.marchand@redhat.com, Honnappa.Nagarahalli@arm.com,
Ruifeng.Wang@arm.com, ferruh.yigit@intel.com,
jerinjacobk@gmail.com, dev@dpdk.org
Subject: Re: [PATCH v3 0/4] arm64 cross docs improvements/fixes
Date: Wed, 16 Mar 2022 20:19:00 +0100 [thread overview]
Message-ID: <8533270.T7Z3S40VBb@thomas> (raw)
In-Reply-To: <1643116802-26466-1-git-send-email-juraj.linkes@pantheon.tech>
25/01/2022 14:19, Juraj Linkeš:
> The docs are a bit outdated and in need of updates.
>
> Using CFLAGS and LDFLAGS is an artefact of the old build system, Meson
> doesn't support those well.
>
> Numaclt can't be cross compiled with clang.
>
> The names of downloaded binaried have an extra -none- in them.
>
> And to make these changes more easily understandable, add an example
> cross file.
>
> v3: rebase and minor reformat in:
> doc: arm64 cross build CFLAGS/LDFLAGS alternatives
> docs: add an example arm64 cross file
>
> Juraj Linkeš (4):
> doc: arm64 cross build CFLAGS/LDFLAGS alternatives
> doc: arm64 cross build binary names update
> doc: arm64 cross build numactl compilers
> doc: add an example arm64 cross file
Improved details (like line wrapping and uppercases),
and applied, thanks.
prev parent reply other threads:[~2022-03-16 19:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 10:00 [PATCH v1] doc: arm64 cross docs improvements/fixes Juraj Linkeš
2021-11-26 13:53 ` Thomas Monjalon
2021-11-26 14:17 ` Juraj Linkeš
2021-12-07 11:05 ` [PATCH v2 0/4] " Juraj Linkeš
2021-12-07 11:05 ` [PATCH v2 1/4] doc: arm64 cross build CFLAGS/LDFLAGS alternatives Juraj Linkeš
2021-12-15 8:00 ` Ruifeng Wang
2021-12-07 11:05 ` [PATCH v2 2/4] doc: arm64 cross build binary names update Juraj Linkeš
2021-12-15 8:02 ` Ruifeng Wang
2021-12-07 11:05 ` [PATCH v2 3/4] doc: arm64 cross build numactl compilers Juraj Linkeš
2021-12-15 8:38 ` Ruifeng Wang
2021-12-07 11:05 ` [PATCH v2 4/4] docs: add an example arm64 cross file Juraj Linkeš
2021-12-15 8:59 ` Ruifeng Wang
2022-01-25 13:19 ` [PATCH v3 0/4] arm64 cross docs improvements/fixes Juraj Linkeš
2022-01-25 13:19 ` [PATCH v3 1/4] doc: arm64 cross build CFLAGS/LDFLAGS alternatives Juraj Linkeš
2022-01-25 13:20 ` [PATCH v3 2/4] doc: arm64 cross build binary names update Juraj Linkeš
2022-01-25 13:20 ` [PATCH v3 3/4] doc: arm64 cross build numactl compilers Juraj Linkeš
2022-01-25 13:20 ` [PATCH v3 4/4] doc: add an example arm64 cross file Juraj Linkeš
2022-03-16 19:19 ` Thomas Monjalon [this message]
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=8533270.T7Z3S40VBb@thomas \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinjacobk@gmail.com \
--cc=juraj.linkes@pantheon.tech \
/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.