[yocto] Post-installation and read-only-image

2014-05-23 Thread Neuer User
Hello I build a read-only-image and need to exchange a few configuration files before the final image is build. Unfortunately, I ran into this error: ERROR: The following packages could not be configuredoffline and rootfs is read-only: xxx My recipe looks basically as follows: ... do_install()

[yocto] Setting default system python version

2014-05-23 Thread Diego Sueiro
Folks, I did not fount it on manuals. How can I set the default system python version for an image? Regards, -- *dS Diego Sueiro Administrador do Embarcados www.embarcados.com.brhttp://www.embarcados.com.br/?utm_source=assinatura_diegoutm_medium=e-mailutm_campaign=Assinatura%20Email%20Diego

[yocto] [Probably solved] Re: Post-installation and read-only-image

2014-05-23 Thread Neuer User
Sorry, please ignore my mail. I seem to have missed a install -d command. Not it builds the image, but I still seem to have some errors I need to fix. Thanks nonetheless! Michael Am 23.05.2014 16:23, schrieb Neuer User: Hello I build a read-only-image and need to exchange a few

Re: [yocto] Setting default system python version

2014-05-23 Thread Diego Sueiro
Now python3-distutils returns the following on do_compile: Log data follows: | DEBUG: Executing shell function do_compile | Traceback (most recent call last): | File setup.py, line 45, in module | exec(init_file.read(), d) | File string, line 8, in module | File

Re: [yocto] Strange certificate problem with wget

2014-05-23 Thread Neuer User
Btw, this works beautifully. Thanks a lot! Michael Am 21.05.2014 17:02, schrieb Burton, Ross: On 21 May 2014 11:49, Auslands-KV auslands...@gmx.de wrote: That's it. It does't seem to know where they are. If I add the option with the path, it works. Do I miss something in my local.conf?

[yocto] Yocto with Initial RamFS

2014-05-23 Thread Brian Smucker
Hello, I have an initial ramfs image that I want to convert to Yocto. That is in addition to the main yocto-based custom distro. The initial ram fs is a tiny image based on uclibc (poky-tiny) and having busybox and two other compiled apps. The main file system is eglibc-based. How is

Re: [linux-yocto] [PATCH 00/24] [linux-yocto-3.10] [Scenerio 1] Enable feature branch for Valley Island features

2014-05-23 Thread Ong, Boon Leong
So however you got a merge conflict. Your tree wasn't up to date. I do not encounter any merge conflicts, is just that the branches is not merging. By checking my build, I notice that the valleyisland-io-1.0 branch has the same HEAD of standard/base (which means I don't see any

Re: [linux-yocto] [PATCH 00/24] [linux-yocto-3.10] [Scenerio 1] Enable feature branch for Valley Island features

2014-05-23 Thread Bruce Ashfield
On 14-05-23 06:48 AM, Ong, Boon Leong wrote: So however you got a merge conflict. Your tree wasn't up to date. I do not encounter any merge conflicts, is just that the branches is not merging. By checking my build, I notice that the valleyisland-io-1.0 branch has the same HEAD of

Re: [linux-yocto] [PATCH 00/24] [linux-yocto-3.10] [Scenerio 1] Enable feature branch for Valley Island features

2014-05-23 Thread Ong, Boon Leong
SRCREV_machine ?= f53a6114b3a6e8c03ca4752de829887015f4c942 And retry ? Retry on the new commit and git describe valleyisland-io-1.0 shows v3.10.38-2618-g8ea4fb6. Perfect! *Sherlock Holmes's* style of solving linux-yocto branch merge mystery. We are good now! Thanks a bunch Bruce! --

Re: [linux-yocto] [PATCH 00/24] [linux-yocto-3.10] [Scenerio 1] Enable feature branch for Valley Island features

2014-05-23 Thread Bruce Ashfield
On 14-05-23 09:26 AM, Ong, Boon Leong wrote: SRCREV_machine ?= f53a6114b3a6e8c03ca4752de829887015f4c942 And retry ? Retry on the new commit and git describe valleyisland-io-1.0 shows v3.10.38-2618-g8ea4fb6. Perfect! *Sherlock Holmes's* style of solving linux-yocto branch merge mystery. We

Re: [linux-yocto] [PATCH] [linux-yocto-3.14] beaglebone: enable the nowayout option for the watchdog

2014-05-23 Thread Bruce Ashfield
On 14-05-23 02:41 AM, Kevin Hao wrote: The default watchdog behaviour is to stop the timer if the process managing it closes the file /dev/watchdog. The system would not reboot if watchdog daemon crashes due to a bug in it or get killed by other malicious code. So we prefer to enable nowayout