On Mon, Nov 18, 2019 at 4:30 PM Chandana Kalluri wrote:
>
>
> > -Original Message-
> > From: Khem Raj
> > Sent: Monday, November 18, 2019 4:21 PM
> > To: Chandana Kalluri
> > Cc: yocto@yoctoproject.org
> > Subject: Re: [yocto] patches to upgrade meta-jupyter layer packages
> >
> > On
> -Original Message-
> From: Khem Raj
> Sent: Monday, November 18, 2019 4:21 PM
> To: Chandana Kalluri
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] patches to upgrade meta-jupyter layer packages
>
> On Mon, Nov 18, 2019 at 4:17 PM Chandana Kalluri
> wrote:
> >
> > Hello all,
>
On Mon, Nov 18, 2019 at 4:17 PM Chandana Kalluri wrote:
>
> Hello all,
>
> I have upgraded python packages from meta-jupyter layer to work with the zeus
> branch.
> I am planning to send out the patches to this yocto project mailing list
> yocto@yoctoproject.org Please let me know if this is
On Mon, Nov 18, 2019 at 4:10 PM Greg Wilson-Lindberg
wrote:
>
> Hi Khem,
>
> I found the BBCLASSEXTEND in the qemu.inc file, I also found a line in the
> .bb file:
>
> SRC_URI_append_class-native = " \
>
>
> so I changed my SRC_URI to that and I stopped getting the 'can't find file to
> patch'
Hi Khem,
And just after I hit send I realized that I changed 'SRC_URI' to
'SRC_URII_append_class-native' with the 'II'. I deleted the 'II' and now the
file is changed like it should be.
Thanks fo all of your help,
Greg Wilson-Lindberg
From: Greg Wilson-Lindberg
Sent: Monday, November
Hello all,
I have upgraded python packages from meta-jupyter layer to work with the zeus
branch.
I am planning to send out the patches to this yocto project mailing list
yocto@yoctoproject.org Please let me know if this is alright or if I need to
send them to a different mailing list.
Thanks,
Hi Khem,
I found the BBCLASSEXTEND in the qemu.inc file, I also found a line in the .bb
file:
SRC_URI_append_class-native = " \
so I changed my SRC_URI to that and I stopped getting the 'can't find file to
patch' error, but the file (syscall.c) is not modified.
Here is my
On Mon, Nov 18, 2019 at 3:27 PM Greg Wilson-Lindberg
wrote:
>
> I'm building thud for the raspberry pi3 for boot2qt on Ubuntu 18.04.
> I've got a patch that I need to apply to to fix an include file problem and I
> can't find the qemu-native recipe. I can find a number of recipes that depend
>
I'm building thud for the raspberry pi3 for boot2qt on Ubuntu 18.04.
I've got a patch that I need to apply to to fix an include file problem and I
can't find the qemu-native recipe. I can find a number of recipes that depend
in one way or another on 'qemu-native', but I can't find a recipe,
Hi,
I'm wondering whether anyone here uses Yocto to build images
for legacy x86 systems (without UEFI) with GRUB as a bootloader.
I know that the GRUB with UEFI is well supported in Yocto.
I'm looking for a way to create a bootable disk (ideally using WIC)
for legacy BIOS with GRUB
So it looks like KVM is built in (at least it's supposed to be). I'm
pretty sure that is the case after looking at my kernel configuration file:
https://gist.github.com/WayneZhenLi/4172cd4a819b71a11b85fc5aaa57ebd1
I then changed the CONFIG_KVM=y line to CONFIG_KVM=m and also added the
On 18.11.2019 19:22, Wayne Li wrote:
Dear Yocto Developers,
I'm trying to incorporate KVM into a Yocto kernel me and my coworker
build for a T4240 RDB (which has a PowerPC CPU). The problem is, no
matter what I do the KVM kernel module (I'm expecting a kvm.ko or any
.ko file along those
Dear Yocto Developers,
I'm trying to incorporate KVM into a Yocto kernel me and my coworker build
for a T4240 RDB (which has a PowerPC CPU). The problem is, no matter what
I do the KVM kernel module (I'm expecting a kvm.ko or any .ko file along
those lines) is not present in the image.
First I
looks good to me.
On Sun, Nov 17, 2019 at 11:00 PM Jain, Sangeeta wrote:
>
> Hello all,
>
> This is the full report for 2.7.2 RC1:
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
>
> === Summary
> No high milestone defects.
> No
All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:
You are changing the value of something in there dynamically. Most likely
you've done something like embed the current date and time.
If you do something like that, you need to evaluate it -once- during parse time
and not again. This will fix the hash value at parse time and not change it
Thanks for you help, finally I've got it working.
Just for clarification, I'm using Yocto rocko. I've checked and support for
parametrized systemd services is available in systemd.bbclass.
Also I've tried to make a dummy profile file and populate it on rootfs
instead of symlink. It also didn't
On 17/11/2019 19:44, Mateusz Majchrzycki wrote:
What am I doing wrong? I suppose the symlink is not a problem as
normally systemctl enables service with non-existent file as a parameter
(it fails on start, but not enabling).
The problem is that the systemd class doesn't know what to do here.
Dear all,
When I modify the os-release file in my yocto project, it appear some error,
and how can I solve it ? Who can give me some help or advice? Thank you！
I carried out the recommended order and it didn't work.
ERROR: os-release-1.0-r0 do_compile: Taskhash mismatch
Dear all,
When I modify the os-release file in my yocto project, it appear some error,
and how can I solve it ? Who can give me some help or advice? Thank you！
I carried out the recommended order and it didn't work.
ERROR: os-release-1.0-r0 do_compile: Taskhash mismatch
20 matches
Mail list logo
