From: Mike <mikez@OpenPlayer.org>
To: buildroot@busybox.net
Subject: [Buildroot] host-luarocks include path does not match installation of host-luajit
Date: Sun, 5 Jul 2015 11:56:17 -0500 [thread overview]
Message-ID: <20150705115617.76d410a2@core2quad.morethan.org> (raw)
In-Reply-To: <20150705150335.GQ3647@free.fr>
On Sun, 5 Jul 2015 17:03:35 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > >>> 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
That is the luarocks package that is reporting that it can not
find 'lua.h'.
Only LuaJIT is in an external source directory, and it installed
just fine, with your proposed patch.
There is just a mis-match between where host-luajit was installed
and where host-luarocks is expecting them.
- - - - -
Translation: One problem fixed, now exposes another one.
Hah!
And someone commented on how the title of this thread does
not strictly apply.
So I changed the title, but kept the same threading.
Mike
next prev parent reply other threads:[~2015-07-05 16:56 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 ` Mike [this message]
2015-07-05 17:09 ` [Buildroot] host-luarocks include path does not match installation of host-luajit 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=20150705115617.76d410a2@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