date:20171211

Re: [yocto] rocko build fails

2017-12-11 Thread Zoran Stojsavljevic

> Any hints ?

For the starters, No idea what is your host. I will assume it is Ubuntu.

So for rocko, you need to upgrade you host. I have Fedora 26, so my latest
autotools are:
[root@localhost ~]# dnf install autoconf automake
Last metadata expiration check: 0:05:16 ago on Mon 11 Dec 2017 09:14:44 AM
CET.
Package autoconf-2.69-24.fc26.noarch is already installed, skipping.
Package automake-1.15-9.fc26.noarch is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!
[root@localhost ~]#
___

If you have Fedora, I warmly recommend: dnf upgrade --refresh
If you have Ubuntu, at least: apt-get update

Maybe this will solve your problem. Lets hope.

Zoran

On Mon, Dec 11, 2017 at 8:58 AM, Mircea Gliga 
wrote:

> Hello,
>
> I have a working krogoth build - I build images etc, everything is fine.
> Then I wanted to try a rocko build, I installed the needed host packages:
> http://www.yoctoproject.org/docs/2.4/yocto-project-qs/
> yocto-project-qs.html#packages
> Then sourced env and *bitbake core-image-minimal*.
> So no extra layers involved, just poky.
> I get errors like this:
>
> ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch:
> Build of do_fetch failed
> ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch:
> Traceback (most recent call last):
>   File 
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
> line 644, in exec_task
> return _exec_task(fn, task, d, quieterr)
>   File 
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
> line 618, in _exec_task
> event.fire(TaskSucceeded(task, logfn, localdata), localdata)
>   File 
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
> line 222, in fire
> fire_class_handlers(event, d)
>   File 
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
> line 134, in fire_class_handlers
> execute_handler(name, handler, event, d)
>   File 
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
> line 106, in execute_handler
> ret = handler(event)
>   File "/media/mircea/ExtLinux/Adventure/repository/rocko/
> poky/meta/classes/buildstats.bbclass", line 166, in run_buildstats
> write_task_data("passed", os.path.join(taskdir, e.task), e, d)
>   File "/media/mircea/ExtLinux/Adventure/repository/rocko/
> poky/meta/classes/buildstats.bbclass", line 90, in write_task_data
> cpu, iostats, resources, childres = get_process_cputime(os.getpid())
>   File "/media/mircea/ExtLinux/Adventure/repository/rocko/
> poky/meta/classes/buildstats.bbclass", line 29, in get_process_cputime
> with open("/proc/%d/io" % pid, "r") as f:
> PermissionError: [Errno 13] Permission denied: '/proc/1530/io'
>
> ERROR: Task (virtual:native:/media/mircea/ExtLinux/Adventure/repository/
> rocko/poky/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_fetch)
> failed with exit code '1'
> ERROR: autoconf-native-2.69-r11 do_fetch: Execution of event handler
> 'run_buildstats' failed
> Traceback (most recent call last):
>   File "/media/mircea/ExtLinux/Adventure/repository/rocko/
> poky/meta/classes/buildstats.bbclass", line 166, in
> run_buildstats(e=):
>  elif isinstance(e, bb.build.TaskSucceeded):
> >write_task_data("passed", os.path.join(taskdir, e.task), e, d)
>  if e.task == "do_rootfs":
>   File "/media/mircea/ExtLinux/Adventure/repository/rocko/
> poky/meta/classes/buildstats.bbclass", line 90, in
> write_task_data(status='passed', logfile='/media/mircea/
> ExtLinux/Adventure/repository/rocko/build/tmp/buildstats/
> 20171211074610/autoconf-native-2.69-r11/do_fetch',
> e=,
> d=):
>  f.write(d.expand("Elapsed time: %0.2f seconds\n" %
> elapsedtime))
> >cpu, iostats, resources, childres =
> get_process_cputime(os.getpid())
>  if cpu:
>   File "/media/mircea/ExtLinux/Adventure/repository/rocko/
> poky/meta/classes/buildstats.bbclass", line 29, in
> get_process_cputime(pid=1543):
>  if os.path.isfile("/proc/%d/io" % pid):
> >with open("/proc/%d/io" % pid, "r") as f:
>  while True:
> PermissionError: [Errno 13] Permission denied: '/proc/1543/io'
>
> ERROR: autoconf-native-2.69-r11 do_fetch: Build of do_fetch failed
> ERROR: autoconf-native-2.69-r11 do_fetch: Traceback (most recent call
> last):
>   File 
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
> line 644, in exec_task
> return _exec_task(fn, task, d, quieterr)
>   File 
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
> line 618, in _exec_task
> event.fire(TaskSucceeded(task, logfn, localdata), localdata)
>   File 
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
> line 222, in fire
> fire_class_handlers(event, d)
>   File 
> "/media/mircea/ExtLinux/Adventure/repository/rocko/

Re: [yocto] rocko build fails

2017-12-11 Thread Mircea Gliga

Hi again,

>For the starters, No idea what is your host. I will assume it is Ubuntu.

Sorry about that.
I'm on Debian 8:
# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"

I updated the system this morning, and again now:

# aptitude update; aptitude full-upgrade
[...]
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

I checked again if I have all the packages mentioned on the Quick Start 
guide installed: 
http://www.yoctoproject.org/docs/2.4/yocto-project-qs/yocto-project-qs.html#packages

They are all there.
Should I also install autoconf/automake ? They are not mentioned in the 
guide ...

Thanks

On 11/12/17 10:25, Zoran Stojsavljevic wrote:

> Any hints ?

For the starters, No idea what is your host. I will assume it is Ubuntu.

So for rocko, you need to upgrade you host. I have Fedora 26, so my 
latest autotools are:

[root@localhost ~]# dnf install autoconf automake
Last metadata expiration check: 0:05:16 ago on Mon 11 Dec 2017 
09:14:44 AM CET.

Package autoconf-2.69-24.fc26.noarch is already installed, skipping.
Package automake-1.15-9.fc26.noarch is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!
[root@localhost ~]#
___

If you have Fedora, I warmly recommend: dnf upgrade --refresh
If you have Ubuntu, at least: apt-get update

Maybe this will solve your problem. Lets hope.

Zoran

On Mon, Dec 11, 2017 at 8:58 AM, Mircea Gliga 
mailto:mircea.gl...@vitheia.com>> wrote:

Hello,

I have a working krogoth build - I build images etc, everything is
fine.
Then I wanted to try a rocko build, I installed the needed host
packages:

http://www.yoctoproject.org/docs/2.4/yocto-project-qs/yocto-project-qs.html#packages

Then sourced env and /bitbake core-image-minimal/.
So no extra layers involved, just poky.
I get errors like this:

ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0
do_fetch: Build of do_fetch failed
ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0
do_fetch: Traceback (most recent call last):
  File

"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
line 644, in exec_task
    return _exec_task(fn, task, d, quieterr)
  File

"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
line 618, in _exec_task
    event.fire(TaskSucceeded(task, logfn, localdata), localdata)
  File

"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
line 222, in fire
    fire_class_handlers(event, d)
  File

"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
line 134, in fire_class_handlers
    execute_handler(name, handler, event, d)
  File

"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
line 106, in execute_handler
    ret = handler(event)
  File

"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 166, in run_buildstats
    write_task_data("passed", os.path.join(taskdir, e.task), e, d)
  File

"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 90, in write_task_data
    cpu, iostats, resources, childres =
get_process_cputime(os.getpid())
  File

"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 29, in get_process_cputime
    with open("/proc/%d/io" % pid, "r") as f:
PermissionError: [Errno 13] Permission denied: '/proc/1530/io'

