On 11/07/2013 09:45 PM, Khem Raj wrote:
On Nov 7, 2013, at 9:20 PM, Saul Wold wrote:
On 11/06/2013 06:33 PM, Khem Raj wrote:
From: Mihaela Sendrea
Nedeed for gcc-runtime tests.
Fixed build on multilib and add patch to remove
!/depot/path/expect -f
which caused rpm to puke on rfs generatio
To avoid a implicit build result.
Signed-off-by: Ming Liu
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/qemu/qemu.inc
b/meta/recipes-devtools/qemu/qemu.inc
index 702fe01..26b670b 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
On Nov 7, 2013, at 9:20 PM, Saul Wold wrote:
> On 11/06/2013 06:33 PM, Khem Raj wrote:
>> From: Mihaela Sendrea
>>
>> Nedeed for gcc-runtime tests.
>>
>> Fixed build on multilib and add patch to remove
>> !/depot/path/expect -f
>> which caused rpm to puke on rfs generation
>>
>
> I did 2 bu
On Thu, Nov 7, 2013 at 9:20 PM, Saul Wold wrote:
> On 11/06/2013 06:33 PM, Khem Raj wrote:
>>
>> From: Mihaela Sendrea
>>
>> Nedeed for gcc-runtime tests.
>>
>> Fixed build on multilib and add patch to remove
>> !/depot/path/expect -f
>> which caused rpm to puke on rfs generation
>>
>
> I did 2 b
On 11/06/2013 06:33 PM, Khem Raj wrote:
From: Mihaela Sendrea
Nedeed for gcc-runtime tests.
Fixed build on multilib and add patch to remove
!/depot/path/expect -f
which caused rpm to puke on rfs generation
I did 2 builds locally and this patch worked, but on the Autobuilder I
got the a fai
On 13-11-07 06:16 PM, Saul Wold wrote:
On 11/07/2013 10:36 AM, Konrad Scherer wrote:
From: Konrad Scherer
Turns out the sed command has not been working as intended since
kernel 3.1 due to the trailing space. Adding the WERROR=0 environment
variable is the correct way to disable warnings as er
On 11/8/2013 8:42 AM, Saul Wold wrote:
On 11/07/2013 03:30 AM, jackie.hu...@windriver.com wrote:
From: Jackie Huang
grub-efi-native builds grub with efi platform, then run
"grub-mkimage" command with built in cfg and modules to
generate an EFI binary for the target, and deploys it.
It works
The gst-ffmpeg and gst-libav packages have always produced this warning.
It is actually caused by the libav/ffmpeg code. I have seen several
attempts at fixing this (both for gst-ffmpeg/libav and for the dedicated
ffmpeg/libav recipes), but wasn't sure which one to pick, and figured
that the ri
On 11/07/2013 07:59 AM, Jack Mitchell wrote:
From: Jack Mitchell
libjson is now known as json-c, support for the old namespace is
disabled as it seems to break SEPBUILDDIR configs. Built without
parallel make as it fails, official word is not to bother trying.
Signed-off-by: Jack Mitchell
---
On 11/07/2013 03:30 AM, jackie.hu...@windriver.com wrote:
From: Jackie Huang
grub-efi-native builds grub with efi platform, then run
"grub-mkimage" command with built in cfg and modules to
generate an EFI binary for the target, and deploys it.
It works fine when build on 64bit host, but when w
On 11/07/2013 11:47 AM, Carlos Rafael Giani wrote:
starting with this version, the recipes enable Orc acceleration by
default
This patch introduces a QA Warning:
WARNING: QA Issue: ELF binary
'/srv/ssd/sgw/builds/world/tmp/work/core2-poky-linux/gstreamer1.0-libav/1.2.0-r1/packages-split/gstr
Richard,
Built tested and reviewed.
This adds ORC from meta-oe to support gstreamer 1.2, I have also included
Peter's U-A replacement for binutils-symlinks.
Sau!
The following changes since commit 1dbd65b4d14319e784a66776c1e9943d0179d3ee:
toolchain-scripts/meta-environment: Further cleanup
On Wed, 2013-11-06 at 09:45 +0100, Andrea Adami wrote:
> On Mon, Nov 4, 2013 at 11:13 PM, Andrea Adami wrote:
> > On Mon, Nov 4, 2013 at 12:10 AM, Richard Purdie
> > wrote:
> >> On Sun, 2013-11-03 at 23:16 +0100, Andrea Adami wrote:
> >>> I have to report an undesiderate behavior:
> >>>
> >>> the
An empty distro value leads to OVERRIDES and FILESOVERRIDES containing
"::" entries which causes odd issues such as files being included when
they shouldn't be. We could put in anonymous python to guard against
empty entries but its messy and setting a default value for DISTRO to
something harmless
On 11/07/2013 10:36 AM, Konrad Scherer wrote:
From: Konrad Scherer
Turns out the sed command has not been working as intended since
kernel 3.1 due to the trailing space. Adding the WERROR=0 environment
variable is the correct way to disable warnings as errors.
So, I recently saw this failure:
On Thu, 2013-11-07 at 13:58 -0200, Otavio Salvador wrote:
> On Wed, Nov 6, 2013 at 9:42 PM, Richard Purdie
> wrote:
> > On Wed, 2013-11-06 at 16:51 -0200, Otavio Salvador wrote:
> >> On Tue, Nov 5, 2013 at 8:15 PM, Richard Purdie
> >> wrote:
> >> > packagegroups are allarch and shouldn't change d
On Thu, 2013-11-07 at 16:08 +0100, Enrico Scholz wrote:
> Martin Jansa
> writes:
>
> > Why not add "before" param to addtask?
> >
> > addtask bundle_initramfs after do_compile before do_build
> >
> > could do the trick
>
> no; due to
>
> do_bundle_initramfs[nostamp] = "1"
>
> a (non-initramf
starting with this version, the recipes enable Orc acceleration by
default
Signed-off-by: Carlos Rafael Giani
---
.../gstreamer/gstreamer1.0-libav.inc | 2 +-
.../gstreamer1.0-libav/libav_e500mc.patch | 21
...-libav_1.0.9.bb => gstreamer1.0-libav_1.2.0.bb} | 13 +
On Tue, 2013-11-05 at 22:21 -0500, Bruce Ashfield wrote:
> On Tue, Nov 5, 2013 at 3:56 PM, Phil Blundell wrote:
> > On Tue, 2013-11-05 at 13:47 -0500, Bruce Ashfield wrote:
> >> I don't have anything extra to add outside of what I put in the
> >> patch commit log ..
> >
> > That's certainly a good
From: Konrad Scherer
Turns out the sed command has not been working as intended since
kernel 3.1 due to the trailing space. Adding the WERROR=0 environment
variable is the correct way to disable warnings as errors.
Signed-off-by: Konrad Scherer
---
meta/recipes-kernel/perf/perf.bb | 4
1
The original method to remove -Werror using sed does not work on
kernels after 3.1 due to trailing space. To avoid build failures due to
warnings as errors add the WERROR env variable.
---
Konrad Scherer, MTS, Linux Products Group, Wind River
___
Openem
On Thu, Nov 7, 2013 at 10:55 AM, Seth Bollinger wrote:
> I've tried setting EXTRA_OECONF --with-python, but it doesn't appear to be
> having much affect.
>
> I'm currently trying to hack together using python manually to build the
> install, but this feels like I'm moving in the wrong direction.
Hello All,
I've been trying to build a non-native version of the libxml2 python module
and am having nothing but trouble.
I've tried setting EXTRA_OECONF --with-python, but it doesn't appear to be
having much affect.
I'm currently trying to hack together using python manually to build the
instal
From: Jack Mitchell
libjson is now known as json-c, support for the old namespace is
disabled as it seems to break SEPBUILDDIR configs. Built without
parallel make as it fails, official word is not to bother trying.
Signed-off-by: Jack Mitchell
---
v4:
- add --disable-oldname-compat to try
On Wed, Nov 6, 2013 at 9:42 PM, Richard Purdie
wrote:
> On Wed, 2013-11-06 at 16:51 -0200, Otavio Salvador wrote:
>> On Tue, Nov 5, 2013 at 8:15 PM, Richard Purdie
>> wrote:
>> > packagegroups are allarch and shouldn't change depending on the target
>> > or machine selected. In general they shoul
Martin Jansa
writes:
> Why not add "before" param to addtask?
>
> addtask bundle_initramfs after do_compile before do_build
>
> could do the trick
no; due to
do_bundle_initramfs[nostamp] = "1"
a (non-initramfs) kernel will be rebuilt everytime although nothing has
been changed. The initramf
I'm following recent master changes in a build tree that just
gets updated, not necessarily rebuilt. With this, I just got
this error:
libpng warning: Application was compiled with png.h from libpng-1.6.6
libpng warning: Application is running with png.c from libpng-1.2.50
libpng error:
On 7 November 2013 12:32, Laurentiu Palcu wrote:
> Why don't you use the -M option when formatting your patches? It
> would be easier to skip over renames when reviewing the patches...
Because I'm getting forgetful in my old age? :/ I'll configure
send-email to always use it.
Ross
_
Ping
On 10/31/2013 09:14 AM, rongqing...@windriver.com wrote:
From: Roy Li
Create connman-evn.service, which will run a script to compute the networking
device when nfs root is on, and pass the result to connman.service
Copy Connmand.service from source code, add ExecStartPre into it to relea
From: Lu Chong
service --status-all command will display wrong status for avahi-daemon.
This commit fix this error prompt and make service display right status
for avahi-daemon.
Signed-off-by: Lu Chong
---
meta/recipes-connectivity/avahi/avahi.inc |1 +
...ahi-fix-avahi-status-com
Why don't you use the -M option when formatting your patches? It
would be easier to skip over renames when reviewing the patches...
Laurentiu
On Thu, Nov 07, 2013 at 12:06:04PM +, Ross Burton wrote:
> The xinerama and dixstruct patches are merged in 1.14.4, so drop them.
>
> Also drop explic
Is it safe and/or sane to put TOPDIR in BB_HASHBASE_WHITELIST?
In my own recipes I make a few uses of TOPDIR and this is causing their
signatures to change between different trees. Simply adding it to
BB_HASHBASE_WHITELIST would avoid this problem but since TOPDIR is quite
fundamental I wondered i
The xinerama and dixstruct patches are merged in 1.14.4, so drop them.
Also drop explicit PR statement.
Signed-off-by: Ross Burton
---
...-fix-segfaults-char-is-unsigned-for-ARM-a.patch | 39
.../xorg-xserver/xserver-xorg-1.14.0/aarch64.patch | 35 --
..
Drop two patches that were backported from upstream.
Signed-off-by: Ross Burton
---
meta/recipes-graphics/cogl/cogl-1.0.inc|4 ---
meta/recipes-graphics/cogl/cogl-1.0_1.14.0.bb |7 -
meta/recipes-graphics/cogl/cogl-1.0_1.16.0.bb |6
.../cogl/files/cogl-
Remove backported patches that are now integrated.
No need to patch build to install examples with --enable-demo-clients, update
FILES now that all examples are being installed.
Remove cairo-gl option as our cairo doesn't support GL (yet), remove
--disable-android-compositor as it was dropped ups
Weston 1.3 needs to run on a VT, which is typically handled by weston-launch.
Currently weston-init doesn't use weston-launch as that depends on the
(non-default) pam DISTRO_FEATURE, so depend on kbd and use openvt directly.
This also fixes problems caused by the init script blocking until Weston
wayland-scanner now uses pkg-config instead of hard-coding paths, so edit the
script to use pkg-config-native.
Based on work by Ewan Le Bideau-Canevet .
Signed-off-by: Ross Burton
---
meta/recipes-graphics/wayland/wayland_1.1.0.bb | 39
meta/recipes-graphics/wayland/w
Delete fix-wayland-deps.patch, it was a backport from upstream.
Delete enable_tests which installed the non-inuititive interactive test suite,
instead install the examples.
Signed-off-by: Ross Burton
---
.../clutter/clutter-1.0-1.14.4/enable_tests.patch | 36 -
.../clutter-1.0-1.
From: Jackie Huang
grub-efi-native builds grub with efi platform, then run
"grub-mkimage" command with built in cfg and modules to
generate an EFI binary for the target, and deploys it.
It works fine when build on 64bit host, but when we build
x86-64 target on 32bit host, it fails to build 64bit
From: Jackie Huang
Tested on the follwoing host:
rhel6.2 32bit, gcc 4.4.6
suse 12.2 32bit, gcc 4.7.1
ubuntu 12.04 64bit, gcc 4.6.3
centOS 5.9 64bit, gcc 4.1.2 (still faill since grub require gcc 4.1.3+)
--
The following changes since commit 1dbd65b4d14319e784a66776c1e9943d0179d3ee:
toolchain-
n lower than 4.4, but we don't need to use
memory over 4GiB, so add a patch to allow compilation
without large model support.
(LOCAL REV: NOT UPSTREAM) -- Sent to oe-core on 20131107)
Signed-off-by: Jackie Huang
---
...allow-a-compilation-without-mcmodel-large.patch | 69 ++
AL REV: NOT UPSTREAM) -- Sent to oe-core on 20131107)
Signed-off-by: Jackie Huang
---
...allow-a-compilation-without-mcmodel-large.patch | 69
meta/recipes-bsp/grub/grub-efi-native_2.00.bb | 52 ++-
meta/recipes-bsp/grub/grub-efi.inc |
From: Jackie Huang
Tested on the follwoing host:
rhel6.2 32bit, gcc 4.4.6
suse 12.2 32bit, gcc 4.7.1
ubuntu 12.04 64bit, gcc 4.6.3
centOS 5.9 64bit, gcc 4.1.2 (still faill since grub require gcc 4.1.3+)
--
The following changes since commit 1dbd65b4d14319e784a66776c1e9943d0179d3ee:
toolchain-
On 7 November 2013 11:03, wrote:
> From: Wenzong Fan
>
> Just ship these sources to their own dbg packages instead of udev-dbg:
>
> libudev* -> libudev-dbg
> gudev* -> libgudev-dbg
> others -> udev-dbg
Why do this? Multiple -dbg packages could make sense in a recipe
which build
From: Wenzong Fan
Currently all source files will be shipped to udev-dbg regardless they
should belong libudev-dbg or libgudev-dbg, just update the FILES list
to ship those files to their own packages:
libudev-dbg: libudev*, libgudev-dbg: gudev*, udev-dbg: others
Signed-off-by: Wenzong Fan
From: Wenzong Fan
Just ship these sources to their own dbg packages instead of udev-dbg:
libudev* -> libudev-dbg
gudev* -> libgudev-dbg
others -> udev-dbg
The following changes since commit d6cc7c8ed76c8b1117cf03c7bd4b0742f98f79b3:
toolchain-scripts/meta-environment: Further
On 7 November 2013 10:49, Carlos Rafael Giani wrote:
> The make 4.0 issue is already fixed in the glibc and eglibc repositories, so
> this patch should be marked with "Upstream-Status: inappropiate [other]".
The log says its a backport of an upstream fix, so Upstream-Status:
Backport is correct.
I just tested Jonathan Liu's patch with Yocto 1.5 . It works for me, I
was able to build a rootfs. Using Arch Linux and make 4.0.
The make 4.0 issue is already fixed in the glibc and eglibc
repositories, so this patch should be marked with "Upstream-Status:
inappropiate [other]".
On 2013-11-04
On Monday 04 November 2013 12:42:59 Stoicescu, CorneliuX wrote:
> On Monday 04 November 2013 14:35:00 Richard Purdie wrote:
> > On Mon, 2013-11-04 at 12:14 +, Paul Eggleton wrote:
> > > On Monday 04 November 2013 09:31:19 Richard Purdie wrote:
> > > The basic idea with buildhistory is to only k
Hi all,
I didn't notice if it was already announced here, but the CFP for the FOSDEM
Embedded dev room in 2014 is open:
https://lists.fosdem.org/pipermail/fosdem/2013-October/001870.html
It would be great to have some folks give OpenEmbedded/Yocto Project-related
presentation(s) this year - we
> On 10/10/2013 06:36 AM, yaoxp wrote:
> > Hi all,
> >
> > If build cronie without --with-syscrontab, the /etc/crontab will not work.
> >
>
> I ran a test without this and the /etc/crontab file was read and the
> cron entry was executed, can you explain more clearly what you observed?
>
My build
51 matches
Mail list logo
