Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] luajit: only available on x86(-64) hosts
Date: Thu, 2 Nov 2017 12:04:23 +0100	[thread overview]
Message-ID: <20171102120423.0f8e5ef7@windsurf> (raw)
In-Reply-To: <20171102104520.29257-4-peter@korsgaard.com>

Hello,

On Thu,  2 Nov 2017 11:45:19 +0100, Peter Korsgaard wrote:
> The -m32 compiler flag is used for 32bit builds and host-luajit has limited
> architecture support, so limit to x86(-64) hosts.
> 
> Fixes:
> http://autobuild.buildroot.net/results/5f5b5edb058efe976c003678e21bcc28a87cc828/
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
>  package/luajit/Config.in | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/package/luajit/Config.in b/package/luajit/Config.in
> index 1a27c434e1..6b9c6e6ae8 100644
> --- a/package/luajit/Config.in
> +++ b/package/luajit/Config.in
> @@ -1,5 +1,8 @@
>  config BR2_PACKAGE_LUAJIT_ARCH_SUPPORTS
>  	bool
> +	# -m32 flag is used for 32bit builds and host-luajit has
> +	# limited architecture support
> +	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
>  	default y if BR2_i386 || \
>  		(BR2_x86_64 && BR2_HOSTARCH='x86_64') || \
>  		BR2_powerpc || BR2_arm || BR2_armeb || \

How is this going to prevent other packages from depending on
host-luajit. BR2_PACKAGE_LUAJIT_ARCH_SUPPORTS is all about the target
variant of luajit, not the host variant.

Do we need a BR2_PACKAGE_HOST_LUAJIT_ARCH_SUPPORTS or something like
that ?

For example, if you enable moarvm, host-luajit will be built, but not
luajit.

Don't we have a problem here if your solution is used ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-11-02 11:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 10:45 [Buildroot] [PATCH 0/4] Fix BR2_HOSTARCH_NEEDS_IA32_* autobuilder issues Peter Korsgaard
2017-11-02 10:45 ` [Buildroot] [PATCH 1/4] kvm-unit-test: x86-64 variant only available on x86-64 hosts Peter Korsgaard
2017-11-05 15:44   ` Arnout Vandecappelle
2017-11-05 19:27     ` Peter Korsgaard
2017-11-05 20:23       ` Arnout Vandecappelle
2017-11-05 20:34         ` Peter Korsgaard
2017-11-26 20:33   ` Peter Korsgaard
2017-11-02 10:45 ` [Buildroot] [PATCH 2/4] ti-gfx: only available on x86(-64) hosts Peter Korsgaard
2017-11-05 16:00   ` Arnout Vandecappelle
2017-11-26 20:19   ` Peter Korsgaard
2017-11-02 10:45 ` [Buildroot] [PATCH 3/4] luajit: " Peter Korsgaard
2017-11-02 11:04   ` Thomas Petazzoni [this message]
2017-11-03 12:17     ` Peter Korsgaard
2017-11-05 15:57   ` Arnout Vandecappelle
2017-11-05 19:20     ` Peter Korsgaard
2017-11-26 20:21   ` Peter Korsgaard
2017-11-02 10:45 ` [Buildroot] [PATCH 4/4] qt5webengine: " Peter Korsgaard
2017-11-05 16:01   ` Arnout Vandecappelle
2017-11-02 14:30 ` [Buildroot] [PATCH 0/4] Fix BR2_HOSTARCH_NEEDS_IA32_* autobuilder issues Peter Korsgaard
2017-11-02 15:50   ` Baruch Siach
2017-11-02 22:01     ` Peter Korsgaard

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=20171102120423.0f8e5ef7@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --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