ERROR: Task

(virtual:native:/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_fetch)
failed with exit code '1'
ERROR: autoconf-native-2.69-r11 do_fetch: Execution of event
handler 'run_buildstats' failed
Traceback (most recent call last):
  File

"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 166, in run_buildstats(e=):
 elif isinstance(e, bb.build.TaskSucceeded):
    >    write_task_data("passed", os.path.join(taskdir,
e.task), e, d)
 if e.task == "do_rootfs":
  File

"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 90, in write_task_data(status='passed',

logfile='/media/mircea/ExtLinux/Adventure/repository/rocko/build/tmp/buildstats/20171211074610/autoconf-native-2.69-r11/do_fetch',
e=,
d=):
 f.write(d.expand("Elapsed time: %0.2f seconds\n"
% elapsedtime))
    >    cpu, iostats, resources, childres =
get_process_cputime(os.getpid())

[yocto] OpenEmbedded stand at FOSDEM 2018

2017-12-11 Thread Paul Barker

Hi all,

We've got confirmation for an OpenEmbedded stand at FOSDEM 2018! We're
in the AW building as usual, you can see the full list of stands and
location details here: https://fosdem.org/2018/stands/

What we need:

* People to help out on the stand and chat about the project. If
you're going to FOSDEM and don't know many people in the OE project
this is a great way to get to know some. Even if you can only help out
for an hour or two this would be much appreciated!

* Device/product demos which show off the features of OE. We only have
one table this year so please let us know if you're bringing hardware,
that way we can make sure everything fits. Preference will go to
hobbyist projects as this is FOSDEM but we're happy with commercial
projects as long as they're not an explicit sales pitch.

* Build system demo. I really want us to show off toaster again as
that got a lot of interest last time we demo'd it at FOSDEM.
Unfortunately I'm on holiday before FOSDEM and I'm not travelling
directly from home so I'll be unable to bring something to run this
demo on. So if someone could bring a laptop or mini-PC/monitor/etc to
run a build system demo on that would be excellent. If not I'll see if
I can get something shipped to Brussels.

I've created a wiki page here:
https://www.openembedded.org/wiki/FOSDEM_2018. Please add to this if
you're planning to bring anything or just attend.

Look forward to seeing many of you in Feb :)

-- 
Paul Barker
Togán Labs Ltd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] rocko build fails

2017-12-11 Thread Zoran Stojsavljevic

> Should I also install autoconf/automake ? They are not mentioned in the
guide ...

You mentioned it before (previous @). Sorry, I forgot. If they are not
installed, you should.

Zoran

On Mon, Dec 11, 2017 at 9:35 AM, Mircea Gliga 
wrote:

