From: Mike Crowe <mac@mcrowe.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Mike Crowe <mac@mcrowe.com>,
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: Tue, 9 Feb 2016 12:30:26 +0000 [thread overview]
Message-ID: <20160209123026.GA22354@mcrowe.com> (raw)
In-Reply-To: <CA+chaQfVbnjSV5Casif1b5_vxp4ysThnJLCShGAp89PCXd1tTw@mail.gmail.com>
On Tuesday 09 February 2016 at 11:39:17 +0100, Martin Jansa wrote:
> /home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-multimedia/ffmpeg/ffmpeg_2.8.5.bb,
> do_compile
That one builds successfully for me for qemuarm. Strange.
> /home/jenkins/oe/world/shr-core/meta-smartphone/meta-android/recipes-support/invensense/invensense_git.bb,
> do_package_qa
That one seems to be using cmake so I can't immediately see how it could be
affected by changing EXTRA_OEMAKE.
> /home/jenkins/oe/world/shr-core/meta-openembedded/meta-networking/recipes-extended/iscsitarget/iscsitarget_1.4.20.3+svn502.bb,
> do_compile
> /home/jenkins/oe/world/shr-core/meta-openembedded/meta-oe/recipes-graphics/wayland/wayland-fits_git.bb,
> do_compile
I think these failed for me even without changing EXTRA_OEMAKE but I
need to go back and check.
Thanks for testing. I shall try and reproduce them and see if adding the
old value of EXTRA_OEMAKE to the recipes fixes them.
Mike.
next prev parent reply other threads:[~2016-02-09 12:30 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
2016-02-08 0:07 ` Martin Jansa
2016-02-09 10:39 ` Martin Jansa
2016-02-09 12:30 ` Mike Crowe [this message]
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=20160209123026.GA22354@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