From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2016-08-23
Date: Sat, 27 Aug 2016 01:43:42 +0200 [thread overview]
Message-ID: <1472255022.3670.11.camel@embedded.rocks> (raw)
In-Reply-To: <20160824172543.36D1D10CEEE@stock.ovh.net>
Hi,
On Mi, 2016-08-24 at 19:25 +0200, Thomas Petazzoni wrote:
> Hello,
>
> This is the list of Buildroot build failures that occured on
> 2016-08-23, and for which you are a registered architecture developer
> or package developer. Please help us improving the quality of
> Buildroot by investigating those build failures and sending patches
> to
> fix them. Thanks!
>
> Build failures related to your packages:
>
> ??????mipsel |????????????????????luvi-v2.7.5 | http://autobuild.buil
> droot.net/results/8e001112b1678f9fb1c198c84184cd6f5fc3d004
>
Incompatible object files:
file luvi-v2.7.5/jitted_tmp/src/lua/init.lua_luvi_generated.o: ELF 32-
bit LSB relocatable, MIPS, MIPS32 version 1 (SYSV), not stripped
luvi-v2.7.5/CMakeFiles/luvi.dir/src/main.c.o: ELF 32-bit LSB
relocatable, MIPS, MIPS32 rel6 version 1 (SYSV), not stripped
I'm not sure if LuaJIT is able to output object files for MIPS32R6, so
I asked on the LuaJIT mailing list [1]. If not, we have to exclude the
MIPS32R6 architecture from LuaJIT arch support, right?
[1]?http://www.freelists.org/post/luajit/Support-for-MIPS32r6
Best regards
J?rg Krause
next parent reply other threads:[~2016-08-26 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160824172543.36D1D10CEEE@stock.ovh.net>
2016-08-26 23:43 ` Jörg Krause [this message]
2016-08-27 7:59 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2016-08-23 Thomas Petazzoni
[not found] <20160824172543.21E4E10CE3A@stock.ovh.net>
2016-08-26 16:57 ` André Hentschel
2016-08-26 17:46 ` Thomas Petazzoni
[not found] <20160824172543.19BA410CCE6@stock.ovh.net>
2016-08-26 9:20 ` Rahul Bedarkar
2016-08-26 9:44 ` Thomas Petazzoni
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=1472255022.3670.11.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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