From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Christopher Larson <chris_larson@mentor.com>
Subject: Re: [meta-oe][PATCH 2/6] luajit: fix build issues, obey more vars
Date: Mon, 30 May 2016 12:18:07 +0200 [thread overview]
Message-ID: <20160530101807.GB2588@jama> (raw)
In-Reply-To: <20160530094419.GA2588@jama>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
On Mon, May 30, 2016 at 11:44:19AM +0200, Martin Jansa wrote:
> On Sat, May 28, 2016 at 08:41:16PM -0700, Christopher Larson wrote:
> > On Tue, May 17, 2016 at 9:10 AM, Christopher Larson <kergoth@gmail.com>
> > wrote:
> >
> > > From: Christopher Larson <chris_larson@mentor.com>
> > >
> > > Rework how variables are passed in to ensure that more of our flag vars are
> > > obeyed, make it obey more of our target path vars, and use fewer of its
> > > hardcoded flags. Also add verbosity to the compile output for debugging.
> > >
> > > Without this, errors were seen for us:
> > >
> > > | In file included from
> > > .../lib/gcc/i686-pc-linux-gnu/5.2.0/include-fixed/64/sgxx-glibc/syslimits.h:7:0,
> > > | from
> > > .../lib/gcc/i686-pc-linux-gnu/5.2.0/include-fixed/64/sgxx-glibc/limits.h:34,
> > > | from luaconf.h:12,
> > > | from lua.h:16,
> > > | from lj_arch.h:9:
> > > |
> > > .../lib/gcc/i686-pc-linux-gnu/5.2.0/include-fixed/64/sgxx-glibc/limits.h:168:61:
> > > fatal error: limits.h: No such file or directory
> > > | compilation terminated.
> > > | Makefile:233: *** Unsupported target architecture. Stop.
> > > | make[1]: Leaving directory '.../luajit/2.0.4-r0/LuaJIT-2.0.4/src'
> > >
> > > Signed-off-by: Christopher Larson <chris_larson@mentor.com>
> > >
> >
> > Were there issues with this one? I noticed the other patches in this series
> > were applied, but this one wasn't.
>
> I've seen some luajit failures, but haven't confirmed if it was
> caused/related to this change yet, so I've kept it in master-next for a
> bit longer until I find time to confirm it.
FWIW: this is the one I was seeing (now reproduced in public build so
that I can actually share the log).
http://errors.yoctoproject.org/Errors/Details/68382/
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-05-30 10:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 16:10 [meta-oe][PATCH 0/6] Various fixes from meta-mentor Christopher Larson
2016-05-17 16:10 ` [meta-oe][PATCH 1/6] mg: stop relying on make -e Christopher Larson
2016-05-17 16:11 ` Christopher Larson
2016-05-17 16:10 ` [meta-oe][PATCH 2/6] luajit: fix build issues, obey more vars Christopher Larson
2016-05-29 3:41 ` Christopher Larson
2016-05-29 3:43 ` Christopher Larson
2016-05-30 9:44 ` Martin Jansa
2016-05-30 10:18 ` Martin Jansa [this message]
2016-05-31 17:38 ` [meta-oe][PATCHv2] " Christopher Larson
2016-05-17 16:10 ` [meta-oe][PATCH 3/6] openlmi-networking: add missing dep on konkretcmpi-native Christopher Larson
2016-05-17 16:10 ` [meta-oe][PATCH 4/6] networkmanager: add missing dep on intltool-native Christopher Larson
2016-05-17 16:10 ` [meta-oe][PATCH 5/6] networkmanager: add missing dep on dbus-glib-native Christopher Larson
2016-05-17 16:10 ` [meta-oe][PATCH 6/6] x11vnc: remove old libtool macros from acinclude.m4 Christopher Larson
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=20160530101807.GB2588@jama \
--to=martin.jansa@gmail.com \
--cc=chris_larson@mentor.com \
--cc=openembedded-devel@lists.openembedded.org \
/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