Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike <mikez@OpenPlayer.org>
To: buildroot@busybox.net
Subject: [Buildroot] Hash checking infrastructure
Date: Sun, 5 Jul 2015 07:15:26 -0500	[thread overview]
Message-ID: <20150705071526.64f5a6df@core2quad.morethan.org> (raw)
In-Reply-To: <20150705094452.GI3647@free.fr>

On Sun, 5 Jul 2015 11:44:52 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Mike, All,
> 
> On 2015-07-05 00:00 -0500, Mike spake thusly:
> [--SNIP--]
> > I fell into this strange behavior when trying a simple(tm)
> > LuaJIT version bump (from 2.0.3 -> 2.0.4).
> 
> Note that we already have luajit 2.0.4 in Buildroot.
> 
> Regards,
> Yann E. MORIN.
> 

@Thomas P & Yann -
Thanks for checking and reporting no problems.
I presume you where both using the current head.

I have been working on this for a few days now,
so my work was against the head of a few days ago.

I.E: Back in the "old days" (hours?) when it still
had only 2.0.3 in it.

- - - -

I don't see any signs of enabling a Lua module in
the .config snippet that Thomas P. sent.

Not just any Lua module, but one that uses the
LuaRocks infrastructure.

Why?
Because to install the host LuaRocks infrastructure
causes a host-Lua to be built.

At the moment, I am thinking that part is what falls
into the hash checking of a non-existent tar-ball.

The related part of my .config:

BR2_LUAROCKS_MIRROR="http://rocks.moonscript.org"
# BR2_PACKAGE_LUA is not set
BR2_PACKAGE_PROVIDES_LUAINTERPRETER="luajit"
BR2_PACKAGE_LUAINTERPRETER_ABI_VERSION="5.1"
BR2_PACKAGE_HAS_LUAINTERPRETER=y
BR2_PACKAGE_LUAJIT_ARCH_SUPPORTS=y
BR2_PACKAGE_LUAJIT=y

# Right here is the significant difference:
BR2_PACKAGE_LUALOGGING=y
BR2_PACKAGE_LUAPOSIX=y

- - - - -

Which is why my question about the auto-builder:

Once it had picked one of the Lua providers, did
it also go on to pick some (or all) of the Lua
modules.

From the lack of noise on the subject in the
auto-builder reports, I suspect not.

I.E: Some of the modules do not properly set
Lua-Include-Path (however named) and they just
are not going to build that way.  ;)

- - - - -

Come Monday morning, I'll do a pull to pick up the
recent changes made when the version was bump'd.

Then start over.

Thanks again,
Mike

  reply	other threads:[~2015-07-05 12:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-04 19:01 [Buildroot] Hash checking infrastructure Mike
2015-07-04 21:47 ` Yann E. MORIN
2015-07-05  2:36   ` Mike
2015-07-05  5:00     ` Mike
2015-07-05  9:10       ` Thomas Petazzoni
2015-07-05  9:42         ` Yann E. MORIN
2015-07-05 13:32         ` Mike
2015-07-05 14:27           ` Yann E. MORIN
     [not found]             ` <20150705095425.174bde89@core2quad.morethan.org>
2015-07-05 15:03               ` Yann E. MORIN
2015-07-05 16:56                 ` [Buildroot] host-luarocks include path does not match installation of host-luajit Mike
2015-07-05 17:09                   ` Yann E. MORIN
2015-07-05  9:44       ` [Buildroot] Hash checking infrastructure Yann E. MORIN
2015-07-05 12:15         ` Mike [this message]
2015-07-05 12:27           ` Mike

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=20150705071526.64f5a6df@core2quad.morethan.org \
    --to=mikez@openplayer.org \
    --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