I met a similar error, maybe we can add:
COMPATIBLE_HOST = (x86_64.*|i.86.*)-linux
to gummiboot_git.bb to fix the problem.
I will send a patch for it, and fix another gnu-efi error.
// Robert
On 03/27/2014 04:18 AM, Martin Jansa wrote:
On Tue, Mar 11, 2014 at 04:23:55PM +,
The following changes since commit ae938eba92b2c89a9fd91161e57c5dbc594ad4ad:
local.conf.sample.extended: update it for the archiver (2014-03-26 12:15:44
+)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ciorga/YB5795
LSB lsb_log_message calls a begin()
function that should be implemented
in /etc/init.d/functions.
The aforementioned script does not
implement the begin() function, as
such there is a small issue related to logging.
This fix implements a local version of
the function, while cleaning up the
The following changes since commit 109f6731210053ac6c490fc49956d0f65078f0ef:
util-linux-native: fix qsort_r for CentOS 5.10 (2014-03-27 03:45:56 -0400)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/gummiboot
Its LIBDIR in Makefile is:
LIBDIR = $(PREFIX)/lib
This is incorrect for 64 bit bsp, thus will cause build failures on gummiboot:
ld: cannot open linker script file /path/to/usr/lib64/elf_x86_64_efi.lds: No
such file or directory
[YOCTO #6053]
Signed-off-by: Robert Yang
Fix the warning:
WARNING: QA Issue: gummiboot: Files/directories were installed but not shipped
/usr/lib
/usr/lib/gummiboot
/usr/lib/gummiboot/gummibootx64.efi
This is because it uses /usr/lib in gummibootlibdir, use ${libdir} to
fix it.
Signed-off-by: Robert Yang liezhi.y...@windriver.com
Fix the error:
[snip]
| nm -D -u src/efi/gummiboot.so | grep ' U ' exit 1 || :
| objcopy -j .text -j .sdata -j .data -j .dynamic \
| -j .dynsym -j .rel -j .rela -j .reloc -j .eh_frame \
| --target=efi-app-x86_64 src/efi/gummiboot.so gummibootx64.efi
| objcopy: src/efi/gummiboot.so: Invalid
The gummiboot depends on gnu-efi which had set:
COMPATIBLE_HOST = (x86_64.*|i.86.*)-linux
We also need set this for gummiboot, otherwise there would be build
failures for other non-x86 archs.
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
meta/recipes-bsp/gummiboot/gummiboot_git.bb |
The test failed when more than 1 error or 1 warning is present.
Also pasting the bitbake output when the test fails.
Signed-off-by: Corneliu Stoicescu corneliux.stoice...@intel.com
---
meta/lib/oeqa/selftest/bbtests.py | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
On 2014-03-25 15:31, David Nyström wrote:
On 2014-03-24 17:00, Richard Purdie wrote:
As development on 1.6 finishes up, its time to think about what we
should be doing in the 1.7 cycle.
I think from my perspective, in 1.7 I'd like to see us looking at
Developer Workflow. Its a generic topic
On Thu, Mar 27, 2014 at 04:11:22AM -0400, Robert Yang wrote:
The gummiboot depends on gnu-efi which had set:
COMPATIBLE_HOST = (x86_64.*|i.86.*)-linux
We also need set this for gummiboot, otherwise there would be build
failures for other non-x86 archs.
Signed-off-by: Robert Yang
On 03/26/2014 11:07 PM, Otavio Salvador wrote:
From: Prabhu Sundararaj prabhu.sundara...@freescale.com
Signed-off-by: Prabhu Sundararaj prabhu.sundara...@freescale.com
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
meta/recipes-graphics/wayland/weston_1.4.0.bb | 7 +--
1 file
The old implementation was wrong. It was not very generic and it checked
IMAGE_FEATURES while building the recipe, which led to various issues
with the generation of the final script. That is, the run-postinsts
script was generated once, while building the package for the first
time. Hence, any
The following changes since commit 0150bc30d3674301631c2e9b6c64e01058fd1070:
bitbake: runqueue: Really fix sigchld handling (2014-03-18 23:05:53 +)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib lpalcu/b5666_unique_run_postinsts
On 26 March 2014 22:12, Burton, Ross ross.bur...@intel.com wrote:
On 26 March 2014 22:04, Khem Raj raj.k...@gmail.com wrote:
There were interest in other threads in having musl as an alternative
to eglibc/uclibc that we already have in OE, in that direction I have
poured in my on and off work
Build Appliance includes a more recent version
of poky, up to commit:
ae938eba92b2c89a9fd91161e57c5dbc594ad4ad.
Adds bitbake fixes/optimizations;
Signed-off-by: Cristian Iorga cristian.io...@intel.com
---
meta/recipes-core/images/build-appliance-image_8.0.bb | 2 +-
1 file changed, 1
The following changes since commit c4eeaa8e35e926b6d1f633549f76d1ba9ed9278b:
bitbake: knotty: Show a link to the logfile for failed setscene tasks
(2014-03-27 10:42:08 +)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ciorga/BA-update
On 03/27/2014 07:39 PM, Martin Jansa wrote:
On Thu, Mar 27, 2014 at 04:11:22AM -0400, Robert Yang wrote:
The gummiboot depends on gnu-efi which had set:
COMPATIBLE_HOST = (x86_64.*|i.86.*)-linux
We also need set this for gummiboot, otherwise there would be build
failures for other non-x86
On 03/27/2014 10:48 PM, Robert Yang wrote:
On 03/27/2014 07:39 PM, Martin Jansa wrote:
On Thu, Mar 27, 2014 at 04:11:22AM -0400, Robert Yang wrote:
The gummiboot depends on gnu-efi which had set:
COMPATIBLE_HOST = (x86_64.*|i.86.*)-linux
We also need set this for gummiboot, otherwise
Hi Khem,
On Friday, March 21, 2014 6:06 PM, Khem Raj wrote:
On Fri, Mar 21, 2014 at 9:45 AM, Mark Hatle mark.ha...@windriver.com wrote:
On 3/21/14, 7:10 AM, Mats Kärrman wrote:
Hi,
On: Thursday, March 13, 2014 11:36 AM, Mats Kärrman wrote:
My home made hard float tune for PowerPC looks
On Mar 27, 2014 8:16 AM, Mats Kärrman mats.karr...@tritech.se wrote:
Hi Khem,
On Friday, March 21, 2014 6:06 PM, Khem Raj wrote:
On Fri, Mar 21, 2014 at 9:45 AM, Mark Hatle mark.ha...@windriver.com
wrote:
On 3/21/14, 7:10 AM, Mats Kärrman wrote:
Hi,
On: Thursday, March 13, 2014
On Thu, Mar 27, 2014 at 1:11 AM, Robert Yang liezhi.y...@windriver.com wrote:
The gummiboot depends on gnu-efi which had set:
COMPATIBLE_HOST = (x86_64.*|i.86.*)-linux
We also need set this for gummiboot, otherwise there would be build
failures for other non-x86 archs.
isn't gnu-efi
The following changes since commit c4eeaa8e35e926b6d1f633549f76d1ba9ed9278b:
bitbake: knotty: Show a link to the logfile for failed setscene tasks
(2014-03-27 10:42:08 +)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib lpalcu/b6049_do_rootfs_crash
If the locks are not removed, the output of the next rpm command
executed will contain the following string:
rpmdb: BDB1540 configured environment flags incompatible with
existing environment
And this will create various parsing issues.
[YOCTO #6049]
Signed-off-by: Laurentiu Palcu
Excellent information! Thanks for all the workflow examples, this is great.
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
On 3/27/14, 11:18 AM, Laurentiu Palcu wrote:
If the locks are not removed, the output of the next rpm command
executed will contain the following string:
rpmdb: BDB1540 configured environment flags incompatible with
existing environment
This usually means that RPM was not called with the same
Changelog since 2014-03-16 until 2014-03-23. Projects included in this report:
bitbake: git://git.openembedded.org/bitbake
openembedded-core: git://git.openembedded.org/openembedded-core
meta-openembedded: git://git.openembedded.org/meta-openembedded
meta-angstrom:
On Mon, Mar 24, 2014 at 8:10 PM, Robert Yang liezhi.y...@windriver.comwrote:
If we run bitbake -S base-files today, and re-run it tomorrow with
nothing changed, we would see that the do_install.sigdata changes
because of:
do_intall - do_install_basefilesissue - DISTRO_VERSION - DATE
We had
On Thu, 2014-03-27 at 10:21 -0700, Chris Larson wrote:
On Mon, Mar 24, 2014 at 8:10 PM, Robert Yang
liezhi.y...@windriver.com wrote:
If we run bitbake -S base-files today, and re-run it
tomorrow with
nothing changed, we would see that the do_install.sigdata
On Thu, Mar 27, 2014 at 10:49 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Thu, 2014-03-27 at 10:21 -0700, Chris Larson wrote:
On Mon, Mar 24, 2014 at 8:10 PM, Robert Yang
liezhi.y...@windriver.com wrote:
If we run bitbake -S base-files today, and re-run it
The package's LICENSE.txt is pretty clear that this is licened under MIT and
LGPLv2.1, not MIT and GPL.
Signed-off-by: Mark Asselstine mark.asselst...@windriver.com
---
meta-oe/recipes-devtools/python/python-pip_1.3.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Thu, Mar 27, 2014 at 9:30 AM, Valentin Popa valentin.p...@intel.com wrote:
On 03/26/2014 11:07 PM, Otavio Salvador wrote:
From: Prabhu Sundararaj prabhu.sundara...@freescale.com
Signed-off-by: Prabhu Sundararaj prabhu.sundara...@freescale.com
Signed-off-by: Otavio Salvador
On Thu, Mar 27, 2014 at 10:53:20AM -0700, Chris Larson wrote:
On Thu, Mar 27, 2014 at 10:49 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Thu, 2014-03-27 at 10:21 -0700, Chris Larson wrote:
On Mon, Mar 24, 2014 at 8:10 PM, Robert Yang
liezhi.y...@windriver.com
Signed-off-by: Drew Moseley drew_mose...@mentor.com
---
.../zisofs-tools/zisofs-tools-native_1.0.8.bb |2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/zisofs-tools/zisofs-tools-native_1.0.8.bb
b/meta/recipes-devtools/zisofs-tools/zisofs-tools-native_1.0.8.bb
Updating the 3.10 meta SRCREV to include the valleyisland IO .scc and
configuration files.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 2 +-
Updating the meta SRCREV with the latest configuration updates.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 2
Andrea Adami reported the following build failure:
.../drm/drm_mm.h:105:2: error: implicit declaration of function
'BUG_ON' [-Werror=implicit-function-declaration]
| BUG_ON(!hole_node-hole_follows);
| ^
| CC drivers/pci/setup-res.o
| CC
Updating to the latest -stable release.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 16
Importing the following configuration changes to support the latest intel
common BSPs:
6e0e756d5137 intel-common: Remove GMA500 support
226c3b7a2b82 intel-core*: Add baytrail soc support
25df7acf2cc4 baytrail: Add feature/soc/baytrail
8715856ab617 meta: input: add CONFIG_INPUT dependency
Updating to the latest korg -stable release.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 8
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 18
Richard/Saul,
Here are the udpates to the various kernels that have been soaked and
tested long enough to head into the main trees.
3.4:
- minor configuration updates for the monhonpeak
3.10:
- BSP configuration updates
- korg stable integrations
- build fixes
3.8:
- removal
3.14:
3.14 is now the reference for libc-headers. After building and booting 3.x based
BSPs against the 3.14 headers, we can safely remove the old version and patches
that are now part of the mainline kernel.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
Bumping the meta branch SRCREV for the following two commits:
df3aa753c882 intel-common: Add media-all to the standard builds
4b0d57269dae intel-common: Add mohonpeak BSP
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 2 +-
Importing the following two meta data changes for EFI configuration:
284e9589436a meta: efi.cfg/efi-ext.cfg: add EFIVAR_FS to default efi fragment
0a8c4971e2d9 meta: update efi config fragment to include EFI_STUB by default
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
Yocto 1.6 will support the LTSI 3.4/3.10 kernels and the 3.14 kernel. As
such, we remove the 3.8 linux-yocto recipes to keep our number of supported
kernels at three.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb | 30
Introduce the 3.14 linux-libc-headers recipe, now that the 3.14 kernel is
available, and the default for the qemu reference BSPs.
The three patches which were required for the previous 3.10 libc-headers
are not required for 3.14 and can be ignored.
Signed-off-by: Bruce Ashfield
The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
the versioned recipes here.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21
meta/recipes-kernel/linux/linux-yocto_3.14.bb | 37
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/distro/include/tcmode-default.inc
b/meta/conf/distro/include/tcmode-default.inc
index
On 3/27/14, 1:13 PM, Martin Jansa wrote:
On Thu, Mar 27, 2014 at 10:53:20AM -0700, Chris Larson wrote:
On Thu, Mar 27, 2014 at 10:49 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Thu, 2014-03-27 at 10:21 -0700, Chris Larson wrote:
On Mon, Mar 24, 2014 at 8:10 PM, Robert
On Tue, 2014-03-25 at 23:42 -0300, João Henrique Ferreira de Freitas
wrote:
Hi,
These patchs allows the user create the following directdisk-multi-rootfs.wks
file:
part /boot --source bootimg-pcbios --ondisk sda --fstype=msdos \
--label boot --active --align 1024
part /
On 27 March 2014 18:08, Khem Raj raj.k...@gmail.com wrote:
On Thu, Mar 27, 2014 at 1:11 AM, Robert Yang liezhi.y...@windriver.com
wrote:
The gummiboot depends on gnu-efi which had set:
COMPATIBLE_HOST = (x86_64.*|i.86.*)-linux
We also need set this for gummiboot, otherwise there would be
Hi,
These patchs allows the user create the following directdisk-multi-rootfs.wks
file:
part /boot --source bootimg-pcbios --ondisk sda --fstype=msdos \
--label boot --active --align 1024
part / --source rootfs --ondisk sda --fstype=ext3 --label primary --align 1024
part /standby
Implement RootfsPlugin class. The do_prepare_partition() method
is implemented using code in Wic_PartData class.
This class have 'rootfs' name, which is the name that should
be used in the --source parameters of the .wks partition commands.
Signed-off-by: João Henrique Ferreira de Freitas
The do_prepare_partition() method from RootfsPlugin class need
to know what will be the rootfs_dir. This makes sense when .wks
file has a partition set up like this:
part /standby --source rootfs --rootfs-dir=special rootfs ...
then do_prepare_partition() will work with the correct rootfs.
Remove the 'rootfs' case when internal call code is used and
replace to call the general-purpose plugin.
For now RootfsPluing class continues to invoke prepare_rootfs()
method from Wic_PartData. However RootfsPlugin could implement them.
Signed-off-by: João Henrique Ferreira de Freitas
When a partition from .wks file is set up like this:
part /standby --source rootfs --rootfs-dir=special rootfs ... --label \
--label secondary
This means that 'rootfs' must use 'special rootfs' as rootfs and
the default partition filename in /var/tmp/wic/build/ will be create
using the
The '--rootfs-dir' option is optional and only takes efect is a
partition is set up like this:
part /standby --source rootfs --rootfs-dir=special rootfs ...
So '--rootfs-dir' is used instead of bitbake ROOTFS_DIR variable or
'-r' param.
Signed-off-by: João Henrique Ferreira de Freitas
When a .wks has more than one ROOTFS_DIR it's better to report
all ROOTFS_DIR that was used to create the image.
Signed-off-by: João Henrique Ferreira de Freitas joa...@gmail.com
---
scripts/lib/mic/imager/direct.py | 18 ++
The wic command-line param --rootfs-dir gets generalized to support
multiple directories. Each '--rootfs-dir' could be connected using a
special string, that should be present in .wks. I.e:
wic create ... --rootfs-dir rootfs1=/some/rootfs/dir \
--rootfs-dir rootfs2=/some/other/rootfs/dir
Hi Tom,
Em 27-03-2014 17:15, Tom Zanussi escreveu:
On Tue, 2014-03-25 at 23:42 -0300, João Henrique Ferreira de Freitas
wrote:
Hi João,
I'm having some trouble creating an image, looks like the assignment to
krootfs_dir['ROOTFS_DIR'] is bogus?:
I am going to prepare a v3 to fix it.
On Thu, Mar 27, 2014 at 1:11 AM, Robert Yang liezhi.y...@windriver.com wrote:
++OBJCOPY ?= objcopy
if it is a automake file you could also try
OBJCOPY = @OBJCOPY@
instead of above weak assignment.
--
___
Openembedded-core mailing list
On 03/28/2014 02:31 AM, Mark Hatle wrote:
On 3/27/14, 1:13 PM, Martin Jansa wrote:
On Thu, Mar 27, 2014 at 10:53:20AM -0700, Chris Larson wrote:
On Thu, Mar 27, 2014 at 10:49 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Thu, 2014-03-27 at 10:21 -0700, Chris Larson
On 03/28/2014 08:49 AM, Khem Raj wrote:
On Thu, Mar 27, 2014 at 1:11 AM, Robert Yang liezhi.y...@windriver.com wrote:
++OBJCOPY ?= objcopy
if it is a automake file you could also try
OBJCOPY = @OBJCOPY@
instead of above weak assignment.
Hello Khem,
I had tried that before, but it
On 2014年03月26日 22:42, Otavio Salvador wrote:
Hello Kai,
On Wed, Mar 26, 2014 at 7:15 AM, Kai Kang kai.k...@windriver.com wrote:
Replace ocf-linux with cryptodev-linux because linux-yocto use cryptodev-linux
to implement /dev/crypto.
Thanks for handling it; I was going to address same issue
64 matches
Mail list logo