From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] luajit: new package
Date: Sun, 15 Jul 2012 20:00:56 +0200 [thread overview]
Message-ID: <20120715200056.390b3d03@skate> (raw)
In-Reply-To: <CAB0FRsv-bQnLUZvq_8xm4CkQsbxF3z6quUW5jwGhhbr0KK6nZQ@mail.gmail.com>
Le Sun, 15 Jul 2012 19:19:03 +0200,
Fran?ois Perrad <francois.perrad@gadz.org> a ?crit :
> -Wl,-rpath,/home/user/build/qarm/host/usr/lib" -C
> /home/user/build/qarm/build/luajit-2.0.0-beta10 amalg
> /usr/bin/make: invalid option -- '3'
> /usr/bin/make: invalid option -- '2'
>
> so, I remove extra quote :
> ifeq ($(BR2_ARCH_IS_64),y)
> LUAJIT_HOST_CC=$(HOSTCC)
> else
> LUAJIT_HOST_CC=$(HOSTCC) -m32
> endif
Hum, yes, this part was a last-minute addition, which was wrong
apparently. But this doesn't answer my initial question: it is not
possible to build luajit for a 64 bits architecture on a 32 bits host.
If this isn't solved, we can't include luajit as is.
> and the build command could be rewrite with CROSS :
> define LUAJIT_BUILD_CMDS
> $(MAKE) PREFIX="/usr" \
> HOST_CC="$(LUAJIT_HOST_CC)" \
> CROSS="$(TARGET_CROSS)" \
> -C $(@D) amalg
> endef
No, using TARGET_CROSS directly doesn't work when ccache is enabled.
ccache is only used in TARGET_CC and TARGET_CXX, that's why I've done
this this way.
Can you look at the bitness problem?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-15 18:00 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
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 [this message]
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=20120715200056.390b3d03@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