So, should I change it to:
STAGING_FIXMES = "HOSTTOOLS_DIR ${EXTRA_STAGING_FIXMES}"
EXTRA_STAGING_FIXMES ?= ""
And use ${STAGING_FIXMES} instead of ${EXTRA_STAGING_FIXMES} later on?
//Peter
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: den 28 april 2017 17:06
To: Peter Kjellerstedt
On 28 April 2017 at 19:01, Marc Ferland wrote:
> Tested with opkg HEAD revision. I also tested with 0.3.0 but it seems the
> 'compare-versions' command was broken...
>
Thanks for verifying.
Yes, it was. I tried writing a test case for this last year, discovered
that opkg
In deb control files, each line of a long description starts with
a single space. Empty lines are represented by a single space
followed by a single full stop character.
Signed-off-by: Andreas Oberritter
---
Please note: As opkg uses the same format, I believe this to be
Avoids parser errors if PACKAGE_ADD_METADATA_DEB is set to an
empty value.
Signed-off-by: Andreas Oberritter
---
meta/classes/package_deb.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/package_deb.bbclass
Add bash to /etc/shells if busybox is built with bash applet anabled
to fix login via dropbear.
Signed-off-by: Andreas Oberritter
---
meta/recipes-core/busybox/busybox.inc | 9 +
1 file changed, 9 insertions(+)
diff --git a/meta/recipes-core/busybox/busybox.inc
On Fri, Apr 28, 2017 at 12:30 PM, Burton, Ross
wrote:
>
> On 28 April 2017 at 14:58, Burton, Ross wrote:
>
>> dpkg thinks that 1.2rc2 is less than 1.2.0, I suspect the RRS doesn't use
>> the same algorithm. Not sure what opkg and dpkg think of it.
On 28 April 2017 at 14:58, Burton, Ross wrote:
> dpkg thinks that 1.2rc2 is less than 1.2.0, I suspect the RRS doesn't use
> the same algorithm. Not sure what opkg and dpkg think of it.
>
I meant opkg and rpm, obviously.
Good news is that RPM says 1.2rc2 < 1.2.0 too.
On 28 April 2017 at 16:01, Peter Kjellerstedt
wrote:
> -EXTRA_STAGING_FIXMES ?= ""
> +EXTRA_STAGING_FIXMES ?= "HOSTTOOLS_DIR"
>
EXTRA and ?= suggests that this should remain "" and the HOSTTOOLS_DIR
relocation is handled in another way, as other classes that have
The path to where to install and find the tools copied from the host
environment is already used in a couple of places. This warrants it to
get its own variable.
Signed-off-by: Peter Kjellerstedt
---
meta/classes/base.bbclass | 4 ++--
meta/conf/bitbake.conf| 3
After the introduction of copying host tools to the build directory
and cleaning out $PATH, we got a problem with one of our tools. It
turned out that its configure.ac uses AC_PATH_PROG(PERL, perl) to
locate the perl interpreter, and uses that on the shebang line of the
installed tool. Previously
Paths to host tools that have been copied to ${HOSTTOOLS_DIR} may end
up in the sstate cache. They thus need to be corrected when restoring
from the sstate cache.
Signed-off-by: Peter Kjellerstedt
---
meta/classes/sstate.bbclass | 2 +-
On 28 April 2017 at 14:15, Tanu Kaskinen wrote:
> Oh, I'm on speex-dev, and I missed the announcement of the new
> version... The recipe reporting system didn't notice the new version
> either, probably because it thought "1.2.0" is less than "1.2rc2". I
> wonder if this will be a
On Thu, 2017-04-27 at 11:39 -0400, Marc Ferland wrote:
> Upgrade speex to 1.2.0. Very small diff between 1.2rc2 and 1.2.0, mostly
> compiler warning fixes, tabs vs spaces, trailing whitespaces and one
> liners.
>
> Signed-off-by: Marc Ferland
> ---
>
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
Audio playback in gtk-play is broken with vaapi because the
visualizations do not work: disable visualizations as workaround.
This should be reverted as soon as [YOCTO #11410] is fixed.
Signed-off-by: Jussi Kukkonen
---
Hi,
I'm proposing this for 2.3 (in case there is
> -Original Message-
> From: Andre McCurdy [mailto:armccu...@gmail.com]
> Sent: Thursday, April 27, 2017 9:56 PM
> To: Tamtamis, Panagiotis
> Cc: OE Core mailing list
> Subject: Re: [OE-core] [PATCH] Check if /etc/fstab exists
>
> On Thu, Apr 27, 2017 at 9:56 AM, Panagiotis Tamtamis
>
Using "read-only-rootfs" feature in minimal or special
purpose images (eg mounted images) makes build to fail
because ${IMAGE_ROOTFS}/etc/fstab file does not exist.
Signed-off-by: Panagiotis Tamtamis
---
meta/classes/rootfs-postcommands.bbclass | 4 +++-
1 file
17 matches
Mail list logo