Re: [yocto] how do you create a non-read only root file system when making a iso based project
Hi, Please search documentation first: http://www.yoctoproject.org/docs/2.3.1/yocto-project-qs/yocto-project-qs.html#building-an-image-for-emulation http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#dev-manual-qemu Best regards, Chris Z. 06.08.2017 01:07 "blackthirt33n ." napisał(a): how do you create a non-read only root files system when make an iso based project. I had created an iso image by doing the following bitbake core-image-minimal wic create directdisk -e core-image-minimal this created an iso that did boot using qemu qemu-system-x86_64 -boot d -cdrom ./core-image-minimal-genericx86-64.iso -m 512 But, the root file system was read-only. What steps would I need to take to make root filesystem that can be written to? James -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] using wic to build an iso
Hi, It's starting from here: http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#creating-partitioned-images P.S. This link is to latest doc. Best regards, Chris Z. 05.08.2017 19:22 "blackthirt33n ." napisał(a): > is there documentation on how to use wic to create a bootable iso for > an x64/x86 target? > James > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Conflicting recipes / How to set SSTATE_DUPWHITELIST?
Performing pretty much a default build of petalinux 2016.4, Yocto gives me an error because two recipes are creating the same README file. The conflict is only in the README file, and the build goes fine if I delete the file after the first recipe creates it but before the second tries to replace it (but it is bothersome doing this every time). Since the conflict is only in a README file, the appropriate fix to me seems to add it to SSTATE_DUPWHITELIST. How would I do this? I've never used yocto and couldn't ctrl+f information in the manual on where such options are set. Would it go in the main *.bb file? Build log: https://pastebin.com/KrzQvW7d -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Release Candidate Build for yocto-2.4_M2.rc1 now available.
A release candidate build for yocto-2.4_M2.rc1 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.4_M2.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 009d044176d965d5ccf96f473be8be61146eefb2 meta-qt4 : 8758214a054c2127580d781aa0ca9b811c8d20ee refkit : 656e0c4d51379145ae01374c15a3a08c27cf864a meta-mingw : 0679d2a91575bd7f3efd0973aa99d7ee681e9395 meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f meta-gplv2 : 07e5dd2136a2a7cc069ad8c70bb422fa9d5b14f0 poky : 961d2366de97da7f3ced1238d6268237fa0906e2 \nThis is an automated message from\nThe Yocto Project Autobuilder\nGit: git://git.yoctoproject.org/yocto-autobuilder\nEmail: pi...@toganlabs.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Release Candidate Build for yocto-2.4_M2.rc2 now available.
A release candidate build for yocto-2.4_M2.rc2 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.4_M2.rc2 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 009d044176d965d5ccf96f473be8be61146eefb2 meta-qt4 : 8758214a054c2127580d781aa0ca9b811c8d20ee refkit : 656e0c4d51379145ae01374c15a3a08c27cf864a meta-mingw : 0679d2a91575bd7f3efd0973aa99d7ee681e9395 meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f meta-gplv2 : 07e5dd2136a2a7cc069ad8c70bb422fa9d5b14f0 poky : 8e15e9b6e478f6368034519b2a8fd3c7ea71d23b \nThis is an automated message from\nThe Yocto Project Autobuilder\nGit: git://git.yoctoproject.org/yocto-autobuilder\nEmail: pi...@toganlabs.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Build only 32 bit packages using multilib in a packagegroup for 64 bit machine
Hello, I need to use multilib feature in yocto to build some applications which are part of a packagegroup recipe as only 32 bit. I can use command to create 32 bit packages from this packagegroup which works,. # bitbake lib32-packagegroup-name.bb But the packages in this packagegroup are still building as 64 bit when i am trying to build image bitbake core-sato-image.bb Configuration done in local.conf : MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" In image recipe replaced IMAGE_INSTALL += "packagegroup-name" to IMAGE_INSTALL += "lib32-packagegroup-name" Are these changes sufficient ? Thanks gaurav -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Enable only 32 bit packages in a packagegroup for 64 bit machine
Hello, I need to use multilib feature in yocto to build some applications which are part of a packagegroup recipe as only 32 bit. I can use command to create 32 bit packages from this packagegroup which works,. # bitbake lib32-packagegroup-name.bb But the packages in this packagegroup are still building as 64 bit when i am trying to build image bitbake core-sato-image.bb Configuration done in local.conf : MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" In image recipe replaced IMAGE_INSTALL += "packagegroup-name" to IMAGE_INSTALL += "lib32-packagegroup-name" Please suggest, how i can i get to only build 32 bit package in packagegroup. Thanks gaurav -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] feature request: avoid getting the server stuck because of high "-j" value
Hello Yocto developers! recently I found a really nice make feature, that tunes at runtime the number of parallel execution jobs, according to the current system load [1]. I think such a feature would be really nice on server were multiple yocto builds are run in parallel, and when people forgets to put the correct number of parallel build jobs. E.g., a number around CPU+1 is nice, but sometimes CPU*2 gives better results. Unfortunately if somebody else starts a build in parallel, that CPU*2 locks really hard the server, specially when building qt-based projects (e.g. qtbase, qtwebengine). Tuning such value at runtime will probably end in faster compilation time and lower swapping on remote servers. (I would think also to something that checks the amount of free RAM) is such a feature feasible? [1] https://www.gnu.org/software/make/manual/html_node/Parallel.html#Parallel thanks, Gianfranco -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Conflicting recipes / How to set SSTATE_DUPWHITELIST?
hi,
if you need to build both of the packages, a quick and dirty workaround would
be to add a line like this to one of the recipes
do_install_append() {
rm -rf ${D}/foo/README
}
to delete the README before packaging
On Mon, 7 Aug 2017 00:02:59 +0200
Peter Vutov wrote:
> Performing pretty much a default build of petalinux 2016.4, Yocto gives
> me an error because two recipes are creating the same README file. The
> conflict is only in the README file, and the build goes fine if I delete
> the file after the first recipe creates it but before the second tries
> to replace it (but it is bothersome doing this every time).
>
> Since the conflict is only in a README file, the appropriate fix to me
> seems to add it to SSTATE_DUPWHITELIST. How would I do this? I've never
> used yocto and couldn't ctrl+f information in the manual on where such
> options are set. Would it go in the main *.bb file?
>
> Build log: https://pastebin.com/KrzQvW7d
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Markus Volk
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] extensible SDK build failure
Hi Russell, On Wednesday, 2 August 2017 8:34:11 PM CEST RUSSELL PETERSON wrote: > Frustrating in that I can't get the eSDK to fully build. I'm past the issue > with kernel-devsrc and harfbuzz... but now I see hundreds of messages like > below. Anyone seen this before? From what I can tell these tasks are being > executed out of the run queue. Not all the messages are from cve-check but > most. So there are certain classes that will interfere with the ability of the eSDK to lock down the configuration, I wasn't aware of it but cve-check.bbclass is apparently one of them. Try adding this to your configuration: SDK_INHERIT_BLACKLIST = "buildhistory icecc cve-check" Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
