From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/pkg-meson: fix meson cpu_family format
Date: Mon, 25 Feb 2019 20:35:01 +0100 [thread overview]
Message-ID: <20190225203501.3af08ef8@gmx.net> (raw)
In-Reply-To: <20190225005245.1954-1-james.hilliard1@gmail.com>
Hello James,
On Mon, 25 Feb 2019 08:52:45 +0800, james.hilliard1 at gmail.com wrote:
> From: James Hilliard <james.hilliard1@gmail.com>
>
> meson requires a custom cpu_family format
> https://mesonbuild.com/Reference-tables.html#cpu-families
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> package/pkg-meson.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/pkg-meson.mk b/package/pkg-meson.mk
> index a637299476..886fcf7205 100644
> --- a/package/pkg-meson.mk
> +++ b/package/pkg-meson.mk
> @@ -64,7 +64,7 @@ define $(2)_CONFIGURE_CMDS
> rm -rf $$($$(PKG)_SRCDIR)/build
> mkdir -p $$($$(PKG)_SRCDIR)/build
> sed -e "s%@TARGET_CROSS@%$$(TARGET_CROSS)%g" \
> - -e "s%@TARGET_ARCH@%$$(ARCH)%g" \
> + -e "s%@TARGET_ARCH@%$$(HOST_MESON_TARGET_CPU_FAMILY)%g" \
> -e "s%@TARGET_CPU@%$$(GCC_TARGET_CPU)%g" \
> -e "s%@TARGET_ENDIAN@%$$(call LOWERCASE,$$(BR2_ENDIAN))%g" \
> -e "s%@TARGET_CFLAGS@%$$(HOST_MESON_SED_CFLAGS)%g" \
Doing the same for package/pgk-meson.mk as commit 'package/meson: fix CPU familly' ([1])
does for package/meson/meson.mk (and by overlapping timing this change got lost for
the 'package/pkg-meson: support per-package directories' ([2]) patch)...
Reviewed-by: Peter Seiderer <ps.report@gmx.net>
Regards,
Peter
[1] https://git.buildroot.net/buildroot/commit/?id=f3bacda0c0e0adb2ac7f515476f6bb83d1385130
[2] https://git.buildroot.net/buildroot/commit/?id=5d882b71a8c0c87b0ccdea7ad620a8f44c33fcb1
next prev parent reply other threads:[~2019-02-25 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 0:52 [Buildroot] [PATCH 1/1] package/pkg-meson: fix meson cpu_family format james.hilliard1 at gmail.com
2019-02-25 19:35 ` Peter Seiderer [this message]
2019-02-25 21:12 ` Thomas Petazzoni
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=20190225203501.3af08ef8@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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