On 1/25/17 9:50 PM, Herve Jourdain wrote:
> Hi Jacob,
>
> I've been able to compile chromium-wayland 53.0.2785.14 on RaspberryPi, with
> Wayland only (no X11), BUT I had to add an additional patch for it to work,
> or else I get an error in ui/events/keycodes/keyboard_code_conversion_xkb.cc.
>
On 1/25/17 8:38 AM, Burton, Ross wrote:
> On 25 January 2017 at 16:18, Martin Jansa wrote:
>
>> Why do we need this in meta-oe? Just because xtscal was dumped here as
>> well?
>>
>
> Yes. xtscal etc are the only users, so they're in oe-core with nothing
> using them. They should have moved t
what happens if commits are already having a sign-off ?
On 1/26/17 2:27 PM, Max Krummenacher wrote:
> ping
>
> Any comments on this one?
>
> Max
>
> 2017-01-17 0:09 GMT+01:00 Max Krummenacher :
>> Prevent missing Signed-off-by lines.
>>
>> Signed-off-by: Max Krummenacher
>> ---
>> README | 2
this is ok to install.
On 1/26/17 2:27 PM, Max Krummenacher wrote:
> ping
>
> Any comments on this one?
>
> Max
>
>
> 2017-01-17 0:09 GMT+01:00 Max Krummenacher :
>> Commit 8cc038d uses the system's nss rather than building a private
>> one. So one should remove the nss libs from PRIVATE_LIBS
On Thu, Jan 26, 2017 at 2:41 PM, Khem Raj wrote:
> On 1/25/17 1:43 PM, Andre McCurdy wrote:
>> When cross compiling, the word size of the compiler set via HOST_CC
>> must match the word size of the target. That's achieved by appending
>> "-m32" to BUILD_CC_ARCH if the target word size is known to
The coreutils has a hostname command; this package already dealt
with that existing as an alternate, but for some reason it did not
do the same with the manpage of the same name. The conflict varied
from intermittent to "why does this keep happening to me?!?".
Mark gets credit for the fix; he did
On 1/25/17 1:43 PM, Andre McCurdy wrote:
> When cross compiling, the word size of the compiler set via HOST_CC
> must match the word size of the target. That's achieved by appending
> "-m32" to BUILD_CC_ARCH if the target word size is known to be 32bits.
>
> Unfortunately the current list of ove
ping
Any comments on this one?
Max
2017-01-17 0:09 GMT+01:00 Max Krummenacher :
> Commit 8cc038d uses the system's nss rather than building a private
> one. So one should remove the nss libs from PRIVATE_LIBS also.
> Otherwise bitbake does not add nss to RDEPENDS automatically resulting
> in a
ping
Any comments on this one?
Max
2017-01-17 0:09 GMT+01:00 Max Krummenacher :
> Prevent missing Signed-off-by lines.
>
> Signed-off-by: Max Krummenacher
> ---
> README | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/README b/README
> index 647404b..effe2f9 100644
> -
On Thu, Jan 5, 2017 at 4:30 PM, Philip Balister wrote:
> On 01/03/2017 08:13 PM, Andreas Müller wrote:
>> On Tue, Jan 3, 2017 at 4:32 PM, Philip Balister wrote:
>>> Every year since 2007, OpenEmbedded has a stand at FOSDEM
>>> (http://www.fosdem.org)
>>>
>>> From the first year:
>>>
>>> https://w
On Thu, Jan 26, 2017 at 04:54:50PM +0200, Samuli Piippo wrote:
> The linux-oe-g++ mkspec is changed to use $$(...) operator to obtain
> the contents of an environment value when qmake is run instead of when
> Makefile is processed. All OE_QMAKE_xxx variables need to be exported
> for qmake to find
Signed-off-by: Oleksandr Kravchuk
---
.../nano/nano-2.2.5/ncursesw.includedir.patch| 12
meta-oe/recipes-support/nano/nano.inc| 10 --
meta-oe/recipes-support/nano/nano_2.2.5.bb | 8
meta-oe/recipes-support/n
On Thu, Jan 26, 2017 at 07:24:31PM +0100, Oleksandr Kravchuk wrote:
> Martin -
>
> May I ask you how it was built? I cannot reproduce this with poky 2.2 and
> oe's 'master' and 'master-next' branches. The package builds perfectly
> fine, without any errors or warnings.
The build setup is describe
Martin -
May I ask you how it was built? I cannot reproduce this with poky 2.2 and
oe's 'master' and 'master-next' branches. The package builds perfectly
fine, without any errors or warnings.
Thanks.
On 25 January 2017 at 15:54, Martin Jansa wrote:
> On Wed, Jan 11, 2017 at 12:36:28PM +0100, O
Did you also see the issue with the QMAKE_INCDIR_EGL, QMAKE_LIBS_EGL
and QMAKE_CFLAGS_EGL variables?
2017-01-26 13:54 GMT+01:00 Martin Jansa :
> On Thu, Jan 26, 2017 at 11:00:59AM +0100, Johannes Pointner wrote:
>> Hello,
>>
>> I tried to build qtbase after this update, but it failed to configure
Strange I was applying https://patchwork.openembedded.org/patch/136285/ to
master-next yesterday, not sure why they aren't there.
Can you send rebased version, because the v5 doesn't apply cleanly:
OE @ ~/meta-qt5 $ pwam 136285
2017-01-26 15:33:41 URL:
https://patchwork.openembedded.org/patch/136
On Thu, Jan 26, 2017 at 2:54 PM, Martin Jansa wrote:
> On Thu, Jan 26, 2017 at 11:00:59AM +0100, Johannes Pointner wrote:
>> Hello,
>>
>> I tried to build qtbase after this update, but it failed to configure
>> because of PACKAGECONFIG options which are no longer available or
>> moved to another p
On Thu, Jan 26, 2017 at 11:00:59AM +0100, Johannes Pointner wrote:
> Hello,
>
> I tried to build qtbase after this update, but it failed to configure
> because of PACKAGECONFIG options which are no longer available or
> moved to another part (qtmultimedia):
> PACKAGECONFIG[mitshm] = "-mitshm,-no-m
Signed-off-by: Gordan Markuš
---
recipes-qt/qt5/qtwebkit_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-qt/qt5/qtwebkit_git.bb b/recipes-qt/qt5/qtwebkit_git.bb
index d679994..3d2dbdf 100644
--- a/recipes-qt/qt5/qtwebkit_git.bb
+++ b/recipes-qt/qt5/qtwebkit_git.
19 matches
Mail list logo
