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] luajit package fails to build on x86_64 for x86
Date: Fri, 7 Mar 2014 21:46:51 +0100	[thread overview]
Message-ID: <20140307214651.1cb85457@skate> (raw)
In-Reply-To: <CAHkwnC8GuQJaRaqw_0A1KNNaFyz4scJBzsALRGx0ounsg7Y5mQ@mail.gmail.com>

Dear Fabio Porcedda,

On Fri, 7 Mar 2014 21:37:14 +0100, Fabio Porcedda wrote:

> diff --git a/package/luajit/Config.in b/package/luajit/Config.in
> index 9c4ecc3..d0c1512 100644
> --- a/package/luajit/Config.in
> +++ b/package/luajit/Config.in
> @@ -4,6 +4,7 @@ config BR2_PACKAGE_LUAJIT
>         # Luajit is only available for some target architectures, and
>         # has some complexity wrt 32/64. See luajit.mk for details.
>         depends on BR2_i386 || (BR2_x86_64 && BR2_HOSTARCH='x86_64')
> || BR2_powerpc || BR2_arm || BR2_armeb
> +       select BR2_HOSTARCH_NEEDS_IA32_COMPILER if !BR2_x86_64

This will prevent building Luajit for ARM, while running Buildroot on
an ARM platform. It's fairly unlikely, but still. "gcc -m32" will only
work on x86, or x86-64 with the 32 bits development files installed.
While in fact Luajit can build in situation where the bitness of the
target and the bitness of the arch match.

For example, Peter has one PowerPC build server: a "gcc -m32" test
would fail on it, even though it would be perfectly capable of building
the ARM 32 bits, PowerPC or x86 Luajit.

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

  reply	other threads:[~2014-03-07 20:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 10:43 [Buildroot] luajit package fails to build on x86_64 for x86 Fabio Porcedda
2014-03-06 20:51 ` François Perrad
2014-03-07 10:19   ` Fabio Porcedda
2014-03-06 21:31 ` Yann E. MORIN
2014-03-07  9:59   ` Fabio Porcedda
2014-03-07 17:21     ` Yann E. MORIN
2014-03-07 17:32       ` Fabio Porcedda
2014-03-07 17:49         ` Yann E. MORIN
2014-03-07 19:40           ` Thomas Petazzoni
2014-03-07 20:37             ` Fabio Porcedda
2014-03-07 20:46               ` Thomas Petazzoni [this message]
2014-03-07 20:51                 ` Fabio Porcedda
2014-03-07 20:58                   ` Thomas Petazzoni
2014-03-07 21:11                     ` Fabio Porcedda
2014-03-07 21:30                       ` Thomas Petazzoni
2014-03-07 21:58                         ` Fabio Porcedda
2014-03-07 22:19                           ` Fabio Porcedda
2014-03-07 21:38             ` Yann E. MORIN

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=20140307214651.1cb85457@skate \
    --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