> Hi again,
>
> >For the starters, No idea what is your host. I will assume it is Ubuntu.
>
> Sorry about that.
> I'm on Debian 8:
> # cat /etc/os-release
> PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
>
> I updated the system this morning, and again now:
>
> # aptitude update; aptitude full-upgrade
> [...]
> No packages will be installed, upgraded, or removed.
> 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B of archives. After unpacking 0 B will be used.
>
> I checked again if I have all the packages mentioned on the Quick Start
> guide installed: http://www.yoctoproject.org/docs/2.4/yocto-project-qs/
> yocto-project-qs.html#packages
>
> They are all there.
> Should I also install autoconf/automake ? They are not mentioned in the
> guide ...
>
> Thanks
>
>
>
> On 11/12/17 10:25, Zoran Stojsavljevic wrote:
>
> > Any hints ?
>
> For the starters, No idea what is your host. I will assume it is Ubuntu.
>
> So for rocko, you need to upgrade you host. I have Fedora 26, so my latest
> autotools are:
> [root@localhost ~]# dnf install autoconf automake
> Last metadata expiration check: 0:05:16 ago on Mon 11 Dec 2017 09:14:44 AM
> CET.
> Package autoconf-2.69-24.fc26.noarch is already installed, skipping.
> Package automake-1.15-9.fc26.noarch is already installed, skipping.
> Dependencies resolved.
> Nothing to do.
> Complete!
> [root@localhost ~]#
> ___
>
> If you have Fedora, I warmly recommend: dnf upgrade --refresh
> If you have Ubuntu, at least: apt-get update
>
> Maybe this will solve your problem. Lets hope.
>
> Zoran
>
> On Mon, Dec 11, 2017 at 8:58 AM, Mircea Gliga 
> wrote:
>
>> Hello,
>>
>> I have a working krogoth build - I build images etc, everything is fine.
>> Then I wanted to try a rocko build, I installed the needed host packages:
>> http://www.yoctoproject.org/docs/2.4/yocto-project-qs/yocto-
>> project-qs.html#packages
>> Then sourced env and *bitbake core-image-minimal*.
>> So no extra layers involved, just poky.
>> I get errors like this:
>>
>> ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch:
>> Build of do_fetch failed
>> ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch:
>> Traceback (most recent call last):
>>   File 
>> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
>> line 644, in exec_task
>> return _exec_task(fn, task, d, quieterr)
>>   File 
>> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
>> line 618, in _exec_task
>> event.fire(TaskSucceeded(task, logfn, localdata), localdata)
>>   File 
>> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
>> line 222, in fire
>> fire_class_handlers(event, d)
>>   File 
>> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
>> line 134, in fire_class_handlers
>> execute_handler(name, handler, event, d)
>>   File 
>> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
>> line 106, in execute_handler
>> ret = handler(event)
>>   File "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/
>> meta/classes/buildstats.bbclass", line 166, in run_buildstats
>> write_task_data("passed", os.path.join(taskdir, e.task), e, d)
>>   File "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/
>> meta/classes/buildstats.bbclass", line 90, in write_task_data
>> cpu, iostats, resources, childres = get_process_cputime(os.getpid())
>>   File "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/
>> meta/classes/buildstats.bbclass", line 29, in get_process_cputime
>> with open("/proc/%d/io" % pid, "r") as f:
>> PermissionError: [Errno 13] Permission denied: '/proc/1530/io'
>>
>> ERROR: Task (virtual:native:/media/mircea/ExtLinux/Adventure/repository/
>> rocko/poky/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_fetch)
>> failed with exit code '1'
>> ERROR: autoconf-native-2.69-r11 do_fetch: Execution of event handler
>> 'run_buildstats' failed
>> Traceback (most recent call last):
>>   File "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/
>> meta/classes/buildstats.bbclass", line 166, in
>> run_buildstats(e=):
>>  elif isinstance(e, bb.build.TaskSucceeded):
>> >write_task_data("passed", os.path.join(taskdir, e.task), e,
>> d)
>>  if e.task == "do_rootfs":
>>   File "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/
>> meta/classes/buildstats.bbclass", line 90, in
>> write_task_data(status='passed', logfile='/media/mircea/ExtLinu
>> x/Adventure/repository/rocko/build/tmp/buildstats/201712110
>> 74610/autoconf-native-2.69-r11/do_fetch', e=> object at 0x7f07f3f31898>, d=> 0x7f07f23de2b0>):
>>

Re: [yocto] rocko build fails

2017-12-11 Thread Mircea Gliga

I installed autoconf and automake, result is the same. bitbake still 
tries to fetch the respective packages, it doesn't use the ones provided 
by the system, and that makes sense... It creates its own toolchain.


As I understand the *Permission denied* error pops up during do_fetch, 
when it tries to gather some statistics for that process. For some 
reason it cannot open the */proc/**/PID/**/io* files.


I've created a python script to test if I'm able to read such a file 
from python. I was successful...


This error comes up for a bunch of *-native recipes. Here is the 
complete log, the one from the previous email was truncated:


$ bitbake core-image-minimal
Loading cache: 100% 
|##| 
Time: 0:00:00

Loaded 1275 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.36.0"
BUILD_SYS    = "x86_64-linux"
NATIVELSBSTRING  = "universal-4.9"
TARGET_SYS   = "i586-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"
DISTRO_VERSION   = "2.4.1"
TUNE_FEATURES    = "m32 i586"
TARGET_FPU   = ""
meta
meta-poky
meta-yocto-bsp   = "rocko:74863e0d67c1a1a63d7d7c6d7753da225e02143d"

Initialising tasks: 100% 
|#| 
Time: 0:00:04

NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: m4-native-1.4.18-r0 do_fetch: Execution of event handler 
'run_buildstats' failed

Traceback (most recent call last):
  File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 166, in run_buildstats(e=0x7fa8a28028d0>):

 elif isinstance(e, bb.build.TaskSucceeded):
    >    write_task_data("passed", os.path.join(taskdir, e.task), e, d)
 if e.task == "do_rootfs":
  File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 90, in write_task_data(status='passed', 
logfile='/home/repository/rocko/build/tmp/buildstats/20171211092724/m4-native-1.4.18-r0/do_fetch', 
e=, 
d=):
 f.write(d.expand("Elapsed time: %0.2f seconds\n" % 
elapsedtime))
    >    cpu, iostats, resources, childres = 
get_process_cputime(os.getpid())

 if cpu:
  File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 29, in get_process_cputime(pid=5947):

 if os.path.isfile("/proc/%d/io" % pid):
    >    with open("/proc/%d/io" % pid, "r") as f:
 while True:
PermissionError: [Errno 13] Permission denied: '/proc/5947/io'

ERROR: m4-native-1.4.18-r0 do_fetch: Build of do_fetch failed
ERROR: m4-native-1.4.18-r0 do_fetch: Traceback (most recent call last):
  File "/home/repository/rocko/poky/bitbake/lib/bb/build.py", line 644, 
in exec_task

    return _exec_task(fn, task, d, quieterr)
  File "/home/repository/rocko/poky/bitbake/lib/bb/build.py", line 618, 
in _exec_task

    event.fire(TaskSucceeded(task, logfn, localdata), localdata)
  File "/home/repository/rocko/poky/bitbake/lib/bb/event.py", line 222, 
in fire

    fire_class_handlers(event, d)
  File "/home/repository/rocko/poky/bitbake/lib/bb/event.py", line 134, 
in fire_class_handlers

    execute_handler(name, handler, event, d)
  File "/home/repository/rocko/poky/bitbake/lib/bb/event.py", line 106, 
in execute_handler

    ret = handler(event)
  File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 166, in run_buildstats

    write_task_data("passed", os.path.join(taskdir, e.task), e, d)
  File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 90, in write_task_data

    cpu, iostats, resources, childres = get_process_cputime(os.getpid())
  File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 29, in get_process_cputime

    with open("/proc/%d/io" % pid, "r") as f:
PermissionError: [Errno 13] Permission denied: '/proc/5947/io'

ERROR: Task 
(/home/repository/rocko/poky/meta/recipes-devtools/m4/m4-native_1.4.18.bb:do_fetch) 
failed with exit code '1'
ERROR: texinfo-dummy-native-1.0-r0 do_fetch: Execution of event handler 
'run_buildstats' failed

Traceback (most recent call last):
  File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 166, in run_buildstats(e=0x7fa8a2fbc9e8>):

 elif isinstance(e, bb.build.TaskSucceeded):
    >    write_task_data("passed", os.path.join(taskdir, e.task), e, d)
 if e.task == "do_rootfs":
  File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 90, in write_task_data(status='passed', 
logfile='/home/repository/rocko/build/tmp/buildstats/20171211092724/texinfo-dummy-native-1.0-r0/do_fetch', 
e=, 
d=):
 f.write(d.expand("Elapsed time: %0.2f seconds\n" % 
elapsedtime))
    >

Re: [yocto] VPS for building and serving.

2017-12-11 Thread Paul Barker

On Sun, Dec 10, 2017 at 1:15 PM, Daniel.  wrote:
> Hi,
>
> Is there anybody using VPS for building and serving packages? What plans you
> do recommend?

I don't recommend using a VPS, they tend to get expensive for the spec
you need for a Yocto build. You want plenty of RAM, CPU and disk
space.

I use Hetzner for everything and I'm pretty happy with them. They have
a server auction system that's good if you don't need a
top-of-the-line machine: https://www.hetzner.com/sb

Let me know if you need any more specific advice.

Cheers,

-- 
Paul Barker
Togán Labs Ltd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail

2017-12-11 Thread Paul Barker

On Sun, Dec 10, 2017 at 5:14 PM, Daniel.  wrote:
> Hi everybody,
>
> I'm building a vanilla image for MACHINE=raspberrypi3-64. I'm doing the
> build for the first time and faced an error at
> linux-raspberrypi:do_kernel_configme. I found that .kernel-meta/configs
> folder was missing, so I fired a devshell and created it. After that
> everything works as expected and linux-raspberrypi build fines.
>
> The solution I got is palliative, what would be the real solution and what
> is this .kernel-meta folder? I had never seem this folder before.

I have seen this issue occasionally when the do_kernel_configme task
is re-executed. A "bitbake virtual/kernel -c clean" has always
resolved this for me, allowing the next build to succeed. It doesn't
occur on my autobuild systems though so I figure it's an edge case I'm
hitting when building locally as I'm hacking around on recipes.

I've never seen this on the first build of the kernel though.

Which version of Yocto are you using? Could you send us the build
configuration summary and the full error messages printed by bitbake?

Thanks,

-- 
Paul Barker
Togán Labs Ltd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail

2017-12-11 Thread Daniel.

Yeah but I got to face the error again, maybe tonight when I get home :)

On Dec 11, 2017 9:17 AM, "Paul Barker"  wrote:

> On Sun, Dec 10, 2017 at 5:14 PM, Daniel.  wrote:
> > Hi everybody,
> >
> > I'm building a vanilla image for MACHINE=raspberrypi3-64. I'm doing the
> > build for the first time and faced an error at
> > linux-raspberrypi:do_kernel_configme. I found that .kernel-meta/configs
> > folder was missing, so I fired a devshell and created it. After that
> > everything works as expected and linux-raspberrypi build fines.
> >
> > The solution I got is palliative, what would be the real solution and
> what
> > is this .kernel-meta folder? I had never seem this folder before.
>
> I have seen this issue occasionally when the do_kernel_configme task
> is re-executed. A "bitbake virtual/kernel -c clean" has always
> resolved this for me, allowing the next build to succeed. It doesn't
> occur on my autobuild systems though so I figure it's an edge case I'm
> hitting when building locally as I'm hacking around on recipes.
>
> I've never seen this on the first build of the kernel though.
>
> Which version of Yocto are you using? Could you send us the build
> configuration summary and the full error messages printed by bitbake?
>
> Thanks,
>
> --
> Paul Barker
> Togán Labs Ltd
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail

2017-12-11 Thread Daniel.

I can anticipate some info for you. I'm on version 2.4 Rocko. Building
rpi-hwup-image for MACHINE=rasbiberrypi3-64. Also is worth noting that I'm
running Fedora 27 which wasn't tested...

I'll try to get the full log tonight and let you know

Regards

On Dec 11, 2017 9:26 AM, "Daniel."  wrote:

