On Wed, 2016-07-27 at 16:02 +0300, Maxin B. John wrote:
> 1.13.0 -> 2.0.0
>
> Signed-off-by: Maxin B. John
> ---
> meta/recipes-graphics/glew/{glew_1.13.0.bb => glew_2.0.0.bb} | 4 ++-
> -
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-graphics/glew/{glew_1.13.0.bb => g
On Wed, 2016-07-27 at 21:52 +, Alejandro Hernandez wrote:
> Signed-off-by: Alejandro Hernandez <
> alejandro.hernan...@linux.intel.com>
> ---
> meta/recipes-extended/cronie/{cronie_1.5.0.bb => cronie_1.5.1.bb} |
> 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes
On Wed, 2016-07-27 at 12:57 -0400, Bruce Ashfield wrote:
> Updating the 4.1 kernel to the korg -stable release
>
> Signed-off-by: Bruce Ashfield
> ---
> meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 6 +++---
> meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 6 +++---
> meta/recipes-
Hi Ross,
On 07/28/2016 06:02 AM, Burton, Ross wrote:
On 27 July 2016 at 23:21, Manjukumar Matha
mailto:manjukumar.harthikote-ma...@xilinx.com>> wrote:
This patch enables building u-boot using externalsrc
The commit summary should mention that it's enabling out-of-tree builds,
of which su
On Thu, 2016-07-28 at 18:00 +, Alejandro Hernandez wrote:
> LICENCE checksum did not change, it is emebedded on the setup.py
> file,
> this file changed, so the line number where we get the checksum
> changed.
>
> Signed-off-by: Alejandro Hernandez <
> alejandro.hernan...@linux.intel.com>
> --
never used "wic" before, and i'm wondering if it has the ability to
not create dd-able images so much as partition and format physical
target devices. surely, the underlying logic would be the same, i just
want to work with the target hard drive and bypass creating the image
itself.
rday
--
On Thu, Jul 28, 2016 at 1:49 AM, Awais Belal wrote:
> Using a copy would only make management of devices erroneous
> and makes the system unstable in some scenarios as tools will
> have to manipulate both files separately. A link ensures that
> both files /proc/mounts and /etc/mtab will have the s
On Wed, 2016-07-27 at 15:51 +0300, Ed Bartosh wrote:
> From: Patrick Ohly
>
> When using conversion chaining (for example example: .dsk.vdi.xz),
> the imagetypes_getdepends() did not properly detect all compression
> commands (thus skipping the corresponding COMPRESS_DEPENDS) and
> the base type,
On Wed, 2016-07-27 at 15:51 +0300, Ed Bartosh wrote:
> From: Patrick Ohly
>
> When using conversion chaining (for example example: .dsk.vdi.xz),
> the imagetypes_getdepends() did not properly detect all compression
> commands (thus skipping the corresponding COMPRESS_DEPENDS) and
> the base type,
/124466.html
With the fix applied kernel build time decreased by 22.84%:
Build Configuration:
BB_VERSION= "1.31.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "openSUSE-13.2"
TARGET_SYS= "i586-poky-linux"
MACHINE = "qemux86"
These tasks relied upon [dirs] being ${B} by default. As the functions are not
simple, add back [dirs] so they work again.
[ YOCTO #10027 ]
Signed-off-by: Ross Burton
---
meta/classes/cml1.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes/cml1.bbclass b/meta/classes/cm
LICENCE checksum changed, although license didnt change,
it says PEXPECT license instead of ISC, but its still ISC.
Signed-off-by: Alejandro Hernandez
---
.../python/python-pexpect_4.1.0.bb | 28 --
.../python/python-pexpect_4.2.0.bb | 28 +
LICENCE checksum did not change, it is emebedded on the setup.py file,
this file changed, so the line number where we get the checksum changed.
Signed-off-by: Alejandro Hernandez
---
meta/recipes-devtools/python/python-setuptools.inc | 6 ++--
.../python/python-setuptools_22.0.5.bb
> On Jul 28, 2016, at 1:49 AM, Awais Belal wrote:
>
> Using a copy would only make management of devices erroneous
> and makes the system unstable in some scenarios as tools will
> have to manipulate both files separately. A link ensures that
> both files /proc/mounts and /etc/mtab will have the
It was pointed out that the 4.4 version of -rt was lagging. I had done
the work some time ago, but didn't complete the testing effort.
I've now built and booted this on x86 and built it for ARM.
Two branches are available: standard/preempt-rt/base and
standard/preempt-rt/rebase.
Signed-off-by:
Maxim,
On 07/28/2016 07:04 AM, Maxin B. John wrote:
> From: Tim Orling
>
> Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will only
> contain releases that are currently in Debian, so currently doesn't contain
> 3.1.18 as unstable has moved on to 3.1.20.
>
> So, move all of
Can I please get master commit 92cfdb2ba7e04e2b70986c6569f500dd2a48b5d1
backported to krogoth?
Thanks,
Mike
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedde
Hi Ross,
9 out of those 12 patches applies to master. I have pushed those here:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=maxin/10040
Will update and push the other patches soon.
Best regards,
Maxin
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Thursday, July 28, 2
On 28 July 2016 at 15:04, Maxin B. John wrote:
> Recipes that use DEBIAN_MIRROR in SRC_URI are setting themselves up for
> failure
> as the Debian mirror network only stores active releases, so once a
> version we
> use isn't in oldstable/stable/testing/unstable then it will be removed.
>
> The s
On 07/27/2016 10:18 PM, Leonardo Sandoval wrote:
> Hi Anibal,
>
>
> El 07/27/2016 a las 05:40 PM, Aníbal Limón escribió:
>> When run a command sometimes the output isn't provided so validate
> I wonder if this problem is related to a timeout, so at some point this
> is reached and no output is
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will
only contain releases that are currently in Debian. So, move all of SRC_URI
to the .bb so it can use snapshot.debian.org instead, and set
UPSTREAM_CHECK_URI to ${DEBIAN_MIRROR} so upstream release checking continues
to work.
[Y
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will
only contain releases that are currently in Debian. So, move all of SRC_URI
to the .bb so it can use snapshot.debian.org instead, and set
UPSTREAM_CHECK_URI to ${DEBIAN_MIRROR} so upstream release checking continues
to work.
[Y
From: Tim Orling
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will only
contain releases that are currently in Debian, so currently doesn't contain
3.1.18 as unstable has moved on to 3.1.20.
So, move all of SRC_URI to the .bb so it can use snapshot.debian.org instead,
and se
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will
only contain releases that are currently in Debian. So, move all of SRC_URI
to the .bb so it can use snapshot.debian.org instead, and set
UPSTREAM_CHECK_URI to ${DEBIAN_MIRROR} so upstream release checking continues
to work.
[Y
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will
only contain releases that are currently in Debian.
So, move all of SRC_URI to the .bb so it can use snapshot.debian.org
instead, and set UPSTREAM_CHECK_URI to ${DEBIAN_MIRROR} so upstream
release checking continues to work.
[
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will
only contain releases that are currently in Debian.
So, move all of SRC_URI to the .bb so it can use snapshot.debian.org
instead, and set UPSTREAM_CHECK_URI to ${DEBIAN_MIRROR} so upstream
release checking continues to work.
[
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will
only contain releases that are currently in Debian.
So, move all of SRC_URI to the .bb so it can use snapshot.debian.org
instead, and set UPSTREAM_CHECK_URI to ${DEBIAN_MIRROR} so upstream
release checking continues to work.
[
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will
only contain releases that are currently in Debian. So, move all of SRC_URI
to the .bb so it can use snapshot.debian.org instead, and set
UPSTREAM_CHECK_URI to ${DEBIAN_MIRROR} so upstream release checking continues
to work.
[Y
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will
only contain releases that are currently in Debian.
So, move all of SRC_URI to the .bb so it can use snapshot.debian.org
instead, and set UPSTREAM_CHECK_URI to ${DEBIAN_MIRROR} so upstream
release checking continues to work.
[
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will
only contain releases that are currently in Debian.
So, move all of SRC_URI to the .bb so it can use snapshot.debian.org
instead, and set UPSTREAM_CHECK_URI to ${DEBIAN_MIRROR} so upstream
release checking continues to work.
[
From: Tim Orling
>From Ross Burton (commit 1d39e4c145925e4517dc7fbb6f83767e883bb3c6)
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will
only contain releases that are currently in Debian, so currently doesn't
contain 1.18.4 as unstable has moved on to 1.18.9.
So, move all of
Using ${DEBIAN_MIRROR} for SRC_URI doesn't work very well as that will
only contain releases that are currently in Debian. So, move all of SRC_URI
to the .bb so it can use snapshot.debian.org instead, and set
UPSTREAM_CHECK_URI to ${DEBIAN_MIRROR} so upstream release checking continues
to work.
[Y
Recipes that use DEBIAN_MIRROR in SRC_URI are setting themselves up for failure
as the Debian mirror network only stores active releases, so once a version we
use isn't in oldstable/stable/testing/unstable then it will be removed.
The solution here is to use the snapshot.debian.org service for the
On Thu, Jul 28, 2016 at 1:18 AM, thilo.ceston...@ts.fujitsu.com
wrote:
> Hey Khem!
>
> Thanks for your help!! We used to have an extra ld-script which once worked.
> It was injected into the sdk in our sdk-install script by moving the
> toolchain ld to ld.real and creating a script which
> calls
On Thu, Jul 28, 2016 at 02:24:41PM +0100, Burton, Ross wrote:
> On 28 July 2016 at 14:20, Tom Rini wrote:
>
> > So ARCH and a bunch of other stuff isn't set and things blow up. Just
> > how large of a -j value are you using here as I would have sworn we had
> > gotten this problem fixed.
>
> 20
On 28 July 2016 at 14:20, Tom Rini wrote:
> So ARCH and a bunch of other stuff isn't set and things blow up. Just
> how large of a -j value are you using here as I would have sworn we had
> gotten this problem fixed.
>
20. Before applying the patch I did a build to verify that the patch
introd
On Thu, Jul 28, 2016 at 02:02:20PM +0100, Burton, Ross wrote:
> On 27 July 2016 at 23:21, Manjukumar Matha <
> manjukumar.harthikote-ma...@xilinx.com> wrote:
>
> > This patch enables building u-boot using externalsrc
> >
>
> The commit summary should mention that it's enabling out-of-tree builds
On 27 July 2016 at 23:21, Manjukumar Matha <
manjukumar.harthikote-ma...@xilinx.com> wrote:
> This patch enables building u-boot using externalsrc
>
The commit summary should mention that it's enabling out-of-tree builds, of
which supporting externalsrc is a side effect.
However this doesn't wor
They are unlikely to be of any use in the target file system.
Signed-off-by: André Draszik
---
meta/recipes-core/readline/readline.inc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-core/readline/readline.inc
b/meta/recipes-core/readline/readline.inc
index 35df8b4..1a0a155 1
CFLAGS/CXXFLAGS in the SDK environment script adds debug-prefix mappings
that include staging area/work directories. Remove them since the SDK
shouldn't be aware of them.
Signed-off-by: Jacob Kroon
---
meta/classes/toolchain-scripts.bbclass | 3 +++
meta/conf/bitbake.conf | 8 +++
In Ostro OS we just started to use useradd-staticids.bbclass. Dynamic
IDs are an error (USERADD_ERROR_DYNAMIC = "error") by default because
warnings probably wouldn't be noticed. I was a bit reluctant to make
this change because Ostro OS is supposed to be customizable, and that
becomes harder when
This addresses (among others) the following problem:
- USERADD_ERROR_DYNAMIC=error causes a recipe to get skipped
because a static ID entry is missing
- the entry gets added to the file
- using the recipe still fails with the same error as before
because the recipe gets loaded from the cache in
On 2016-07-28 11:32, Burton, Ross wrote:
On 27 July 2016 at 23:14, Alejandro Hernandez
mailto:alejandro.hernan...@linux.intel.com>> wrote:
-LIC_FILES_CHKSUM =
"file://setup.py;beginline=134;endline=134;md5=3e8df024d6c1442d18e84acf8fbbc475"
+LIC_FILES_CHKSUM =
"file://setup.py;beginli
On 27 July 2016 at 22:52, Alejandro Hernandez <
alejandro.hernan...@linux.intel.com> wrote:
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=66c2378a96b307d56bfb3a9e58edafa8"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=1c7a725251880af8c6a148181665385b"
>
Please state why the license checksum changed.
Ros
On 27 July 2016 at 23:14, Alejandro Hernandez <
alejandro.hernan...@linux.intel.com> wrote:
> -LIC_FILES_CHKSUM =
> "file://setup.py;beginline=134;endline=134;md5=3e8df024d6c1442d18e84acf8fbbc475"
> +LIC_FILES_CHKSUM =
> "file://setup.py;beginline=155;endline=155;md5=3e8df024d6c1442d18e84acf8fbbc4
On Wed, 2016-07-27 at 18:40 -0700, Khem Raj wrote:
>
> > On Jul 27, 2016, at 12:51 PM, Burton, Ross
> > wrote:
> > Why is this needed when wayland already depends on wayland
> > > -native?
> > Because builds from sstate won't pull in all the build dependencies
> > transitively, just enough to do
Using a copy would only make management of devices erroneous
and makes the system unstable in some scenarios as tools will
have to manipulate both files separately. A link ensures that
both files /proc/mounts and /etc/mtab will have the same
information at all times and this is how it is handled
on
Hey Khem!
Thanks for your help!! We used to have an extra ld-script which once worked. It
was injected into the sdk in our sdk-install script by moving the toolchain ld
to ld.real and creating a script which
calls the ld.real with the ldscript as parameter. I didn't introduce this in
the sdk in
On Mi, 2016-07-27 at 08:18 -0700, Khem Raj wrote:
> >
> > On Jul 27, 2016, at 5:14 AM, thilo.ceston...@ts.fujitsu.com wrote:
> >
> > Hey Khem,
> >
> > I figured, when I do the compile in 2 steps, so compile then link and
> > change the link command to use the ubuntu arm-linux-gnueabihf-gcc inst
49 matches
Mail list logo
