Re: [yocto] Core-image-weston network problems
Thanks! It worked out for me. I made a RC script and placed it in /etc/init.d/. In /etc/rc5.d/ I added a symlink which was after the network symlink. Worked great . From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: 30. juli 2015 11:06 To: Eirik Solberg Hamnvik Cc: yocto@yoctoproject.org Subject: Re: [yocto] Core-image-weston network problems On 30 July 2015 at 06:28, Eirik Solberg Hamnvik mailto:eirik.solberg.hamn...@tomra.com>> wrote: The perfect thing would be to make my package dependent on whichever package that configures the network settings, so I am guaranteed that it will download succesfully. Which one is that? Or are there any better solutions? Don't use a postinstall script, which by definition has to run early. Write a normal init script that deletes itself after completion and schedule it to come after networking (which is a can of worms, you'll have more luck if you use systemd here). Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Core-image-weston network problems
Hey! I am building core-image-weston. Branch fido. I have a postinstall script that runs some code on first startup. The script is supposed to do apt-get install of some packages. The problem is that the postinstall script runs before the network is correctly configured. Meaning my packages wont download. When it is fully booted I can manually do apt-get install and it works fine. For now I am using the 'at'-command to solve this issue, but I need to change that. The perfect thing would be to make my package dependent on whichever package that configures the network settings, so I am guaranteed that it will download succesfully. Which one is that? Or are there any better solutions? Eirik -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto with meta-java. Multiple providers problem.
So I am trying to add the meta-java (http://layers.openembedded.org/layerindex/branch/master/layer/meta-java/) to my image with yocto. Just to get it to build I have not yet deleted any of the recipes which comes along with it. When I try to run: bitbake -k core-image-sato I get this error: "ERROR: Multiple .bb files are due to be built which each provide virtual/javac-native (/home/frank/poky/meta-java/recipes-core/ecj/ecj-bootstrap-native.bb virtual:native:/home/frank/poky/meta-java/recipes-core/jikes/jikes_1.22.bb). This usually means one provides something the other doesn't and should." and: ERROR: The recipe ecj-bootstrap-native is trying to install files into a >shared area when those files already exist. Those files and their manifest >location are: /home/frank/poky/build/tmp/sysroots/x86_64-linux/sysroot-providers>/virtual_javac-native Matched in manifest-x86_64-jikes-native.populate_sysroot Please verify which recipe should provide the above files." In my build/conf/local.conf file I have set: PREFERRED_PROVIDER_virtual/java-native = "jamvm-native" PREFERRED_PROVIDER_virtual/javac-native = "ecj-bootstrap-native" PREFERRED_VERSION_openjdk-7-jre = "75b13-2.5.4" PREFERRED_VERSION_icedtea7-native = "2.1.3" PREFERRED_PROVIDER_openjdk-7-jre = "openjdk-7-jre" I have seen several discussion about this problem but none of the solutions helped me. Usually they answer that I need to set the PREFERRED_PROVIDER_virtual/java-native in my local.conf or distro.conf. I have tried both of these solutions, but without any luck. Also, most of these discussion where 5-6 years old (guess they're a bit out-dated). Can anyone help me? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Recipe runs before network is established on target, causes problems.
Hey! I have a recipe where I in the pkg_postinst_mypackage () function runs apt-get update on first boot only. This doesn't work. I've seen the logfile which says: Cannot initiate the connection to xxx.xxx.xxx.xxx - connect (101: Network is unreachable). If I manually go to the terminal after it has booted and type "apt-get update" it works perfectly fine. Guess that means that my code tries to run before the network settings are established. Is there some way I could manage this? Eirik -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