> Yeah but I got to face the error again, maybe tonight when I get home :)
>
> On Dec 11, 2017 9:17 AM, "Paul Barker"  wrote:
>
>> On Sun, Dec 10, 2017 at 5:14 PM, Daniel.  wrote:
>> > Hi everybody,
>> >
>> > I'm building a vanilla image for MACHINE=raspberrypi3-64. I'm doing the
>> > build for the first time and faced an error at
>> > linux-raspberrypi:do_kernel_configme. I found that .kernel-meta/configs
>> > folder was missing, so I fired a devshell and created it. After that
>> > everything works as expected and linux-raspberrypi build fines.
>> >
>> > The solution I got is palliative, what would be the real solution and
>> what
>> > is this .kernel-meta folder? I had never seem this folder before.
>>
>> I have seen this issue occasionally when the do_kernel_configme task
>> is re-executed. A "bitbake virtual/kernel -c clean" has always
>> resolved this for me, allowing the next build to succeed. It doesn't
>> occur on my autobuild systems though so I figure it's an edge case I'm
>> hitting when building locally as I'm hacking around on recipes.
>>
>> I've never seen this on the first build of the kernel though.
>>
>> Which version of Yocto are you using? Could you send us the build
>> configuration summary and the full error messages printed by bitbake?
>>
>> Thanks,
>>
>> --
>> Paul Barker
>> Togán Labs Ltd
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Layer documentation for meta-raspberrypi

2017-12-11 Thread Paul Barker

Hi all,

As a quick announcement, the layer documentation for meta-raspberrypi
is now available on Read the Docs:
http://meta-raspberrypi.readthedocs.io/en/latest/

The latest documentation is shown by default and covers the master
branch. Using the version box in the bottom right corner of the page
you can also switch to the rocko or pyro versions. This is
automatically updated whenever changes are pushed to the documentation
in meta-raspberrypi.

Raspberry Pi seems to be a very common platform for newcomers to
OE/Yocto and so I think it's really important that this layer is well
documented and is easy to use. Please submit pull requests or open
bugs if you think any of the documentation can be improved.

