From: Muhammad Shakeel muhammad_shak...@mentor.com
-Remove dependency on meta-systemd
Signed-off-by: Muhammad Shakeel muhammad_shak...@mentor.com
---
meta/recipes-bsp/apmd/apmd-3.2.2-14/apmd.service |7 +++
meta/recipes-bsp/apmd/apmd_3.2.2-14.bb | 13 +++--
2 files
From: Muhammad Shakeel muhammad_shak...@mentor.com
-Remove dependency on meta-systemd
Signed-off-by: Muhammad Shakeel muhammad_shak...@mentor.com
---
.../oprofileui-server/oprofileui-server.service|6 ++
.../oprofile/oprofileui-server_git.bb | 13 +++--
2
I've done a world build on qemux86 with:
PROVIDES_prepend = ${PN}
it worked well.
// Robert
On 09/09/2013 10:14 PM, Richard Purdie wrote:
For a long time we've provided PN-PV and PN-PV-PR by tweaking PROVIDES. This
looks
nice at first glance however it turns out to be a bit problematic.
On 12 September 2013 02:17, Darren Hart dvh...@linux.intel.com wrote:
I thought the idea was to try to build with --disable-gl or similar if
the DISTRO_FEATURES didn't include opengl, rather than disable the
driver entirely.
Am I remembering incorrectly, or was there more discussion on that
I have a slight problem with this patch. The new
sysroot-relativelinks.py does not obtain the proper access protection
bits!?
Which results in the following error when packaging the SDK
On Thu, 2013-09-12 at 09:48 +0200, Hans Beckérus wrote:
I have a slight problem with this patch. The new
sysroot-relativelinks.py does not obtain the proper access protection
bits!?
Which results in the following error when packaging the SDK
On Thu, Sep 12, 2013 at 10:02 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Thu, 2013-09-12 at 09:48 +0200, Hans Beckérus wrote:
I have a slight problem with this patch. The new
sysroot-relativelinks.py does not obtain the proper access protection
bits!?
Which results in the
Test Case:
1. Prepare a deployed target, and make sure your boot area has enough disk
space.
2. Download the new kernel image rpm to the target
3. Before install/update, check boot area and menu
root@qemux86:~# ls /boot/
grubvmlinuz
root@qemux86:~# cat /boot/grub/grub.cfg
menuentry
While installing a rpm to update kernel on a deployed target, it will update
the boot area and the boot menu with the kernel as the priority but allow
you to fall back to the original kernel as well.
- In pre-install script, it backs up original kernel to avoid confliction with
new one.
- In
The following changes since commit bd76847d867f9f76f76f033439cfb834cf59380f:
libnewt-python: Don't write a whiptail package (2013-09-12 08:23:42 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/perf
In perf.bb:
S = ${STAGING_KERNEL_DIR}
So the source should be ready after the do_unpack, and we need this:
do_unpack[depends] += virtual/kernel:do_populate_sysroot
Otherwise, maybe no source after do_unpack.
[YOCTO #5168]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
On Wednesday 11 September 2013 14:38:01 Saul Wold wrote:
We can't build both recipes in the world build as there is a collision of
package name and PR values. Specificly the libasound-module-bluez which is
the same in both goes backwards from r5 (bluez4) - r0 (bluez5) and the
There was a Segmentation fault error when build icu-native when the
TMPDIR is in a deep directory (for example, when len(readlink -f $TMPDIR
== 410)), use LARGE_BUFFER_MAX_SIZE for cmd rather than
SMALL_BUFFER_MAX_SIZE would fix the problem, this should be a misplay
because other cmd uses
The following changes since commit bd76847d867f9f76f76f033439cfb834cf59380f:
libnewt-python: Don't write a whiptail package (2013-09-12 08:23:42 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/icu
From: Chen Qi qi.c...@windriver.com
The following changes since commit bd76847d867f9f76f76f033439cfb834cf59380f:
libnewt-python: Don't write a whiptail package (2013-09-12 08:23:42 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/updatercd-rdepends
From: Chen Qi qi.c...@windriver.com
If a package inherits update-rc.d.bbclass, it actually needs it to
update the symlinks under /etc/rc?.d/ directories. This is a runtime
dependency. For example, if we try to upgrade the dropbear on target,
its postinst process will need the update-rc.d utility
This change just assumes that all boot systems are alike. Just applying
this patch as is will probably break a lot of embedded systems that
have totally different ways of upgrading the kernel. Best scenario is
that they'll waste time and space running scripts that will have no effect.
It
On Thu, Sep 12, 2013 at 05:43:55PM +0800, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
If a package inherits update-rc.d.bbclass, it actually needs it to
update the symlinks under /etc/rc?.d/ directories. This is a runtime
dependency. For example, if we try to upgrade the
This allows a clean seperation between image outputs from different
machines, and makes it possible to have convenience symlinks to make
the output ready to deploy.
This did require some surgery in runqemu; if explicit paths to the image
and kernel are not supplied then DEPLOY_DIR_IMAGE needs to
On 09/12/2013 06:25 PM, Martin Jansa wrote:
On Thu, Sep 12, 2013 at 05:43:55PM +0800, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
If a package inherits update-rc.d.bbclass, it actually needs it to
update the symlinks under /etc/rc?.d/ directories. This is a runtime
Our Mesa doesn't yet ship the XA Gallium state tracker that the VMWGFX
sub-driver needs, so just disable vmwgfx.
Also remove a spurious xvmc dependency.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
.../xf86-video-vmware/vmwgfx-option.patch | 69
On 09/12/2013 05:47 PM, Mike Looijmans wrote:
This change just assumes that all boot systems are alike. Just
applying this patch as is will probably break a lot of embedded
systems that have totally different ways of upgrading the kernel. Best
scenario is that they'll waste time and space
On Thu, Sep 12, 2013 at 07:18:12PM +0800, ChenQi wrote:
On 09/12/2013 06:25 PM, Martin Jansa wrote:
On Thu, Sep 12, 2013 at 05:43:55PM +0800, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
If a package inherits update-rc.d.bbclass, it actually needs it to
update the
On Thu, Sep 12, 2013 at 12:04:52PM +0100, Paul Eggleton wrote:
This allows a clean seperation between image outputs from different
machines, and makes it possible to have convenience symlinks to make
the output ready to deploy.
This did require some surgery in runqemu; if explicit paths to
On Thu, 2013-09-12 at 10:29 +0100, Paul Eggleton wrote:
On Wednesday 11 September 2013 14:38:01 Saul Wold wrote:
We can't build both recipes in the world build as there is a collision of
package name and PR values. Specificly the libasound-module-bluez which is
the same in both goes
Our Mesa doesn't yet ship the XA Gallium state tracker that the VMWGFX
sub-driver needs, so just disable vmwgfx.
Also remove a spurious xvmc dependency.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
.../xf86-video-vmware/vmwgfx-option.patch | 72
On Tue, 2013-08-13 at 16:20 +0800, rongqing...@windriver.com wrote:
From: Roy.Li rongqing...@windriver.com
sstate_package creates hardlink from sysroot to SSTATE_BUILDDIR, then
sstate_create_package will store SSTATE_BUILDDIR into a archive file by
tar, but once other packages install the
On 09/11/2013 05:08 PM, Rongqing Li wrote:
ping...
You replied to your patch question if it was right, therefore I put this
off expecting an updated patchset.
Or are you asking about 2/2?
Sau!
-Roy
On 09/04/2013 02:56 PM, rongqing...@windriver.com wrote:
From: Roy.Li
This will need a LAYERVERSION_core bump for autobuilder compatibility.
On Thu, Sep 12, 2013 at 4:04 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
This allows a clean seperation between image outputs from different
machines, and makes it possible to have convenience symlinks to make
On Thu, Sep 12, 2013 at 10:29 AM, Hans Beckérus hans.becke...@gmail.com wrote:
On Thu, Sep 12, 2013 at 10:02 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Thu, 2013-09-12 at 09:48 +0200, Hans Beckérus wrote:
I have a slight problem with this patch. The new
On 09/12/2013 10:19 AM, Jason Wessel wrote:
The syslinux.bbclass already has support for automatically generated
serial and graphics menu choices. This patch adds the same concept to
the grub-efi menu. That makes it possible to generate a single image
which can boot on a PCBIOS or EFI firmware
On 09/12/2013 01:01 PM, Saul Wold wrote:
On 09/12/2013 10:19 AM, Jason Wessel wrote:
The syslinux.bbclass already has support for automatically generated
serial and graphics menu choices. This patch adds the same concept to
the grub-efi menu. That makes it possible to generate a single image
On Thu, Sep 12, 2013 at 7:09 PM, Saul Wold s...@linux.intel.com wrote:
On 09/11/2013 09:05 AM, Hans Beckérus wrote:
On Wed, Sep 11, 2013 at 10:15 AM, Hans Beckérus hans.becke...@gmail.com
wrote:
On Tue, Sep 10, 2013 at 11:33 PM, Saul Wold s...@linux.intel.com wrote:
On 09/10/2013 07:56 AM,
On Thu, 2013-09-12 at 12:19 -0500, Jason Wessel wrote:
Using the latest mkisofs it is possible to generate 3 different types
of ISO images, which can be used in various scenarios.
1) PCBIOS Only ISO
- This option remains unchanged by this commit
- Uses syslinux menus
- Can be
On Thu, 2013-09-12 at 15:14 -0500, Jason Wessel wrote:
On 09/12/2013 01:09 PM, Darren Hart wrote:
On Thu, 2013-09-12 at 12:19 -0500, Jason Wessel wrote:
Using the latest mkisofs it is possible to generate 3 different types
of ISO images, which can be used in various scenarios.
1) PCBIOS
On Thu, 2013-09-12 at 11:01 -0700, Saul Wold wrote:
On 09/12/2013 10:19 AM, Jason Wessel wrote:
The syslinux.bbclass already has support for automatically generated
serial and graphics menu choices. This patch adds the same concept to
the grub-efi menu. That makes it possible to generate
On Thu, 2013-09-12 at 14:52 -0500, Jason Wessel wrote:
On 09/12/2013 01:16 PM, Darren Hart wrote:
On Thu, 2013-09-12 at 12:19 -0500, Jason Wessel wrote:
The syslinux.bbclass already has support for automatically generated
serial and graphics menu choices. This patch adds the same concept
On 09/12/2013 01:09 PM, Darren Hart wrote:
On Thu, 2013-09-12 at 12:19 -0500, Jason Wessel wrote:
Using the latest mkisofs it is possible to generate 3 different types
of ISO images, which can be used in various scenarios.
1) PCBIOS Only ISO
- This option remains unchanged by this commit
On Wed, Sep 11, 2013 at 2:17 AM, rongqing...@windriver.com wrote:
+for x in `find -L ./ -name run-ptest -type f -perm /u+x,g+x`
+do
As far as I can tell, busybox find doesn't support -L, so this adds an
implicit, undeclared dependency upon findutils.
--
Christopher Larson
On 09/12/2013 01:16 PM, Darren Hart wrote:
On Thu, 2013-09-12 at 12:19 -0500, Jason Wessel wrote:
The syslinux.bbclass already has support for automatically generated
serial and graphics menu choices. This patch adds the same concept to
the grub-efi menu. That makes it possible to generate a
In order to call the fat image creation multiple times it needs to be
in its own function. A future commit will make use of the new
function to additionally create EFI image files for use with an ISO.
[YOCTO #4100]
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
On 2013-09-12 14:12, Christian Babeux wrote:
Hi Stefan,
+
+make -C tests installcheck
+
A majority of the tests will probably fail this way. As of now, most
tests assumes that they are being runned in the build tree and expect
binaries to be at specific paths. We will have to fix this
On Thu, 2013-09-12 at 12:19 -0500, Jason Wessel wrote:
The iso9660 file system support needs to be added to grub in order to
be able to correctly find the grub.cfg. The grub commands to locate
the grub.cfg also needs to be encoded into grub's default
configuration.
This change allows the
On 2013-09-12 8:02, Hans Beckérus wrote:
On Thu, Sep 12, 2013 at 7:09 PM, Saul Wold s...@linux.intel.com wrote:
On 09/11/2013 09:05 AM, Hans Beckérus wrote:
On Wed, Sep 11, 2013 at 10:15 AM, Hans Beckérus hans.becke...@gmail.com
wrote:
On Tue, Sep 10, 2013 at 11:33 PM, Saul Wold
From: João Henrique Ferreira de Freitas joa...@gmail.com
Condition building PCBIOS legacy images on MACHINE_FEATURES containing
pcbios
or not containing efi. This ensures existing BSPs will continue to get the
old PCBIOS legacy-only images. New BSPs can add efi, pcbios, or both.
The
On Thu, 2013-09-12 at 16:02 -0300, Joao Henrique Ferreira de Freitas
wrote:
From: João Henrique Ferreira de Freitas joa...@gmail.com
Condition building PCBIOS legacy images on MACHINE_FEATURES containing
pcbios
or not containing efi. This ensures existing BSPs will continue to get
On Thu, 2013-09-12 at 12:19 -0500, Jason Wessel wrote:
In order to call the fat image creation multiple times it needs to be
in its own function. A future commit will make use of the new
function to additionally create EFI image files for use with an ISO.
[YOCTO #4100]
Signed-off-by:
On 09/12/2013 02:09 PM, Hans Beckerus wrote:
On 2013-09-12 8:02, Hans Beckérus wrote:
On Thu, Sep 12, 2013 at 7:09 PM, Saul Wold s...@linux.intel.com wrote:
On 09/11/2013 09:05 AM, Hans Beckérus wrote:
On Wed, Sep 11, 2013 at 10:15 AM, Hans Beckérus
hans.becke...@gmail.com
wrote:
On Tue, Sep
Hi Stefan,
+
+make -C tests installcheck
+
A majority of the tests will probably fail this way. As of now, most
tests assumes that they are being runned in the build tree and expect
binaries to be at specific paths. We will have to fix this upstream if
you want to integrate our testsuite with
On Thu, 2013-09-12 at 12:19 -0500, Jason Wessel wrote:
The update is needed to support generation of EFI boot images that
work with optical media. Specifically the -eltorito-platform efi
capability for mkisofs is needed.
[YOCTO #4100]
Signed-off-by: Jason Wessel
Still, I think it's good to include these tests. If anything they may
just provide more motivation to address the underlying issue. :-)
Absolutely! I'll start a thread on lttng-dev to see how we can deal
with the current testsuite limitations.
++prove --merge -v --exec '' - $1 | sed \
++
Signed-off-by: Stefan Stanacar stefanx.stana...@intel.com
---
scripts/contrib/build-perf-test.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/scripts/contrib/build-perf-test.sh
b/scripts/contrib/build-perf-test.sh
index ce0fb9a..be3b648 100755
---
On 09/12/2013 10:19 AM, Jason Wessel wrote:
The update is needed to support generation of EFI boot images that
work with optical media. Specifically the -eltorito-platform efi
capability for mkisofs is needed.
[YOCTO #4100]
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
The iso9660 file system support needs to be added to grub in order to
be able to correctly find the grub.cfg. The grub commands to locate
the grub.cfg also needs to be encoded into grub's default
configuration.
This change allows the resulting grub binary to work both in the hard
drive / USB
The goal of this patch set is to put the EFI ISO boot method on par
with the ISO PCBIOS boot method. This also allows for the creation of
a single ISO image which can boot in legacy boot mode or EFI boot
mode.
In order to make this possible the cdrtools needed an update to the
very latest and
The syslinux.bbclass already has support for automatically generated
serial and graphics menu choices. This patch adds the same concept to
the grub-efi menu. That makes it possible to generate a single image
which can boot on a PCBIOS or EFI firmware with consistent looking
boot options.
[YOCTO
Using the latest mkisofs it is possible to generate 3 different types
of ISO images, which can be used in various scenarios.
1) PCBIOS Only ISO
- This option remains unchanged by this commit
- Uses syslinux menus
- Can be directly copied with dd to a USB device
- Can be burned to
The update is needed to support generation of EFI boot images that
work with optical media. Specifically the -eltorito-platform efi
capability for mkisofs is needed.
[YOCTO #4100]
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
.../cdrtools/cdrtools-native_3.00.bb |
The usual format for the commit summary is as follows:
lttng: Enable ptest support
Please see the Commit/Patch message guideline for details:
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Thanks
Sau!
On 09/11/2013 06:09 PM, Stefan Seefeld wrote:
Signed-off-by:
On 2013-09-12 13:13, Saul Wold wrote:
The usual format for the commit summary is as follows:
lttng: Enable ptest support
Please see the Commit/Patch message guideline for details:
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Thanks, I'll follow that guideline for my
On Fri, Aug 23, 2013 at 11:59:53PM +0200, Martin Jansa wrote:
On Tue, Aug 20, 2013 at 02:21:05PM +, g...@git.openembedded.org wrote:
Module: openembedded-core.git
Branch: master
Commit: 176e5c5bfdeb2529cc40e35870ac49d75439dfeb
URL:
This should fix the case where neon code is emitted for machines
which dont have neon unit in the chip
[YOCTO# 5161]
Signed-off-by: Khem Raj raj.k...@gmail.com
---
.../0001-ARM-Pass-dl_hwcap-to-IFUNC-resolver.patch | 43 ++
meta/recipes-core/eglibc/eglibc_2.18.bb
On 09/12/2013 08:18 PM, Martin Jansa wrote:
On Thu, Sep 12, 2013 at 07:18:12PM +0800, ChenQi wrote:
On 09/12/2013 06:25 PM, Martin Jansa wrote:
On Thu, Sep 12, 2013 at 05:43:55PM +0800, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
If a package inherits
From: Chen Qi qi.c...@windriver.com
In rootfs_uninstall_unneeded function, the update-rc.d package would
be removed if no 'package-management' and no delayed postinsts.
However, in update-rc.d.bbclass, the update-rc.d package is only
recommended. Thus, if NO_RECOMMENDATIONS is enabled or
From: Chen Qi qi.c...@windriver.com
The following changes since commit bd76847d867f9f76f76f033439cfb834cf59380f:
libnewt-python: Don't write a whiptail package (2013-09-12 08:23:42 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib
On Thu, 2013-09-12 at 08:47 -0700, Flanagan, Elizabeth wrote:
This will need a LAYERVERSION_core bump for autobuilder compatibility.
I've queued on in master-next along with this patch.
Cheers,
Richard
___
Openembedded-core mailing list
On Thu, 2013-09-12 at 12:19 -0500, Jason Wessel wrote:
The syslinux.bbclass already has support for automatically generated
serial and graphics menu choices. This patch adds the same concept to
the grub-efi menu. That makes it possible to generate a single image
which can boot on a PCBIOS or
The patch redhat-portability.diff causes this issue
so lets revert the portion which was using %a instead of %m
thats recommended anyway, redhat patch seems to be targetting
old compilers.
Signed-off-by: Khem Raj raj.k...@gmail.com
---
.../elfutils/elfutils/fix-build-gcc-4.8.patch | 44
In busybox, util-linux and shadow, su has been moved to /usr/bin/,
but lsb cmdchk needs su in /bin.
Move su to /bin could fix this issue.
[YOCTO #5175]
Signed-off-by: Hongxu Jia hongxu@windriver.com
---
.../busybox/busybox-1.21.1/su-usr-bin.patch| 26 --
*Problem
LSB Command Check failed
...
su 1 failed
install_initd 1 failed
remove_initd 1 failed
...
The journal shows the command didsn't exist.
...
Looking for command su
Looking for command install_initd
Looking for command remove_initd
...
//Hongxu
The following changes since commit
The install_initd and remove_initd are linked to /sbin/chkconfig for lsb
core test, and chkconfig has been moved from /sbin to /usr/sbin in order
to fix QA warning about unsafe references in binaries.
(In commit e486242db83297701803866bea971a2f1a1135fe)
Let install_initd and remove_initd link to
In busybox, util-linux and shadow, su has been moved to /usr/bin/,
but lsb cmdchk needs su in /bin.
Move su to /bin could fix this issue.
[YOCTO#5175]
Signed-off-by: Hongxu Jia hongxu@windriver.com
---
meta/recipes-extended/shadow/shadow_4.1.4.3.bb | 3 ++-
1 file changed, 2 insertions(+),
In busybox, util-linux and shadow, su has been moved to /usr/bin/,
but lsb cmdchk needs su in /bin.
Move su to /bin could fix this issue.
[YOCTO#5175]
Signed-off-by: Hongxu Jia hongxu@windriver.com
---
meta/recipes-core/util-linux/util-linux.inc | 4 ++--
1 file changed, 2 insertions(+), 2
On Sep 3, 2013, at 6:45 PM, Mark Hatle mark.ha...@windriver.com wrote:
On 9/3/13 4:13 PM, Francois Retief wrote:
Hi all,
Thanks to Richard's recent improvements in the oe-core tree, I finally got my
first MinGW build to compile through and generate a SDK tarball.
Next issue is that on
74 matches
Mail list logo
