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] luajit: new package (v2)
Date: Sun, 15 Jul 2012 00:47:55 +0200	[thread overview]
Message-ID: <20120715004755.4cc159e9@skate> (raw)
In-Reply-To: <CAB0FRssEYqXNWbALe9HPGOyjkffumkOoDfS_zhj0W1d7F8-7Ow@mail.gmail.com>

Hello,

Le Sat, 2 Jun 2012 10:49:14 +0200,
Fran?ois Perrad <francois.perrad@gadz.org> a ?crit :

> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
>  package/Config.in                     |    3 ++-
>  package/luajit/Config.in              |    9 +++++++
>  package/luajit/luajit-root-path.patch |   16 ++++++++++++
>  package/luajit/luajit.mk              |   44 +++++++++++++++++++++++++++++++++
>  4 files changed, 71 insertions(+), 1 deletion(-)

I started integrating this. I made a number of changes (link the luajit
binary dynamically against its shared library, remove the symbolic
thing, addition of the proper 'depends on' for the architectures
that luajit supports, etc.).

However, I've hit a wall with the fact that apparently the luajit build
process requires the host compiler to have the same bitness as the
target architecture. As I was building for ARM on a x86_64 machine,
luajit wasn't happy, and suggested to add -m32 to the host compile
flags. With this, it works.

Unfortunately, it has a number of drawbacks:

 * Requires the host to have multilib libraries available. This is not
   a big problem IMO, as most x86_64 machines will most likely have the
   32 bits libraries installed for one reason or another, and we are
   anyway thinking of using this multilib capability to build Grub when
   the target architecture is x86_64.

 * The major problem is that it means that if your build machine is a 32
   bits machine, then you cannot build luajit for a 64 bits
   architecture (at the moment, the only 64 bits architecture supported
   by luajit is x86_64, so basically, on a i386 build machine, you
   can't build a x86_64 target).

Can you have a look at this and see what's possible to do? I will send
as a reply the current state of the luajit patch that includes my
modifications.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-07-14 22:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-02  8:49 [Buildroot] [PATCH] luajit: new package (v2) François Perrad
2012-07-14 22:47 ` Thomas Petazzoni [this message]
2012-07-14 22:50   ` [Buildroot] [PATCH] luajit: new package Thomas Petazzoni
2012-07-15 17:19     ` François Perrad
2012-07-15 18:00       ` Thomas Petazzoni
2012-07-17  8:07         ` François Perrad
2012-07-17  8:11           ` Thomas Petazzoni
2012-07-17 10:10             ` François Perrad

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=20120715004755.4cc159e9@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