We use Sphinx (http://www.sphinx-doc.org/) plus Read the Docs
(https://readthedocs.org/) integration for this which I think is a
pretty good setup for layer documentation in general. If anyone wants
more details so they can do something similar for another layer then
please let me know!

Cheers,

-- 
Paul Barker
Togán Labs Ltd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] rocko build fails

2017-12-11 Thread Zoran Stojsavljevic

Hello Mircea,

I again went through your messages, and read carefully (since I am also
learner, trying to help, and at the same time, to learn).

And this:









* File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass", line
90, in write_task_data(status='passed',
logfile='/home/repository/rocko/build/tmp/buildstats/20171211092724/gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0/do_fetch',
e=,
d=):
f.write(d.expand("Elapsed time: %0.2f seconds\n" % elapsedtime))
>cpu, iostats, resources, childres =
get_process_cputime(os.getpid()) if cpu:  File
"/home/repository/rocko/poky/meta/classes/buildstats.bbclass", line 29, in
get_process_cputime(pid=5946): if os.path.isfile("/proc/%d/io" %
pid):>with open("/proc/%d/io" % pid, "r") as f:
while True:PermissionError: [Errno 13] Permission denied: '/proc/5946/io'*

I also replicated, writing/replicating this output in Python (3.6.3) on my
Fedora 26. And, for me, it also works (output from my Python script):

[user@localhost python3.6]$ pwd
/home/user/projects/python3.6
[user@localhost python3.6]$ ./pytime.py
cputime is 16767822
proctime is: 1
PID is: 13074
<_io.TextIOWrapper name='/proc/13074/io' mode='r' encoding='UTF-8'>
Again, PID is 13074
UID is 1000
GID is 1000
[user@localhost python3.6]$

UID = 1000 is user - user, GID = 1000 is user (user:user). I am NOT
executing this as root, for sure!?

We need to wait for somebody more (YOCTO project wise) versatile.

Thank you,
Zoran

On Mon, Dec 11, 2017 at 10:35 AM, Mircea Gliga 
wrote:

> I installed autoconf and automake, result is the same. bitbake still tries
> to fetch the respective packages, it doesn't use the ones provided by the
> system, and that makes sense... It creates its own toolchain.
>
> As I understand the *Permission denied* error pops up during do_fetch,
> when it tries to gather some statistics for that process. For some reason
> it cannot open the */proc/**PID**/io* files.
>
> I've created a python script to test if I'm able to read such a file from
> python. I was successful...
>
> This error comes up for a bunch of *-native recipes. Here is the complete
> log, the one from the previous email was truncated:
>
> $ bitbake core-image-minimal
> Loading cache: 100% |#
> 
> #| Time:
> 0:00:00
> Loaded 1275 entries from dependency cache.
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION   = "1.36.0"
> BUILD_SYS= "x86_64-linux"
> NATIVELSBSTRING  = "universal-4.9"
> TARGET_SYS   = "i586-poky-linux"
> MACHINE  = "qemux86"
> DISTRO   = "poky"
> DISTRO_VERSION   = "2.4.1"
> TUNE_FEATURES= "m32 i586"
> TARGET_FPU   = ""
> meta
> meta-poky
> meta-yocto-bsp   = "rocko:74863e0d67c1a1a63d7d7c6d7753da225e02143d"
>
> Initialising tasks: 100% |#
> 
> | Time:
> 0:00:04
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> ERROR: m4-native-1.4.18-r0 do_fetch: Execution of event handler
> 'run_buildstats' failed
> Traceback (most recent call last):
>   File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass",
> line 166, in run_buildstats(e= 0x7fa8a28028d0>):
>  elif isinstance(e, bb.build.TaskSucceeded):
> >write_task_data("passed", os.path.join(taskdir, e.task), e, d)
>  if e.task == "do_rootfs":
>   File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass",
> line 90, in write_task_data(status='passed', logfile='/home/repository/
> rocko/build/tmp/buildstats/20171211092724/m4-native-1.4.18-r0/do_fetch',
> e=,
> d=):
>  f.write(d.expand("Elapsed time: %0.2f seconds\n" %
> elapsedtime))
> >cpu, iostats, resources, childres =
> get_process_cputime(os.getpid())
>  if cpu:
>   File "/home/repository/rocko/poky/meta/classes/buildstats.bbclass",
> line 29, in get_process_cputime(pid=5947):
>  if os.path.isfile("/proc/%d/io" % pid):
> >with open("/proc/%d/io" % pid, "r") as f:
>  while True:
> PermissionError: [Errno 13] Permission denied: '/proc/5947/io'
>
> ERROR: m4-native-1.4.18-r0 do_fetch: Build of do_fetch failed
> ERROR: m4-native-1.4.18-r0 do_fetch: Traceback (most recent call last):
>   File "/home/repository/rocko/poky/bitbake/lib/bb/build.py", line 644,
> in exec_task
> return _exec_task(fn, task, d, quieterr)
>   File "/home/repository/rocko/poky/bitbake/lib/bb/build.py", line 618,
> in _exec_task
> event.fire(TaskSucceeded(task, logfn, localdata), localdata)
>   File "/home/repository/rocko/poky/bitbake/lib/bb/event.py", line 222,
> in fire
> fire_class_handlers(event, d)
>

Re: [yocto] Layer documentation for meta-raspberrypi

2017-12-11 Thread Mirza Krak

2017-12-11 12:55 GMT+01:00 Paul Barker :
> Hi all,
>
> As a quick announcement, the layer documentation for meta-raspberrypi
> is now available on Read the Docs:
> http://meta-raspberrypi.readthedocs.io/en/latest/
>
> The latest documentation is shown by default and covers the master
> branch. Using the version box in the bottom right corner of the page
> you can also switch to the rocko or pyro versions. This is
> automatically updated whenever changes are pushed to the documentation
> in meta-raspberrypi.
>
> Raspberry Pi seems to be a very common platform for newcomers to
> OE/Yocto and so I think it's really important that this layer is well
> documented and is easy to use. Please submit pull requests or open
> bugs if you think any of the documentation can be improved.
>
> We use Sphinx (http://www.sphinx-doc.org/) plus Read the Docs
> (https://readthedocs.org/) integration for this which I think is a
> pretty good setup for layer documentation in general. If anyone wants
> more details so they can do something similar for another layer then
> please let me know!

Great work and this will definitely be appreciated by all the
meta-raspberrypi users.

One little thing though, the current "theme" used which I assume is
the default Sphinx theme is not optimal IMO.

readthedocs does apply its own default theme [1] if you do not provide
one in your custom conf which looks much better (that is the look that
docs.readthedocs.io has) which is easier to read and navigate. I
believe that most developers are familiar with it as many other
projects that host documentation on readthedocs use this theme
(including the Linux kernel and more).

[1]. http://docs.readthedocs.io/en/latest/theme.html?highlight=theme

-- 
Med Vänliga Hälsningar / Best Regards

Mirza Krak
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Layer documentation for meta-raspberrypi

2017-12-11 Thread Paul Barker

On Mon, Dec 11, 2017 at 12:08 PM, Mirza Krak  wrote:
> 2017-12-11 12:55 GMT+01:00 Paul Barker :
>> Hi all,
>>
>> As a quick announcement, the layer documentation for meta-raspberrypi
>> is now available on Read the Docs:
>> http://meta-raspberrypi.readthedocs.io/en/latest/
>>
>> The latest documentation is shown by default and covers the master
>> branch. Using the version box in the bottom right corner of the page
>> you can also switch to the rocko or pyro versions. This is
>> automatically updated whenever changes are pushed to the documentation
>> in meta-raspberrypi.
>>
>> Raspberry Pi seems to be a very common platform for newcomers to
>> OE/Yocto and so I think it's really important that this layer is well
>> documented and is easy to use. Please submit pull requests or open
>> bugs if you think any of the documentation can be improved.
>>
>> We use Sphinx (http://www.sphinx-doc.org/) plus Read the Docs
>> (https://readthedocs.org/) integration for this which I think is a
>> pretty good setup for layer documentation in general. If anyone wants
>> more details so they can do something similar for another layer then
>> please let me know!
>
> Great work and this will definitely be appreciated by all the
> meta-raspberrypi users.
>
> One little thing though, the current "theme" used which I assume is
> the default Sphinx theme is not optimal IMO.
>
> readthedocs does apply its own default theme [1] if you do not provide
> one in your custom conf which looks much better (that is the look that
> docs.readthedocs.io has) which is easier to read and navigate. I
> believe that most developers are familiar with it as many other
> projects that host documentation on readthedocs use this theme
> (including the Linux kernel and more).
>
> [1]. http://docs.readthedocs.io/en/latest/theme.html?highlight=theme
>

Thanks for the feedback. The conf.py file we're using is just what was
generated by sphinx-quickstart with minimal tweaks. It sets html_theme
which is obviously overriding the default for read the docs.

I think I should be able to get the right behaviour by commenting out
the html_theme setting completely. I'll give that a go and see what
happens.

Cheers,

-- 
Paul Barker
Togán Labs Ltd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Permission denied while building rocko on Debian 8 [was: rocko build fails]

2017-12-11 Thread Mircea Gliga


So I went further and I tested in a VM running Debian 9 - there it works:
It looks like I get a Permission denied while building rocko only on 
Debian 8, *not* on Debian 9.


Debian 8 is listed as supported on /Yocto Project Reference Manual/ 
here: 
http://www.yoctoproject.org/docs/2.4/ref-manual/ref-manual.html#detailed-supported-distros

Can somebody confirm this behavior ? It's a straight forward test:

$ git clone -b rocko git://git.yoctoproject.org/poky.git
$ source poky/oe-init-build-env
$ bitbake core-image-minimal


PS I've updated the thread subject to better reflect the problem.

Thanks

On 11/12/17 09:58, Mircea Gliga wrote:

Hello,

I have a working krogoth build - I build images etc, everything is fine.
Then I wanted to try a rocko build, I installed the needed host 
packages: 
http://www.yoctoproject.org/docs/2.4/yocto-project-qs/yocto-project-qs.html#packages

Then sourced env and /bitbake core-image-minimal/.
So no extra layers involved, just poky.
I get errors like this:

ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch: 
Build of do_fetch failed
ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch: 
Traceback (most recent call last):
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py", 
line 644, in exec_task

    return _exec_task(fn, task, d, quieterr)
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py", 
line 618, in _exec_task

    event.fire(TaskSucceeded(task, logfn, localdata), localdata)
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py", 
line 222, in fire

    fire_class_handlers(event, d)
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py", 
line 134, in fire_class_handlers

    execute_handler(name, handler, event, d)
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py", 
line 106, in execute_handler

    ret = handler(event)
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 166, in run_buildstats

    write_task_data("passed", os.path.join(taskdir, e.task), e, d)
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 90, in write_task_data

    cpu, iostats, resources, childres = get_process_cputime(os.getpid())
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 29, in get_process_cputime

    with open("/proc/%d/io" % pid, "r") as f:
PermissionError: [Errno 13] Permission denied: '/proc/1530/io'

ERROR: Task 
(virtual:native:/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_fetch) 
failed with exit code '1'
ERROR: autoconf-native-2.69-r11 do_fetch: Execution of event handler 
'run_buildstats' failed

Traceback (most recent call last):
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 166, in run_buildstats(e=0x7f07f3f31898>):

 elif isinstance(e, bb.build.TaskSucceeded):
    >    write_task_data("passed", os.path.join(taskdir, e.task), 
e, d)

 if e.task == "do_rootfs":
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 90, in write_task_data(status='passed', 
logfile='/media/mircea/ExtLinux/Adventure/repository/rocko/build/tmp/buildstats/20171211074610/autoconf-native-2.69-r11/do_fetch', 
e=, 
d=):
 f.write(d.expand("Elapsed time: %0.2f seconds\n" % 
elapsedtime))
    >    cpu, iostats, resources, childres = 
get_process_cputime(os.getpid())

 if cpu:
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass", 
line 29, in get_process_cputime(pid=1543):

 if os.path.isfile("/proc/%d/io" % pid):
    >    with open("/proc/%d/io" % pid, "r") as f:
 while True:
PermissionError: [Errno 13] Permission denied: '/proc/1543/io'

ERROR: autoconf-native-2.69-r11 do_fetch: Build of do_fetch failed
ERROR: autoconf-native-2.69-r11 do_fetch: Traceback (most recent call 
last):
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py", 
line 644, in exec_task

    return _exec_task(fn, task, d, quieterr)
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py", 
line 618, in _exec_task

    event.fire(TaskSucceeded(task, logfn, localdata), localdata)
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py", 
line 222, in fire

    fire_class_handlers(event, d)
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py", 
line 134, in fire_class_handlers

    execute_handler(name, handler, event, d)
  File 
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py", 
line 106, in execute

Re: [yocto] Permission denied while building rocko on Debian 8 [was: rocko build fails]

2017-12-11 Thread Paul Barker

On Mon, Dec 11, 2017 at 12:43 PM, Mircea Gliga  wrote:
> So I went further and I tested in a VM running Debian 9 - there it works:
> It looks like I get a Permission denied while building rocko only on Debian
> 8, *not* on Debian 9.
>
> Debian 8 is listed as supported on Yocto Project Reference Manual  here:
> http://www.yoctoproject.org/docs/2.4/ref-manual/ref-manual.html#detailed-supported-distros
> Can somebody confirm this behavior ? It's a straight forward test:
>
> $ git clone -b rocko git://git.yoctoproject.org/poky.git
> $ source poky/oe-init-build-env
> $ bitbake core-image-minimal

This looks like a weird permission issue rather than something
Yocto-related. How are you running your Debian 8 system? Is it bare
metal, VM, container, some hosting providers VPS, etc?

>
>
> PS I've updated the thread subject to better reflect the problem.
>
> Thanks
>
> On 11/12/17 09:58, Mircea Gliga wrote:
>
> Hello,
>
> I have a working krogoth build - I build images etc, everything is fine.
> Then I wanted to try a rocko build, I installed the needed host packages:
> http://www.yoctoproject.org/docs/2.4/yocto-project-qs/yocto-project-qs.html#packages
> Then sourced env and bitbake core-image-minimal.
> So no extra layers involved, just poky.
> I get errors like this:
>
> ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch: Build
> of do_fetch failed
> ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch:
> Traceback (most recent call last):
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
> line 644, in exec_task
> return _exec_task(fn, task, d, quieterr)
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
> line 618, in _exec_task
> event.fire(TaskSucceeded(task, logfn, localdata), localdata)
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
> line 222, in fire
> fire_class_handlers(event, d)
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
> line 134, in fire_class_handlers
> execute_handler(name, handler, event, d)
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
> line 106, in execute_handler
> ret = handler(event)
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
> line 166, in run_buildstats
> write_task_data("passed", os.path.join(taskdir, e.task), e, d)
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
> line 90, in write_task_data
> cpu, iostats, resources, childres = get_process_cputime(os.getpid())
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
> line 29, in get_process_cputime
> with open("/proc/%d/io" % pid, "r") as f:
> PermissionError: [Errno 13] Permission denied: '/proc/1530/io'
>
> ERROR: Task
> (virtual:native:/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_fetch)
> failed with exit code '1'
> ERROR: autoconf-native-2.69-r11 do_fetch: Execution of event handler
> 'run_buildstats' failed
> Traceback (most recent call last):
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
> line 166, in run_buildstats(e= 0x7f07f3f31898>):
>  elif isinstance(e, bb.build.TaskSucceeded):
> >write_task_data("passed", os.path.join(taskdir, e.task), e, d)
>  if e.task == "do_rootfs":
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
> line 90, in write_task_data(status='passed',
> logfile='/media/mircea/ExtLinux/Adventure/repository/rocko/build/tmp/buildstats/20171211074610/autoconf-native-2.69-r11/do_fetch',
> e=,
> d=):
>  f.write(d.expand("Elapsed time: %0.2f seconds\n" %
> elapsedtime))
> >cpu, iostats, resources, childres =
> get_process_cputime(os.getpid())
>  if cpu:
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
> line 29, in get_process_cputime(pid=1543):
>  if os.path.isfile("/proc/%d/io" % pid):
> >with open("/proc/%d/io" % pid, "r") as f:
>  while True:
> PermissionError: [Errno 13] Permission denied: '/proc/1543/io'
>
> ERROR: autoconf-native-2.69-r11 do_fetch: Build of do_fetch failed
> ERROR: autoconf-native-2.69-r11 do_fetch: Traceback (most recent call last):
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
> line 644, in exec_task
> return _exec_task(fn, task, d, quieterr)
>   File
> "/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
> line 618, in _exec_task
> event.fire(TaskSucceeded(task, logfn, localdata), localdata)
>   File
> "/media/mircea/ExtLinux/Adventur

[yocto] Checksum of an external file

2017-12-11 Thread Anton Gerasimov

Hi,

my recipe takes a path to a file on user's file system as an input,
processes it and stores on the device. Sometimes user wants to update
this file and I'd like the recipe to be rebuilt every time the file
itself changes, even if the file path didn't.

So I had an illusion to understand how sstate cache works and wrote the
following code:

    def calculate_file_sha256(bb, d):
        return bb.utils.sha256_file(d.getVar("PATH_TO_FILE"))

    PATH_TO_FILE[vardepvalue] = "${@calculate_file_sha256(bb, d)}"

Unfortunately this doesn't work as expected (the recipe doesn't get
rebuilt when the file changes, looks like calculate_file_sha256 doesn't
run unless PATH_TO_FILE has changed) and at the same time if I
'cleanall' the recipe and change the file before rebuilding I get a lot
of "metadata is not deterministic" errors.

Is there a proper way to do that with bitbake?

Thanks,
Anton Gerasimov



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] [PATCH 47/48] kernel/sched: Revert compile fixes

2017-12-11 Thread Daniel Dragomir

From: Charlie Paul 

These changes were needed for the kernel to compile after
applying the three previous revert patches.

Signed-off-by: Charlie Paul 
---
 kernel/sched/core.c | 2 +-
 kernel/sched/rt.c   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 54bbbd9..a7d0587 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -1757,7 +1757,7 @@ int select_task_rq(struct task_struct *p, int cpu, int 
sd_flags, int wake_flags)
 {
lockdep_assert_held(&p->pi_lock);
 
-   if (tsk_nr_cpus_allowed(p) > 1)
+   if (p->nr_cpus_allowed > 1)
cpu = p->sched_class->select_task_rq(p, cpu, sd_flags, 
wake_flags);
else
cpu = cpumask_any(tsk_cpus_allowed(p));
diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
index 32be096..701eddf 100644
--- a/kernel/sched/rt.c
+++ b/kernel/sched/rt.c
@@ -2198,7 +2198,7 @@ static void switched_to_rt(struct rq *rq, struct 
task_struct *p)
 */
if (task_on_rq_queued(p) && rq->curr != p) {
 #ifdef CONFIG_SMP
-   if (tsk_nr_cpus_allowed(p) > 1 && rq->rt.overloaded)
+   if (p->nr_cpus_allowed > 1 && rq->rt.overloaded)
queue_push_tasks(rq);
 #endif /* CONFIG_SMP */
if (p->prio < rq->curr->prio)
-- 
2.7.4

-- 
___
linux-yocto mailing list
linux-yo...@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [yocto] Permission denied while building rocko on Debian 8 [was: rocko build fails]

2017-12-11 Thread Mircea Gliga

On 11/12/17 15:06, Paul Barker wrote:

On Mon, Dec 11, 2017 at 12:43 PM, Mircea Gliga  wrote:

So I went further and I tested in a VM running Debian 9 - there it works:
It looks like I get a Permission denied while building rocko only on Debian
8, *not* on Debian 9.

Debian 8 is listed as supported on Yocto Project Reference Manual  here:
http://www.yoctoproject.org/docs/2.4/ref-manual/ref-manual.html#detailed-supported-distros
Can somebody confirm this behavior ? It's a straight forward test:

$ git clone -b rocko git://git.yoctoproject.org/poky.git
$ source poky/oe-init-build-env
$ bitbake core-image-minimal

This looks like a weird permission issue rather than something
Yocto-related. How are you running your Debian 8 system? Is it bare
metal, VM, container, some hosting providers VPS, etc?

Debian 8 is running on a real system, no VM etc.
I used netinstall with no desktop environment and without all the blows 
and whistles and added just what I needed, when I needed it.
This machine was used for the last 1,5 years or so for developing on 
Krogoth.
I was able to reproduce the problem on a second box, real machine, 
running Debian 8

Meanwhile I tried building rocko on another real machine, running Debian 
9 - it works. ( in the prev email I tested in a Debian 9 VM)

Thanks

PS I've updated the thread subject to better reflect the problem.

Thanks

On 11/12/17 09:58, Mircea Gliga wrote:

Hello,

I have a working krogoth build - I build images etc, everything is fine.
Then I wanted to try a rocko build, I installed the needed host packages:
http://www.yoctoproject.org/docs/2.4/yocto-project-qs/yocto-project-qs.html#packages
Then sourced env and bitbake core-image-minimal.
So no extra layers involved, just poky.
I get errors like this:

ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch: Build
of do_fetch failed
ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch:
Traceback (most recent call last):
   File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
line 644, in exec_task
 return _exec_task(fn, task, d, quieterr)
   File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
line 618, in _exec_task
 event.fire(TaskSucceeded(task, logfn, localdata), localdata)
   File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
line 222, in fire
 fire_class_handlers(event, d)
   File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
line 134, in fire_class_handlers
 execute_handler(name, handler, event, d)
   File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
line 106, in execute_handler
 ret = handler(event)
   File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 166, in run_buildstats
 write_task_data("passed", os.path.join(taskdir, e.task), e, d)
   File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 90, in write_task_data
 cpu, iostats, resources, childres = get_process_cputime(os.getpid())
   File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 29, in get_process_cputime
 with open("/proc/%d/io" % pid, "r") as f:
PermissionError: [Errno 13] Permission denied: '/proc/1530/io'

ERROR: Task
(virtual:native:/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_fetch)
failed with exit code '1'
ERROR: autoconf-native-2.69-r11 do_fetch: Execution of event handler
'run_buildstats' failed
Traceback (most recent call last):
   File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 166, in run_buildstats(e=):
  elif isinstance(e, bb.build.TaskSucceeded):
 >write_task_data("passed", os.path.join(taskdir, e.task), e, d)
  if e.task == "do_rootfs":
   File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 90, in write_task_data(status='passed',
logfile='/media/mircea/ExtLinux/Adventure/repository/rocko/build/tmp/buildstats/20171211074610/autoconf-native-2.69-r11/do_fetch',
e=,
d=):
  f.write(d.expand("Elapsed time: %0.2f seconds\n" %
elapsedtime))
 >cpu, iostats, resources, childres =
get_process_cputime(os.getpid())
  if cpu:
   File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 29, in get_process_cputime(pid=1543):
  if os.path.isfile("/proc/%d/io" % pid):
 >with open("/proc/%d/io" % pid, "r") as f:
  while True:
PermissionError: [Errno 13] Permission denied: '/proc/1543/io'

ERROR: autoconf-native-2.69-r11 do_fetch: Build of do_fetch failed
ERROR: autoconf-native-2.69-r11 do_fetch: Traceback (most recent call last):
   File
"/media/mircea/ExtLinux/

[yocto] recipe to clean up files from rootfs

2017-12-11 Thread Sherif Omran

i want to create a recipe to clean some files from the rootfile system, but
i don't know how to let this recipe run the last one before building the
rootfile system.

any idea?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] VPS for building and serving.

2017-12-11 Thread Daniel.

Thanks for the feedback Paul,

I thinking about compiling with own server and only serving the packages
online..

Regards,

2017-12-11 9:12 GMT-02:00 Paul Barker :

> On Sun, Dec 10, 2017 at 1:15 PM, Daniel.  wrote:
> > Hi,
> >
> > Is there anybody using VPS for building and serving packages? What plans
> you
> > do recommend?
>
> I don't recommend using a VPS, they tend to get expensive for the spec
> you need for a Yocto build. You want plenty of RAM, CPU and disk
> space.
>
> I use Hetzner for everything and I'm pretty happy with them. They have
> a server auction system that's good if you don't need a
> top-of-the-line machine: https://www.hetzner.com/sb
>
> Let me know if you need any more specific advice.
>
> Cheers,
>
> --
> Paul Barker
> Togán Labs Ltd
>



-- 
“If you're going to try, go all the way. Otherwise, don't even start. ..."
  Charles Bukowski
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] VPS for building and serving.

2017-12-11 Thread Mike Looijmans


On 11-12-17 12:12, Paul Barker wrote:

On Sun, Dec 10, 2017 at 1:15 PM, Daniel.  wrote:

Hi,

Is there anybody using VPS for building and serving packages? What plans you
do recommend?


I don't recommend using a VPS, they tend to get expensive for the spec
you need for a Yocto build. You want plenty of RAM, CPU and disk
space.


Saparate the two.

Use a private desktop machine for building images and feeds. You probably 
already have it...


For serving packages, any HTTP server will do, so you can use any cheap plain 
and simple file based hosting.
Update the feed using rsync, or just use a script that copies the newer files 
over to the hosting.


It's also a much better option security wise.


Kind regards,

Mike Looijmans
System Expert

TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Checksum of an external file

2017-12-11 Thread Alexander Kanavin


On 12/11/2017 03:19 PM, Anton Gerasimov wrote:

Unfortunately this doesn't work as expected (the recipe doesn't get
rebuilt when the file changes, looks like calculate_file_sha256 doesn't
run unless PATH_TO_FILE has changed) and at the same time if I
'cleanall' the recipe and change the file before rebuilding I get a lot
of "metadata is not deterministic" errors.

Is there a proper way to do that with bitbake?


I don't think so. You need to write an external script that copies the 
file into the layer, then runs bitbake. The recipe should simply refer 
to the file via SRC_URI file fetcher.


Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] recipe to clean up files from rootfs

2017-12-11 Thread Alexander Kanavin


On 12/11/2017 04:18 PM, Sherif Omran wrote:
i want to create a recipe to clean some files from the rootfile system, 
but i don't know how to let this recipe run the last one before building 
the rootfile system.


Have a look at ROOTFS_POSTPROCESS_COMMAND.

Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Checksum of an external file

2017-12-11 Thread Anton Gerasimov


> I don't think so. You need to write an external script that copies the
> file into the layer, then runs bitbake. The recipe should simply refer
> to the file via SRC_URI file fetcher.

Thank you a lot, that actually works without copying: SRC_URI works with
absolute pathes as well. Such a straightworward solution has never
occured to me for some reason.

- Anton

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] user space package recommends kernel fragment with builting CONFIG

