> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Khem Raj
> Sent: den 21 september 2017 07:15
> To: Takashi Matsuzawa ; yocto@yoctoproject.org
> Subject: Re: [yocto] "(-)"??
>
> On 9/20/17 8:18 PM, Takashi Matsuzawa wrote:
On 9/20/17 8:18 PM, Takashi Matsuzawa wrote:
> Hello.
> I am seeing some of the recipes contains lines like below.
>
>> COMPATIBLE_MACHINE = "(-)"
>
> Sorry being novice, but what is the intended effect of this line?
> I can see submit comments that this is for blacklisting but I am not
> sure
Hello.
I am seeing some of the recipes contains lines like below.
> COMPATIBLE_MACHINE = "(-)"
Sorry being novice, but what is the intended effect of this line?
I can see submit comments that this is for blacklisting but I am not sure how
it works. It simply means a '-' letter?
--
__
On Tue, Sep 19, 2017 at 11:43 PM, Svein Seldal wrote:
>
> I have the spu-image.bb recipe below, and running on Pyro, the recipe
> behaves differently if the recipe is run on a fresh system with no sstate
> elements, compared to a system that has a sstate cache present.
>
> The failure is that the
This script name was changed in the following commit:
b46e05677b342df44829ffe8bcfbfc954e906030
This patch updates the script name to match.
[YOCTO #12110]
Signed-off-by: Stephano Cetola
---
lib/python2.7/site-packages/autobuilder/buildsteps/CheckYoctoCompat.py | 3 ++-
1 file changed, 2 inser
Hi Paul,
thanks for explaining and helping sorting this out.
On Wed, Sep 20, 2017 at 11:54 AM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:
> Hi Andrea,
>
> On Wednesday, 20 September 2017 8:44:22 PM NZST Andrea Galbusera wrote:
> > Seeing the errors below while installing an eSDK. This
On Wed, Sep 13, 2017 at 10:56 AM, Dan Walkes
wrote:
> On Mon, Sep 11, 2017 at 5:01 AM, Burton, Ross wrote:
>> On 10 September 2017 at 21:35, Dan Walkes
>> wrote:
>>>
>>> It looks like because the update-rc.d step fails this setup gets moved
>>> into a gpsd post install script, which won’t work b
Hi Richard,
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
> On Behalf Of Schmitt, Richard
> Sent: Friday, July 14, 2017 8:23 AM
> To: yocto@yoctoproject.org
> Subject: [yocto] Kernel Build Failures with Shared SSTATE
>
> Hi,
>
>
>
>
Hello,
The meta-tpm layer inside the meta-security layer looks like exactly
what I want in order to get TPM 2.0 support on my devices. I'm currently
using qemu and trying to create a swtpm device on my host and pass it
through to the device. Despite my best attempts, I have not yet been
able to ge
Hi Andrea,
On Wednesday, 20 September 2017 8:44:22 PM NZST Andrea Galbusera wrote:
> Seeing the errors below while installing an eSDK. This is a routinely
> generated VM that installs the eSDK from installation script. The errors
> appeared with the latest iteration of the eSDK script, which is ge
From: Wenzong Fan
Fix the warnings if ${libdir} = '/usr/lib64':
WARNING: selinux-python-2.7-r0 do_package: QA Issue: selinux-python: \
Files/directories were installed but not shipped in any package:
/usr/lib/python2.7/site-packages/sepolicy-1.1.egg-info
/usr/lib/python2.7/site-pack
Seeing the errors below while installing an eSDK. This is a routinely
generated VM that installs the eSDK from installation script. The errors
appeared with the latest iteration of the eSDK script, which is generated
with almost up-to-date revisions from master. Of course I have extra layers
in the
Hi all,
I am using Yocto Poky 2.3 (yocto-2.3-65-gcc48789276e0) and its
extensible SDK. Host is Ubuntu 16.04.3 LTS. I have multiple issues
with sdk-update:
1. $ devtool sdk-update
Fetching origin
fatal: unable to access
'https://foobar.com/~builder/releases/yocto-2.3/toolchain/updates/layers/.git
13 matches
Mail list logo
