On 28 September 2015, Tudor Florea wrote:
> > On 28 September 2015, Ross Burton wrote:
> > > Surely if an upstream is under your control and is ptest-aware, it can
> > > also
> > > install run-ptest into the right place too?
> > The run-ptest script is currently required to be in WORKDIR.
>
On 09/28/2015 08:31 PM, Burton, Ross wrote:
On 28 September 2015 at 10:20, Robert Yang > wrote:
-inherit distutils
+inherit distutils setuptools
setuptools inherits distutils, so you can replace instead of adding.
recall this patch, I'll send out v2 for update commit logs.
Wenzong
On 09/24/2015 07:04 PM, wenzong@windriver.com wrote:
From: Wenzong Fan
* gio-2.0.pc:
-L/path/to/tmp/sysroots/qemux86-64/lib64 -> -L/lib64
* gobject-2.0.pc:
Remove dependencies for test targets. Otherwise, during ptest
execution, "make" tries to rebuild those executables and fails
there.
[YOCTO #8059]
Signed-off-by: Maxin B. John
---
.../openssl/openssl/ptest_makefile_deps.patch | 248 +
On Tue, 2015-09-29 at 06:59 +, Ray, Ian (GE Healthcare) wrote:
> On 28 September 2015, Tudor Florea wrote:
> > > On 28 September 2015, Ross Burton wrote:
> > > > Surely if an upstream is under your control and is ptest-aware, it can
> > > > also
> > > > install run-ptest into the right place
Prelinking on x86-64 wasn't working out the box as it uses /lib and
not /lib64 for libs. Prelink was refusing to link as the dynamic loader
didn't match its idea of the right path. Passing in the --dyanmic-linker
option avoids this.
We can share code from image-mklibs so abstract that into a new
Hi all,
There hasn't been anything on this for two weeks already, has anyone
considered merging these patches?
--
Cheers,
Andrew
signature.asc
Description: OpenPGP digital signature
--
___
Openembedded-core mailing list
Hi RP,
On Tue, Sep 29, 2015 at 11:54:38AM +0100, Richard Purdie wrote:
> On Tue, 2015-09-29 at 05:54 +0300, Maxin B. John wrote:
> > Remove dependencies for test targets. Otherwise, during ptest
> > execution, "make" tries to rebuild those executables and fails
> > there.
> >
> > [YOCTO #8059]
>
On Tue, 2015-09-29 at 13:57 +0300, Markus Lehtonen wrote:
> Hi,
>
>
> On Mon, 2015-09-28 at 15:25 -0500, Leonardo Sandoval wrote:
> >
> > On 09/24/2015 06:53 AM, Markus Lehtonen wrote:
> > > In order to remove some code duplication.
> > >
> > > Signed-off-by: Markus Lehtonen
Checks within prelink force 64 bit binaries into lib64 and n32 binaries
into lib32. We load prelink.conf with all combinations but this code
then defeats it for us and means /lib is ignored.
Comment out this code to disable it and allow our settings to work. This
allows 64 bit binaries in /lib to
Currently a lib32-core-image-* SDK prints an incorrect environment-setup-*
file name when installing the SDK. Instead of printing the wrong thing, list
the environment setup files present in the SDK.
As it happens this fixes the message printed with buildtools-tarball too
which someone reported
On Mon, 2015-09-28 at 14:43 +0300, Ioan-Adrian Ratiu wrote:
> Signed-off-by: Ioan-Adrian Ratiu
> ---
> meta-oe/recipes-support/vim/vim_7.4.481.bb | 10 +-
> 1 file changed, 9 insertions(+), 1 deletion(-)
This should be sent to oe-devel for meta-oe changes.
Cheers,
Signed-off-by: Daniel Istrate
---
meta/lib/oeqa/selftest/wic.py | 33 +
1 file changed, 29 insertions(+), 4 deletions(-)
diff --git a/meta/lib/oeqa/selftest/wic.py b/meta/lib/oeqa/selftest/wic.py
index 3dc54a4..9425dc0 100644
From: Ross Burton
To avoid races between the sstate tasks/hooks using ${B} as the cwd, and other
tasks such as cmake_do_configure which deletes and re-creates ${B}, ensure that
all sstate hooks are run in the right directory, and run the prefunc/postfunc
in WORKDIR.
From: Ross Burton
To avoid races between the sstate tasks/hooks using ${B} as the cwd, and other
tasks such as cmake_do_configure which deletes and re-creates ${B}, ensure that
all sstate hooks are run in the right directory, and run the prefunc/postfunc
in WORKDIR.
On Mon, Sep 28, 2015 at 7:53 AM, Richard Purdie
wrote:
> If you currently do a DISTRO_FEATURES_remove = "x11" with OE-Core, you
> see failures due to dependency problems. The work in resolving this was
> partially completed a while back. This adds in the markup
The following changes since commit 4a1dec5c61f73e7cfa430271ed395094bb262f6b:
multilib: Add TARGET_VENDOR to saved variables list (2015-09-28 11:59:17
+0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib ChenQi/runuser-pam
Hi,
While using fido branch on custom SDK, hit this below problem was most of the
recipes. The below error happened when trying to build directfb
Any pointer on the below error and how to resolve this.
The stack trace of python calls that resulted in this exception/failure was:
File:
On Tue, 2015-09-29 at 05:54 +0300, Maxin B. John wrote:
> Remove dependencies for test targets. Otherwise, during ptest
> execution, "make" tries to rebuild those executables and fails
> there.
>
> [YOCTO #8059]
>
> Signed-off-by: Maxin B. John
> ---
>
The runuser command fails with below error message, add proper PAM
config files to fix the problem. The config files are borrowed from
CentOS 7.0 release.
runuser: Failure setting user credentials
Signed-off-by: Shan Hai
Signed-off-by: Chen Qi
---
On 24 September 2015 at 10:33, Lucian Musat
wrote:
> (options, args) = parser.parse_args()
> if len(args) != 1:
> -parser.error("Incorrect number of arguments. The one and only
> argument should be a json file exported by the build system")
> +
On 29 September 2015 at 11:54, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> I'm torn to be honest, the patch is explicit, the sed could be more
> prone to breakage. How do we handle this in other ptest situations?
>
FWIW I tend to prefer patches as they're self-documenting,
Hi,
On Mon, 2015-09-28 at 15:25 -0500, Leonardo Sandoval wrote:
>
> On 09/24/2015 06:53 AM, Markus Lehtonen wrote:
> > In order to remove some code duplication.
> >
> > Signed-off-by: Markus Lehtonen
> > ---
> > meta/lib/oeqa/selftest/devtool.py | 63
> >
When not doing actual tests with testimage, like for example
exporting tests, the link to the log file was still created
although the actual log file was not existent. Fixed it by
moving the link creation part into the run() method.
Signed-off-by: Lucian Musat
---
When not doing actual tests with testimage, like for example
exporting tests, the link to the log file was still created
although the actual log file was not existent. Fixed it by
moving the link creation part into the run() method.
Signed-off-by: Lucian Musat
---
From: Leonardo Sandoval
When getting the failures/errors/skipped lists, include the
unit test without the full path.
This issue was found on this scenario
| test_1_logrotate_setup (oeqa.runtime.logrotate.LogrotateTest) ... FAIL
|
Hi Andrew,
On 29 September 2015 at 13:39, Andrew Shadura <
andrew.shad...@collabora.co.uk> wrote:
> There hasn't been anything on this for two weeks already, has anyone
> considered merging these patches?
>
Sorry but they didn't quite make the M3 deadline (well, the patches did,
but reviewing
On 29/09/15 16:41, Burton, Ross wrote:
> On 29 September 2015 at 13:39, Andrew Shadura
> >
> wrote:
>
>>There hasn't been anything on this for two weeks already, has anyone
>>considered merging these patches?
> Sorry
Also added the default json file name as default for
the first positional argument.
Signed-off-by: Lucian Musat
---
meta/lib/oeqa/runexported.py | 36 +---
1 file changed, 17 insertions(+), 19 deletions(-)
diff --git
Updating the 4.1 SRCREVs to integrate the following DRM backports:
a8abc111a96d drm/i915: Only wait for required lanes in vlv_wait_port_ready()
81354180432b Revert "drm/i915: Hack to tie both common lanes together on chv"
d660fc117731 drm/i915: Work around DISPLAY_PHY_CONTROL register
As part of the axxia preempt-rt integration, the preempt-rt
branch now becomes standard/preempt-rt/base, to allow proper
branch inheritance as: standard/preempt-rt/axxia/base.
No functional changes happen to the base -rt, just the default
KBRANCH changes.
Signed-off-by: Bruce Ashfield
There are some important fixes and CVEs in 4.1.8, so we update the
SRCREVs to integrate the -stable changes.
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
Hi all,
Here is the latest round of linux-yocto related changes.
The first three are integrations of BSP patches/fixes, and a -stable
update for 4.1. I've built and booted them here.
The only trick with the axxia BSP integration is that there's a branch
rename for standard/preempt-rt to
Updating the kern-tools SRCREV to import the following fix:
kgit-meta: resume after last applied patch
When the auto-resume (resume point detection) was removed from the
processing of a meta-series, it ignored the fact that a single patch
series may in fact be processed a number
If you build buildtools-tarball with opkg as the package manager, it
passes in an empty target packages list and fails.
This allows the code to cope with an empty package list (in sync
with the rpm backend).
Signed-off-by: Richard Purdie
diff --git
On Tue, 2015-09-29 at 15:41 +0100, Burton, Ross wrote:
> On 29 September 2015 at 13:39, Andrew Shadura
> wrote:
> There hasn't been anything on this for two weeks already, has
> anyone
> considered merging these patches?
>
> Sorry but they
On 29/09/15 16:50, Richard Purdie wrote:
> On Tue, 2015-09-29 at 15:41 +0100, Burton, Ross wrote:
>> > On 29 September 2015 at 13:39, Andrew Shadura
>> > wrote:
>> >>There hasn't been anything on this for two weeks already, has
>> >>anyone
>> >>
On Mon, Sep 28, 2015 at 03:38:23PM -0700, Randy Witt wrote:
> Since inittab for qemu images now always tries to start getty on a
> second serial device, make sure that device exists.
>
> Otherwise the following message will be spammed:
> INIT: Id "S1" respawning too fast: disabled for 5
On 29 September 2015 at 15:48, Andrew Shadura <
andrew.shad...@collabora.co.uk> wrote:
> So, what is the planned date for the release?
>
It's scheduled for early October.
Ross
--
___
Openembedded-core mailing list
> On Sep 29, 2015, at 6:27 AM, Richard Purdie
> wrote:
>
> Prelinking on x86-64 wasn't working out the box as it uses /lib and
> not /lib64 for libs. Prelink was refusing to link as the dynamic loader
> didn't match its idea of the right path. Passing in the
> On Sep 29, 2015, at 7:31 AM, Bruce Ashfield
> wrote:
>
> Updating the kern-tools SRCREV to import the following fix:
>
>kgit-meta: resume after last applied patch
>
>When the auto-resume (resume point detection) was removed from the
>processing of
On Thu, Sep 10, 2015 at 04:31:26PM +0200, Martin Jansa wrote:
> * this can be useful for passing extra parameters, pass
> -v by default to see what's going on in do_rootfs
> * we need to use this for extra parameter we implemented
> in fontconfig:
> --ignore-mtime always use cache file
> On Sep 29, 2015, at 6:26 AM, Richard Purdie
> wrote:
>
> Checks within prelink force 64 bit binaries into lib64 and n32 binaries
> into lib32. We load prelink.conf with all combinations but this code
> then defeats it for us and means /lib is ignored.
>
>
On Tue, 2015-09-29 at 17:45 +, Alejandro Hernandez wrote:
> gcc packages use a shared source directory, this causes an issue since
> the archiver will try to patch the same source several times (one for
> each gcc package), producing an error, the archiver class used stamp-base
> to check
We are experimenting segfault in qemu arm SCSI driver because
it's broken [1][2] so enable virtio drivers to use as default.
[YOCTO #8060]
[1] https://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00093.html
[2] https://lists.nongnu.org/archive/html/qemu-devel/2010-07/msg01473.html
Use virtio block device into qemuarm for avoid qemu SCSI device problem that
is broken.
I tested (ran testimage) this patches using core-image-sato and core-image-lsb
with kernels 3.14, 3.19 and 4.1.
[YOCTO #8060]
The following changes since commit f78f90240a3041be426c6ba9085849352164ee8b:
We are experiencing occasional segfaults in scsi sym53c8xx driver
on qemuarm boot. There are some old discussions into the mailing
lists [1] about the scsi problem and seems to be isn't fixed.
We use virtio blk/net devices into qemuarm64 also are supported
into qemuarm so change to use it because
On 2015-09-29 6:51 PM, Aníbal Limón wrote:
We are experimenting segfault in qemu arm SCSI driver because
it's broken [1][2] so enable virtio drivers to use as default.
This looks fine to me, and is consistent with the other features
we are enabling for the default qemu* machines.
What (if
From: Mariano Lopez
This change just add two more commands to
the host dumps to get more information
related to the IO.
[YOCTO #8412]
Signed-off-by: Mariano Lopez
---
meta/classes/testimage.bbclass | 2 ++
> On Sep 29, 2015, at 2:05 AM, mariano.lo...@linux.intel.com wrote:
>
> From: Mariano Lopez
>
> This change just add two more commands to
> the host dumps to get more information
> related to the IO.
>
> [YOCTO #8412]
>
> Signed-off-by: Mariano Lopez
On 9/29/15 12:12 PM, Khem Raj wrote:
>
>> On Sep 29, 2015, at 6:26 AM, Richard Purdie
>> wrote:
>>
>> Checks within prelink force 64 bit binaries into lib64 and n32 binaries
>> into lib32. We load prelink.conf with all combinations but this code
>> then
gcc packages use a shared source directory, this causes an issue since
the archiver will try to patch the same source several times (one for
each gcc package), producing an error, the archiver class used stamp-base
to check this, nonetheless our gcc packages no longer use stamp-base,
they use
On 29/09/2015 09:59, Ray, Ian (GE Healthcare) wrote:
On 28 September 2015, Tudor Florea wrote:
On 28 September 2015, Ross Burton wrote:
Surely if an upstream is under your control and is ptest-aware, it can also
install run-ptest into the right place too?
The run-ptest script is currently
53 matches
Mail list logo