2017-12-11 Thread Paulo Neves

Hello all,

I have the idea I am doing someting in a strange way but correct me if
I am wrong.
I want to make hostapd RRECOMEND .config fragments which have wireless
drivers. How do I achieve this?

Paulo Neves
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW50’17

2017-12-11 Thread Jolley, Stephen K

Current Dev Position: YP 2.5 M2 development

Next Deadline: YP 2.5 M2 cut off of 1/15/18


SWAT team rotation: Tracy -> Stephano on Dec. 8, 2017.

SWAT team rotation: Stephano -> Maxin on Dec. 15, 2017.

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

·The morty hang has been traced to a uninative glibc incompatibility 
issue and there is a fix merged. Other releases are not affected as recipe 
specific sysroots doesn’t have the issue. We also figured out the eSDK failures 
are also uninative related and this fix does affect all releases including 
master. This means morty should be unblocked and a point release able to head 
to QA soon.

·The rocko point release build is now in QA.

·The master/mut/master-next failures were tracked down to:

o   an issues with the elf image type removal

o   a buggy upgrade of i2c-tools

o   a kernel upgrade which broke automated testing

o   a problem with multilib and PREFERRRED_RPROVIDER

o   a determinism problem in bitbake itself in providers.py (only when 
PREFERRED_*PROVIDER wasn’t set)

