Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Hash checking infrastructure
Date: Sun, 5 Jul 2015 17:03:35 +0200	[thread overview]
Message-ID: <20150705150335.GQ3647@free.fr> (raw)
In-Reply-To: <20150705095425.174bde89@core2quad.morethan.org>

Mike, all,

[Please, keep the list in Cc]

On 2015-07-05 09:54 -0500, Mike spake thusly:
> On Sun, 5 Jul 2015 16:27:27 +0200
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> 
> > And infact, I already reproduced *that* error and already sent a
> > patch: https://patchwork.ozlabs.org/patch/491307/
> 
> Tested, same set-up as previous, with this result:
> 
> ==== Successfully installed LuaJIT 2.0.4 to /usr ====
> make[1]: Leaving directory `/var1/arm/new-i386/build/host-luajit-custom'
> >>> host-luainterpreter virtual Extracting
> >>> host-luainterpreter virtual Patching
> >>> host-luainterpreter virtual Configuring
> >>> host-luainterpreter virtual Building
> >>> host-luainterpreter virtual Installing to host directory
> WARNING: no hash file for luarocks-2.2.2.tar.gz
> >>> host-luarocks 2.2.2 Extracting
> gzip -d -c /var1/arm/buildroot.git/dl/luarocks-2.2.2.tar.gz | tar --strip-components=1 -C /var1/arm/new-i386/build/host-luarocks-2.2.2  -xf -
> >>> host-luarocks 2.2.2 Patching
> >>> host-luarocks 2.2.2 Configuring
> cd /var1/arm/new-i386/build/host-luarocks-2.2.2 && ./configure --prefix=/var1/arm/new-i386/host/usr --sysconfdir=/var1/arm/new-i386/host/usr/etc/luarocks --with-lua=/var1/arm/new-i386/host/usr --lua-suffix=jit
> Checking Lua interpreter... luajit found in /var1/arm/new-i386/host/usr/bin
> Checking Lua includes... lua.h not found (looked in /var1/arm/new-i386/host/usr/include, /var1/arm/new-i386/host/usr/include/lua/5.1, /var1/arm/new-i386/host/usr/include/lua5.1)
> You may want to use the flag --with-lua or --with-lua-include. See --help.
> 
> configure failed.
> 
> make: *** [/var1/arm/new-i386/build/host-luarocks-2.2.2/.stamp_configured] Error 1
> make: Leaving directory `/var1/arm/buildroot.git'

This is expected behaviour, because the patches fronm Buildroot are
*not* applied when using an override-srcdir. This is done on-purpose, on
the assumption that the content of override-srcdir is entirely managed
by the user, and because there is *no* way for Buildroot to know if the
patches we have would still apply.

So, the new "error" you reported is totally expected.

Thanks for testing! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2015-07-05 15:03 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 [this message]
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
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=20150705150335.GQ3647@free.fr \
    --to=yann.morin.1998@free.fr \
    --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