From: Mike Crowe <mac@mcrowe.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Remove unhelpful default value of EXTRA_OEMAKE
Date: Sun, 7 Feb 2016 22:07:41 +0000 [thread overview]
Message-ID: <20160207220741.GA12339@mcrowe.com> (raw)
In-Reply-To: <20160206204110.GA21969@mcrowe.com>
Further to my previous response, I've tried another build with qemuarm this
time and more layers enabled.
> On Saturday 06 February 2016 at 18:32:18 +0100, Martin Jansa wrote:
> > /home/jenkins/oe/world/shr-core/meta-openembedded/meta-multimedia/recipes-mkv/libebml/libebml_1.3.0.bb,
> > /home/jenkins/oe/world/shr-core/meta-openembedded/meta-networking/recipes-connectivity/vlan/vlan_1.9.bb,
> > /home/jenkins/oe/world/shr-core/meta-openembedded/meta-networking/recipes-protocols/pptp-linux/pptp-linux_1.7.2.bb,
> > /home/jenkins/oe/world/shr-core/meta-openembedded/meta-networking/recipes-support/pimd/pimd_2.1.8.bb,
These recipes all appear to require EXTRA_OEMAKE = "-e MAKEFLAGS=". I have
patches ready to post.
I also saw similar failures with vsftpd and vpnc which you didn't see for
some reason. I have patches ready for those too.
> > /home/jenkins/oe/world/shr-core/meta-openembedded/meta-initramfs/recipes-devtools/klibc/klibc_2.0.4.bb,
> > /home/jenkins/oe/world/shr-core/meta-openembedded/meta-oe/recipes-support/soci/soci_3.2.2.bb,
> > virtual:native:/home/jenkins/oe/world/shr-core/meta-openembedded/meta-oe/recipes-extended/libwmf/libwmf_0.2.8.4.bb,
> > /home/jenkins/oe/world/shr-core/meta-openembedded/meta-oe/recipes-devtools/cunit/cunit_2.1-3.bb,
> > /home/jenkins/oe/world/shr-core/meta-openembedded/meta-networking/recipes-irc/znc/znc_git.bb,
These recipes all compiled successfully for me with EXTRA_OEMAKE = "".
Perhaps they are non-deterministic or they failed for you for other reasons?
> > /home/jenkins/oe/world/shr-core/meta-openembedded/meta-oe/recipes-support/libtinyxml2/libtinyxml2_git.bb,
This recipe doesn't appear to call oe_runmake. It failed to compile for me
even after explicitly setting EXTRA_OEMAKE back to "-e MAKEFLAGS=".
> > /home/jenkins/oe/world/shr-core/meta-openembedded/meta-networking/recipes-extended/iscsitarget/iscsitarget_1.4.20.3+svn502.bb,
This recipe fails to compile for me too but it doesn't seem to be related
to EXTRA_OEMAKE. I think it can't find the kernel headers it needs which
may be due to an error in my configuration.
> > /home/jenkins/oe/world/shr-core/meta-smartphone/meta-android/recipes-support/invensense/invensense_git.bb,
I haven't yet tried meta-android.
Thanks.
Mike.
next prev parent reply other threads:[~2016-02-07 22:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 14:49 [PATCH 0/3] Remove unhelpful default value of EXTRA_OEMAKE Mike Crowe
2016-02-02 14:49 ` [PATCH 1/3] openssl: Explicitly set EXTRA_OEMAKE as required Mike Crowe
2016-02-02 14:49 ` [PATCH 2/3] pciutils: " Mike Crowe
2016-02-02 14:49 ` [PATCH 3/3] bitbake.conf: Remove unhelpful default value for EXTRA_OEMAKE Mike Crowe
2016-02-16 12:28 ` Richard Purdie
2016-02-02 16:01 ` [PATCH 0/3] Remove unhelpful default value of EXTRA_OEMAKE Richard Purdie
2016-02-02 16:17 ` Martin Jansa
2016-02-06 17:32 ` Martin Jansa
2016-02-06 20:41 ` Mike Crowe
2016-02-07 22:07 ` Mike Crowe [this message]
2016-02-08 0:07 ` Martin Jansa
2016-02-09 10:39 ` Martin Jansa
2016-02-09 12:30 ` Mike Crowe
2016-02-09 12:51 ` Andrea Adami
2016-02-09 15:16 ` Mike Crowe
2016-02-02 21:04 ` Mike Crowe
2016-02-02 22:41 ` Richard Purdie
2016-02-05 17:32 ` Mike Crowe
2016-02-05 18:22 ` Khem Raj
2016-02-05 18:31 ` Richard Purdie
2016-02-05 18:35 ` Khem Raj
2016-02-06 17:43 ` Khem Raj
2016-02-05 18:35 ` Martin Jansa
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=20160207220741.GA12339@mcrowe.com \
--to=mac@mcrowe.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@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