·The kvm apic hang appears to resolve when “echo 1 > 
/proc/sys/vm/drop_caches” is triggered, suggesting it’s a kernel memory 
fragmentation issue (making two different kvm memory fragmentation issues we 
have).

·We found the drop_caches trip also helps with the other kvm ENOMEM 
issue we were seeing too. We have this automated on the autobuilders but it's 
currently frequent enough to avoid the apic hangs.

·Patches for M1 have merged although I’m aware we have a long backlog. 
We will likely make an M1 build and then handle the majority of the queue in 
M2. M1 isn’t being rushed as QA are busy with 2.4.1 (rocko point release).


Planned upcoming dot releases:

YP 2.4.1 (Rocko) rc1 is in QA.  See 
https://wiki.yoctoproject.org/wiki/2.4_QA_Status.

YP 2.2.3 (Morty) is planned and should build sometime after YP 2.5 M1 is sent 
to QA.

YP 2.3.3 (Pyro) is planned for sometime after YP 2.2.3 is done.


Key YP 2.5 Dates are:

YP 2.5 M1 cut off of 12/4/17 (Should build this week.)

YP 2.5 M1 release of 12/15/17 (Will be later this month.)

YP 2.5 M2 cut off of 1/15/18

YP 2.5 M2 release of 1/26/18

