From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] luvi: build for the right MIPS endianness
Date: Wed, 20 Jan 2016 00:09:26 +0100 [thread overview]
Message-ID: <569EC226.7060700@mind.be> (raw)
In-Reply-To: <1453133375-54831-1-git-send-email-Vincent.Riera@imgtec.com>
On 18-01-16 17:09, Vicente Olivert Riera wrote:
> Otherwise it will cause build failures like this one:
>
> [100%] Linking C executable luvi
> /home/buildroot/autobuild/run/instance-2/output/host/opt/ext-toolchain/bin/../lib/gcc/mipsel-buildroot-linux-gnu/5.2.0/../../../../mipsel-buildroot-linux-gnu/bin/ld:
> jitted_tmp/src/lua/init.lua_luvi_generated.o: compiled for a big endian
> system and target is little endian
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> package/luvi/luvi.mk | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/package/luvi/luvi.mk b/package/luvi/luvi.mk
> index ef1c2e1..d83933e 100644
> --- a/package/luvi/luvi.mk
> +++ b/package/luvi/luvi.mk
> @@ -20,8 +20,10 @@ else ifeq ($(BR2_powerpc),y)
> LUVI_TARGET_ARCH = ppc
> else ifeq ($(BR2_arm)$(BR2_armeb),y)
> LUVI_TARGET_ARCH = arm
> -else ifeq ($(BR2_mips)$(BR2_mipsel),y)
> +else ifeq ($(BR2_mips),y)
> LUVI_TARGET_ARCH = mips
> +else ifeq ($(BR2_mipsel),y)
> +LUVI_TARGET_ARCH = mipsel
This could just fall into the BR2_ARCH situation below, no?
Regards,
Arnout
> else
> LUVI_TARGET_ARCH = $(BR2_ARCH)
> endif
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2016-01-19 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 16:09 [Buildroot] [PATCH] luvi: build for the right MIPS endianness Vicente Olivert Riera
2016-01-19 21:00 ` Thomas Petazzoni
2016-01-19 23:09 ` Arnout Vandecappelle [this message]
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=569EC226.7060700@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.