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 20:40:55 +0100 [thread overview]
Message-ID: <20140307204055.2d0a4b23@skate> (raw)
In-Reply-To: <20140307174903.GE3384@free.fr>
Dear Yann E. MORIN,
On Fri, 7 Mar 2014 18:49:03 +0100, Yann E. MORIN wrote:
> Doing the check in dependencies is not much better than doing it as a
> pre-configure hook: it can be delayed quite late in the build process.
>
> > Right now i don't know how to check about the presence of the 32bit
> > support on the 64 bit host toolchain.
>
> What about something like this:
>
> ifeq ($(BR2_PACKAGE_LUAJIT),y)
> ifeq ($(TARGET_32BIT)$(HOST_64BIT),yy)
> ifneq ($(shell echo 'int main() { return 0; }' |gcc -m32 -o foo -x c - >/dev/null 2>&1 && echo y; rm -f foo),y)
> $(error Can't build luajit for 32-bit target on this machine (mising 32-bit development packages))
> endif
> endif
> endif
>
> Not really trivial, but should work with some tweaking...
Why do you invent something crazy here? We already have
BR2_HOSTARCH_NEEDS_IA32_COMPILER which tests exactly what your new test
intends to do. However, I'm not sure this test is actually completely
correct: -m32 is a x86 compiler option. And my understanding is that
Luajit needs to be built with a host that has the same bitness, so for
example building a x86-64 target on a x86 system would not work, and
your test would not catch such a situation.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-07 19:40 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 [this message]
2014-03-07 20:37 ` Fabio Porcedda
2014-03-07 20:46 ` Thomas Petazzoni
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=20140307204055.2d0a4b23@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