YP 2.5 M3 cut off of 2/19/18

YP 2.5 M3 release of 3/2/18

YP 2.5 M4 cut off of 4/2/18

YP 2.5 M4 release of 4/27/18


Tracking Metrics:

WDD 2690 (last week 2687)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features

[If anyone has suggestions for other information you’d like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
•   Work Telephone:(503) 712-0534
•Cell:  (208) 244-4460
• Email:stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] executable depends on the library that is built in the same recipe

2017-12-11 Thread Rail Shafigulin

I have a recipe that builds a library and an executable. Executable
depends on the library which built int he same recipe. When I run
bitbake I get the following error:

WARNING: mytool-1.0+gitAUTOINC+3e2b76e330-r0 do_package_qa: QA Issue:
/bin/mytool contained in package mytool requires libMyTool.so, but no
providers found in RDEPENDS_mytool? [file-rdeps]

I tried the suggestion given by the bitbake putting mytool in
REDEPNDS_${PN}, but that didn't work. I also tried looking online for
the solution but didn't find one.

Can someone help out?


-- 
Rail Shafigulin
Software Engineer
Esencia Technologies

-- 




*ESENCIA TECHNOLOGIES, INC.*3945 Freedom Circle, Suite #360,
Santa Clara CA 95054


Phone: +1 408 736 8284 Fax: +1 408 519 3475 
http://www.esenciatech.com | http://www.lnttechservices.com


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] executable depends on the library that is built in the same recipe

2017-12-11 Thread Jeremy A. Puhlman

Given it is looking for libMyTool.so and not a versioned library, my 
guess is that the shared
library is not setting a proper soname when being built. All libraries 
should be built with a soname,
and if done correctly should be versioned.  The .so file generally 
shouldn't be the runtime library
but a link back to the versioned library, so you get something that 
looks like:


/usr/lib/libz.so -> libz.zo.1.2.11
/usr/lib/libz.so.1.2.11
/usr/lib/libz.so.1 -> libz.so.1


On 12/11/2017 11:45 AM, Rail Shafigulin wrote:

I have a recipe that builds a library and an executable. Executable
depends on the library which built int he same recipe. When I run
bitbake I get the following error:

WARNING: mytool-1.0+gitAUTOINC+3e2b76e330-r0 do_package_qa: QA Issue:
/bin/mytool contained in package mytool requires libMyTool.so, but no
providers found in RDEPENDS_mytool? [file-rdeps]

I tried the suggestion given by the bitbake putting mytool in
REDEPNDS_${PN}, but that didn't work. I also tried looking online for
the solution but didn't find one.

Can someone help out?




--
Jeremy A. Puhlman
jpuhl...@mvista.com

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] user space package recommends kernel fragment with builting CONFIG

2017-12-11 Thread Bruce Ashfield


On 2017-12-11 10:19 AM, Paulo Neves wrote:

Hello all,

I have the idea I am doing someting in a strange way but correct me if
I am wrong.
I want to make hostapd RRECOMEND .config fragments which have wireless
drivers. How do I achieve this?


You can't really do it via the hostapd recipe, since if you could, you'd
break the separation between recipes (and if the build system allowed
it, you'd be able to influence any other recipe from another .. and a
lot would break).

You'll need to have a kernel bbappend in your layer, and from there,
you can use the KERNEL_FEATURES variable (if the fragment is in the
common kernel-cache) or put a .cfg fragment on the SRC_URI.

If you want to conditionally trigger the SRC_URI addition or the
KERNEL_FEATURE, you could use a distro feature that both hostapd
and the kernel recipe use to enable a set of common features.

Cheers,

Bruce





Paulo Neves



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] executable depends on the library that is built in the same recipe

2017-12-11 Thread Vineeth Karumanchi


using this might help

oe_libinstall -so

On 12/12/2017 1:24 AM, Jeremy A. Puhlman wrote:
Given it is looking for libMyTool.so and not a versioned library, my 
guess is that the shared
library is not setting a proper soname when being built. All libraries 
should be built with a soname,
and if done correctly should be versioned.  The .so file generally 
shouldn't be the runtime library
but a link back to the versioned library, so you get something that 
looks like:


/usr/lib/libz.so -> libz.zo.1.2.11
/usr/lib/libz.so.1.2.11
/usr/lib/libz.so.1 -> libz.so.1


On 12/11/2017 11:45 AM, Rail Shafigulin wrote:

I have a recipe that builds a library and an executable. Executable
depends on the library which built int he same recipe. When I run
bitbake I get the following error:

WARNING: mytool-1.0+gitAUTOINC+3e2b76e330-r0 do_package_qa: QA Issue:
/bin/mytool contained in package mytool requires libMyTool.so, but no
providers found in RDEPENDS_mytool? [file-rdeps]

I tried the suggestion given by the bitbake putting mytool in
REDEPNDS_${PN}, but that didn't work. I also tried looking online for
the solution but didn't find one.

Can someone help out?





--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] rocko build fails

Re: [yocto] rocko build fails

[yocto] OpenEmbedded stand at FOSDEM 2018

Re: [yocto] rocko build fails

Re: [yocto] rocko build fails

Re: [yocto] VPS for building and serving.

Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail

Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail

Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail

[yocto] Layer documentation for meta-raspberrypi

Re: [yocto] rocko build fails

Re: [yocto] Layer documentation for meta-raspberrypi

Re: [yocto] Layer documentation for meta-raspberrypi

Re: [yocto] Permission denied while building rocko on Debian 8 [was: rocko build fails]

Re: [yocto] Permission denied while building rocko on Debian 8 [was: rocko build fails]

[yocto] Checksum of an external file

[linux-yocto] [PATCH 47/48] kernel/sched: Revert compile fixes

Re: [yocto] Permission denied while building rocko on Debian 8 [was: rocko build fails]

[yocto] recipe to clean up files from rootfs

Re: [yocto] VPS for building and serving.

Re: [yocto] VPS for building and serving.

Re: [yocto] Checksum of an external file

Re: [yocto] recipe to clean up files from rootfs

Re: [yocto] Checksum of an external file

[yocto] user space package recommends kernel fragment with builting CONFIG

[yocto] Yocto Project Status WW50’17

[yocto] executable depends on the library that is built in the same recipe

Re: [yocto] executable depends on the library that is built in the same recipe

Re: [yocto] user space package recommends kernel fragment with builting CONFIG

Re: [yocto] executable depends on the library that is built in the same recipe

30 matches

Site Navigation

Mail list logo

Footer information