Built and boot test for all these boards on 4.1, 4.4 and 4.8 kernels.
Signed-off-by: Kevin Hao
---
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 6 +++---
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend | 12 ++--
meta-yocto-bsp/recipes-kernel/linux/linux-y
On Wed, 2016-10-26 at 06:20 +, Blaettler, Michael wrote:
> Hi Patrick
>
> I just checked the source code of curl.
>
> In acinclude.m4 on line 2560, you'll find:
> dnl CURL_CHECK_CA_BUNDLE
> dnl -
> dnl Check if a default ca-bundle should be used
Hi Patrick
I just checked the source code of curl.
In acinclude.m4 on line 2560, you'll find:
dnl CURL_CHECK_CA_BUNDLE
dnl -
dnl Check if a default ca-bundle should be used
dnl
dnl regarding the paths this will scan:
dnl /etc/ssl/certs/ca-certificat
Ensure recent contributions from Mark and Liam are reflected in the
authors list.
Signed-off-by: Paul Eggleton
---
templates/layerindex/about.html | 2 ++
1 file changed, 2 insertions(+)
diff --git a/templates/layerindex/about.html b/templates/layerindex/about.html
index 3e98825..a290344 100644
For some repo URLs we can automatically determine the values of all of
the other fields - e.g. for github or git.openembedded.org, and we've
been doing that for a while. However if someone submits a URL for some
other site we don't know what type of interface it uses, and usually
the submitter leav
Sometimes people put values that aren't URLs into the HOMEPAGE variable.
If that's the case, then we should not turn that value into a link which
will be invalid.
Signed-off-by: Paul Eggleton
---
layerindex/models.py | 6 ++
templates/layerindex/recipedetail.html | 8 ++
From: Stefan Agner
Signed-off-by: Stefan Agner
---
recipes-qt4/qt4/qt4-4.8.7.inc | 1 +
.../0001-QWS-fix-24-bit-RGB-BGR-handling.patch | 36 ++
2 files changed, 37 insertions(+)
create mode 100644
recipes-qt4/qt4/qt4-4.8.7/0001-QWS-fix-24-bit-RGB-
Hi Luca,
In order for us to help you, could you please provide more information
which better describes exactly what you did?
I have no experience with any of the paid SUSE products, but I do know
that poky can be built fine with openSUSE Leap 42.1 or 13.2 on x86-64
hardware.
There is a lot of do
On 10/25/16 12:49 PM, Brian Avery wrote:
> Hi,
>
> This doesn't default to slirp, it just allows it as an option.
Ok.. I misunderstood what it was trying to do then. That sounds fine.
> In particular, on CROPS containers on Windows 10 and Mac OSX the hypervisor
> is
> *not* a linux kernel.
Hi,
This doesn't default to slirp, it just allows it as an option.
In particular, on CROPS containers on Windows 10 and Mac OSX the
hypervisor is *not* a linux kernel. This means that the only way we can run
qemu in the container for testing/debugging is to run it in slirp mode
.since there is n
Hi
Here is the report for QA Cycle on 2.2 rc4
Full Report :
https://wiki.yoctoproject.org/wiki/WW43_-_2016-10-18_-_Full_Test_Cycle_2.2_rc4
Summary
There were found 10 new bugs, 3 of them are already triaged as M+ 1 as Medium
and the rest are not yet triaged, no one of these bugs was a blocke
> On Oct 25, 2016, at 6:02 AM, Nikola Popovic wrote:
>
> Greetings.
>
> Is there any possibility to make recipe which start and run application
> inside weston terminal when Yocto starts.
weston init does have mechanism for such usecases see weston.ini. I would
recommend to read through west
Hello,
I'm using SUSE Linux Enterprise Desktop 12. I follow Yocto
documentation. I start the buid with following command:
>>bitbake core-image-minimal
Output is the following with error:
Loading cache: 100% |#
#
Greetings.
Is there any possibility to make recipe which start and run application
inside weston terminal when Yocto starts.
Tnx !
--
Nikola Popovic
Software Engineer
Tel: +381 21 4801 1304
E-mail : nikola.popo...@rt-rk.com
RT-RK LLC
Narodnog fronta 23a
21000 Novi Sad
Serbia
www.rt-rk.com
On 10/25/16 6:49 AM, Alexander Kanavin wrote:
> On 10/25/2016 02:42 PM, Bipnesh, Abhinav (Abhinav) wrote:
>> Basically when we try to install these package on the image using RPM
>> package management i.e. rpm -ivh the dependency checks
>> fails as the rootfs doesn't contain RPM database from wher
On 10/25/2016 02:42 PM, Bipnesh, Abhinav (Abhinav) wrote:
Basically when we try to install these package on the image using RPM
package management i.e. rpm -ivh the dependency checks
fails as the rootfs doesn't contain RPM database from where the check
be made. So below is sample output
If the
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Alexander Kanavin
Sent: Tuesday, October 25, 2016 17:00
To: yocto@yoctoproject.org
Subject: Re: [yocto] Requires section of RPM Spec
On 10/25/2016 02:24 PM, Bipnesh, Abhinav (Abh
On 10/25/2016 02:24 PM, Bipnesh, Abhinav (Abhinav) wrote:
Is there a way we can avoid pre-populating the Requires section of the
generated RPM Spec from a recipe?
I have not set any RDEPENDS or other such section but still the section
get populated. Below is an example
Requires: libcrypto.so
Hi All,
Is there a way we can avoid pre-populating the Requires section of the
generated RPM Spec from a recipe?
I have not set any RDEPENDS or other such section but still the section get
populated. Below is an example
Requires: libcrypto.so.1.0.0(OPENSSL_1.0.2d)
Requires: libdl.so.2
Requires:
On Tue, 2016-10-25 at 05:49 +, Blaettler, Michael wrote:
> Hi Patrick
>
> What do you think of removing the --with-ca-bundle as a solution for
> curl-native? On my machine it works without problems.
What path does it use then? Something that configure determines based on
the current machine (
20 matches
Mail list logo
