*** adam3371 <adam3371!~adam3371@ip5f5ac7d3.dynamic.kabel-deutschland.de> has joined #yocto | 00:00 | |
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC | 00:04 | |
*** vineela <vineela!~vtummala@134.134.139.76> has quit IRC | 00:07 | |
adam3371 | hey there, im a bachelor student and currently im working with yocto, so im verry new in this topic. Everything worked fine and i even could compile FITimages without the rootfs but by simply adding INITRAMFS_IMAGE = "console-tdx-image" (toradex imx6ull som) i get 4 dependency loops. After a long try i managed to get rid of two of them by adding IMAGE_FSTYPES_remove = "tar.xz but i still have two left. Do someone know what | 00:11 |
---|---|---|
adam3371 | possibly I can do to solve this problem? | 00:11 |
adam3371 | thank you in advance ;) | 00:12 |
*** dev1990 <dev1990!~dev@dynamic-78-8-104-31.ssp.dialog.net.pl> has quit IRC | 00:24 | |
*** adam3371 <adam3371!~adam3371@ip5f5ac7d3.dynamic.kabel-deutschland.de> has quit IRC | 00:58 | |
*** rdude <rdude!0ec9386e@14-201-56-110.static.tpgi.com.au> has joined #yocto | 01:00 | |
rdude | Hi | 01:06 |
*** stephano <stephano!~stephano@c-73-164-244-205.hsd1.or.comcast.net> has quit IRC | 01:14 | |
*** Nooks <Nooks!~jasonp@c-98-239-234-32.hsd1.pa.comcast.net> has left #yocto | 01:15 | |
*** gsalazar <gsalazar!5e3ce511@gateway/web/cgi-irc/kiwiirc.com/ip.94.60.229.17> has quit IRC | 01:21 | |
*** kaspter <kaspter!~Instantbi@124.77.82.153> has joined #yocto | 01:47 | |
*** ustas_ <ustas_!~ustas@94.153.66.159> has quit IRC | 01:48 | |
*** kaspter <kaspter!~Instantbi@124.77.82.153> has quit IRC | 02:12 | |
*** ustas <ustas!~ustas@46.211.51.246> has joined #yocto | 02:16 | |
*** hpsy1 <hpsy1!~hpsy@92.118.12.53> has joined #yocto | 02:30 | |
*** mattsm <mattsm!~mattsm@76-205-175-243.lightspeed.austtx.sbcglobal.net> has quit IRC | 02:30 | |
*** mattsm <mattsm!~mattsm@76-205-175-243.lightspeed.austtx.sbcglobal.net> has joined #yocto | 02:31 | |
*** hpsy <hpsy!~hpsy@92.118.12.53> has quit IRC | 02:31 | |
kergoth | huh, BBTARGETS doesn't work well with multiconfigs. can't go 'bitbake mc:foo:' and have it run the targets defined there. admittedly probably nobody uses that variable, but.. :) | 02:34 |
*** mattsm <mattsm!~mattsm@76-205-175-243.lightspeed.austtx.sbcglobal.net> has quit IRC | 02:39 | |
*** mattsm <mattsm!~mattsm@76-205-175-243.lightspeed.austtx.sbcglobal.net> has joined #yocto | 02:41 | |
*** meow` <meow`!~sbourdeli@192.222.239.49> has quit IRC | 02:53 | |
*** NiksDev <NiksDev!~NiksDev@192.91.101.31> has quit IRC | 03:26 | |
*** NiksDev <NiksDev!~NiksDev@192.91.75.30> has joined #yocto | 03:26 | |
*** ustas <ustas!~ustas@46.211.51.246> has quit IRC | 03:48 | |
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto | 03:51 | |
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC | 03:53 | |
*** nslu2-log_ is now known as nslu2-log | 03:54 | |
*** sgw2 <sgw2!~swold@c-71-238-119-71.hsd1.or.comcast.net> has quit IRC | 04:01 | |
*** ustas_ <ustas_!~ustas@94.153.32.145> has joined #yocto | 04:11 | |
*** kroon <kroon!~kroon@213.185.29.22> has joined #yocto | 04:39 | |
*** paulg <paulg!~paulg@198-84-145-15.cpe.teksavvy.com> has quit IRC | 04:47 | |
*** ssajal <ssajal!~ssajal@otwaon1146w-lp140-01-64-229-139-21.dsl.bell.ca> has quit IRC | 04:58 | |
*** ssajal <ssajal!~ssajal@bras-base-otwaon1146w-grc-12-174-88-221-226.dsl.bell.ca> has joined #yocto | 05:00 | |
*** sgw2 <sgw2!~swold@c-71-238-119-71.hsd1.or.comcast.net> has joined #yocto | 05:08 | |
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC | 05:09 | |
*** rdude <rdude!0ec9386e@14-201-56-110.static.tpgi.com.au> has quit IRC | 05:11 | |
*** sgw2 <sgw2!~swold@c-71-238-119-71.hsd1.or.comcast.net> has quit IRC | 05:14 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 05:17 | |
*** radsquirrel <radsquirrel!~radsquirr@mail.fuzziesquirrel.com> has quit IRC | 05:20 | |
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto | 05:27 | |
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-quehexathkezgkze> has quit IRC | 05:32 | |
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC | 05:40 | |
*** radsquirrel <radsquirrel!~radsquirr@mail.fuzziesquirrel.com> has joined #yocto | 05:47 | |
*** wooosaiiii <wooosaiiii!~wooo@89-212-21-243.static.t-2.net> has joined #yocto | 05:50 | |
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto | 06:07 | |
*** matthewzmd <matthewzmd!~user@216-58-109-18.cpe.distributel.net> has quit IRC | 06:13 | |
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/irccloud.com/x-xhnvvofqgmizawiw> has joined #yocto | 06:37 | |
*** mbulut <mbulut!~nameclash@ip1f126b1a.dynamic.kabel-deutschland.de> has joined #yocto | 06:44 | |
*** ustas_ <ustas_!~ustas@94.153.32.145> has quit IRC | 06:48 | |
*** gsalazar <gsalazar!5e3ce511@gateway/web/cgi-irc/kiwiirc.com/ip.94.60.229.17> has joined #yocto | 06:52 | |
*** ustas <ustas!~ustas@46.211.6.136> has joined #yocto | 06:54 | |
*** mckoan|away is now known as mckoan | 06:54 | |
*** fl0v0 <fl0v0!~fvo@i59F44C21.versanet.de> has joined #yocto | 06:59 | |
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto | 07:17 | |
*** sagner <sagner!~ags@2a02:169:3df5::edf> has quit IRC | 07:20 | |
*** sagner <sagner!~ags@2a02:169:3df5::edf> has joined #yocto | 07:21 | |
*** fbre <fbre!91fdde45@145.253.222.69> has joined #yocto | 07:25 | |
*** ustas <ustas!~ustas@46.211.6.136> has quit IRC | 07:26 | |
fbre | Hi! Where is explained how yocto Linux boots after loading the kernel? When yocto Linux boots I want to change the filesystem root to a mountpoint of an overlay filesystem. I found this Raspi script in the internet, but the approach how that script is called (entry in cmdline.txt in boot partition) seems to be quite different to how yocto boots. | 07:31 |
fbre | http://wiki.psuter.ch/doku.php?id=solve_raspbian_sd_card_corruption_issues_with_read-only_mounted_root_partition | 07:32 |
*** ustas <ustas!~ustas@46.211.6.136> has joined #yocto | 07:32 | |
LetoThe2nd | fbre: there is no documentation on this because it is board specific, not yocto specific. it depends on the bootloader in use, and the mechanisms it applies. | 07:33 |
fbre | I use u-boot which loads and starts the kernel. But that script I want to add (see my link above) uses stuff which requires a loaded kernel already. That's why I think it's already all about mechanisms already within Linux and the distro concepts. | 07:37 |
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto | 07:40 | |
LetoThe2nd | fbre: the cmdline.txt part is absolutely rpi specific. agreed on that the script runs in userland but it again is pretty rpi specific | 07:41 |
*** PaowZ_ <PaowZ_!~Vince@193.252.149.222> has quit IRC | 07:41 | |
LetoThe2nd | fbre: i know that it is a recurring topic these days to have a ro-rootfs + overlay, but so far nobody has shared an approach to refer to. | 07:42 |
*** ustas <ustas!~ustas@46.211.6.136> has quit IRC | 07:45 | |
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC | 07:49 | |
*** ustas <ustas!~ustas@holdings.sink.volia.net> has joined #yocto | 07:50 | |
*** PaowZ_ <PaowZ_!~Vince@193.252.149.222> has joined #yocto | 07:56 | |
fbre | I just wonder what actually happens in the time between the Linux kernel starts up and the time of /etc/fstab is read. Which scripts are running, where are they located? Some say there is /etc/inittab but I can't find such file in yocto Linux. I think I need to understand that boot stage at first before I try to hook a script somewhere... | 07:57 |
LetoThe2nd | init is run. and depending on which init you have, this decides what gets run in which order. | 07:57 |
fbre | I just can see /sbin/init which is a binary. What does /sbin/init do? | 07:58 |
fbre | It's a link to /lib/systemd/systemd | 08:00 |
sno | RP: when I understand your proposal correctly, it bundles both my suggestions in one commit again (as the initial proposal with a bad commit messages was). | 08:00 |
sno | I give it a shot and tell you how it behaves | 08:00 |
*** luneff <luneff!~yury@95.174.106.201> has joined #yocto | 08:00 | |
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto | 08:01 | |
LetoThe2nd | fbre: so then systemd is run and works through its units as specified. and i am very sure that there is one or more units that do the mounting. | 08:02 |
LetoThe2nd | fbre: see: https://www.freedesktop.org/software/systemd/man/systemd-fstab-generator.html | 08:02 |
*** gtristan <gtristan!~tristanva@114.207.54.105> has joined #yocto | 08:03 | |
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 08:05 | |
fbre | LetoThe2nd: cool, thanx! That's a good trace to further follow up to :] | 08:05 |
*** dev1990 <dev1990!~dev@dynamic-78-8-104-31.ssp.dialog.net.pl> has joined #yocto | 08:06 | |
*** davidinux <davidinux!~davidinux@192.145.127.172> has quit IRC | 08:10 | |
*** davidinux <davidinux!~davidinux@net-93-66-24-130.cust.vodafonedsl.it> has joined #yocto | 08:12 | |
*** luneff <luneff!~yury@95.174.106.201> has quit IRC | 08:13 | |
*** adam3371 <adam3371!~adam3371@ip5f5ac7d3.dynamic.kabel-deutschland.de> has joined #yocto | 08:19 | |
*** f843d0 <f843d0!~f843d0@213.61.153.180> has joined #yocto | 08:20 | |
f843d0 | Hello Everyone, I created a qemux86 iso image from Yocto Zeus, and I am able to boot into the system in VBox. A problem that I am facing now is that / is mounted on /dev/loop0 as ro, but I need to change settings e.g. sshd_config. Sorry maybe for noob question, but is there possibility of mounting the system in rw mode? I tried editing the cmd_line adding rw on root=/dev/ram but no success. Thanks a lot in | 08:23 |
f843d0 | advance for your kind attention | 08:23 |
LetoThe2nd | f843d0: iso images are probably ro by default, as they are supposed to end up on ro media... | 08:27 |
*** beneth <beneth!~beneth@irc.beneth.fr> has joined #yocto | 08:27 | |
LetoThe2nd | f843d0: so my guess is that iso is just not the image type that you actually want. | 08:28 |
f843d0 | LetoThe2nd: thanks, so for example for importing the solution in VBox, should I go for vmdk somehow? | 08:28 |
*** escalion <escalion!~escalion@cpc84165-pool16-2-0-cust116.15-1.cable.virginm.net> has joined #yocto | 08:29 | |
LetoThe2nd | f843d0: why "somehow"? | 08:30 |
LetoThe2nd | f843d0: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/image_types.bbclass#n287 | 08:30 |
LetoThe2nd | and why zeus? :P | 08:30 |
f843d0 | LetoThe2nd: is the stable, ain't it?! :) | 08:30 |
LetoThe2nd | f843d0: um, no? | 08:31 |
LetoThe2nd | https://www.yoctoproject.org/ | 08:31 |
f843d0 | LetoThe2nd: https://wiki.yoctoproject.org/wiki/Releases | 08:31 |
*** Jebee <Jebee!63fa1356@CPE0c9d922c2f00-CM9050ca299b20.cpe.net.cable.rogers.com> has quit IRC | 08:32 | |
LetoThe2nd | f843d0: ok, and what is saying that zeus is the latest stable there? | 08:32 |
f843d0 | LetoThe2nd: Zeus 3.0 October 2019 3.0.3 Stable 22.0.3 1.44 | 08:32 |
LetoThe2nd | Dunfell 3.1 April 2020 3.1.1 Long Term Stable | 08:33 |
LetoThe2nd | :) | 08:33 |
erbo | fbre: Have you looked at https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-features-image? I'm using raspberry pi + read-only-rootfs, and it works well. | 08:34 |
LetoThe2nd | erbo: its about the overlayfs magic (again) | 08:34 |
erbo | Ok, I figured the interest in that was in order to find a way to achieve what the magic already achieves. :) | 08:36 |
fbre | erbo: I opened your link and searched for "overlay" but there aint no such phrase | 08:36 |
erbo | fbre: the read-only-rootfs image feature will result in overlays being used, but the documentation mostly talks about the end result and doesn't go into details of how it's achieved (which is partyly using overlays) | 08:38 |
LetoThe2nd | erbo: really? (/me is not so sure about that, but would love to be proven wrong) | 08:38 |
erbo | On my rpi image built with read-only-rootfs, I have overlays for /var/spool/, /var/cache and /var/lib | 08:39 |
LetoThe2nd | erbo: really overlays, or rather just tmpfs mounts? | 08:40 |
erbo | mount shows e.g. "overlay on /home/root type overlay (rw,relatime,lowerdir=/home/root,upperdir=/var/volatile/root,workdir=/var/volatile/.root-work)" | 08:40 |
fbre | erbo: My idea is to support a factory reset which throws all done system updates over board | 08:40 |
erbo | that's an extra overlay I added for convenience | 08:41 |
fbre | erbo: therefore everything coming from an update must be in the upper overlay filesystem. | 08:41 |
LetoThe2nd | erbo: did you add that, or does meta-raspberrypi bring that? | 08:41 |
erbo | fbre: ah, so you want changes to be persistent, but in an overlay so it can be reset? | 08:41 |
erbo | LetoThe2nd: I just added the /home/root overlay, the other stuff is out-of-the-box | 08:42 |
fbre | erbo: yes, in the end I will have 2 partitions, one for each layer. The lower layer is read-only, the upper layer is read-write. The factory reset just removes the upper layer. | 08:42 |
erbo | LetoThe2nd: the volatile binds are provided by poky/meta/recipes-core/volatile-binds/volatile-binds.bb | 08:43 |
LetoThe2nd | erbo: yup, but every incarntion i've seen so far just goes for tmpfs. | 08:43 |
fbre | The use case so to speak is simply to support an easy total factory reset. | 08:44 |
erbo | LetoThe2nd: yes, it use a tmpfs in /var/volatile/ and then use overlays to put parts of the filesystem there. | 08:45 |
fbre | I think it's not enough to have overlays in a few subdirs | 08:45 |
erbo | fbre: If you look at the volatile-binds receipe, you can probably get some ideas of how you can instead achieve an overlay for the whole root | 08:45 |
fbre | erbo: ok, thanx! | 08:46 |
escalion | tmpfs with a persistent partition is the most common way I've seen to support factory reset. That and a 'recovery' partition to overwrite the primary, which IMHO is daft because wear levelling | 08:46 |
escalion | Morning all, btw | 08:47 |
LetoThe2nd | moinmoin :) | 08:49 |
*** runde <runde!sid228344@gateway/web/irccloud.com/x-qpbtxduccizykxow> has quit IRC | 08:50 | |
f843d0 | LetoThe2nd: thanks, I've created wic.vmdk and everything looks fine :) | 08:50 |
LetoThe2nd | f843d0: :) | 08:50 |
*** ustas_ <ustas_!~ustas@46.211.26.137> has joined #yocto | 08:52 | |
*** ustas <ustas!~ustas@holdings.sink.volia.net> has quit IRC | 08:53 | |
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto | 09:00 | |
*** paulbarker_tmp <paulbarker_tmp!pbarkermat@gateway/shell/matrix.org/x-wkanconmgcleqjdc> has quit IRC | 09:00 | |
*** ndec[m] <ndec[m]!ndecmatrix@gateway/shell/matrix.org/x-julfubfzblpldwzc> has quit IRC | 09:00 | |
*** Dracos-Carazza_ is now known as Dracos-Carazza | 09:01 | |
*** mbulut_ <mbulut_!~nameclash@ip1f126b1a.dynamic.kabel-deutschland.de> has joined #yocto | 09:03 | |
*** mbulut <mbulut!~nameclash@ip1f126b1a.dynamic.kabel-deutschland.de> has quit IRC | 09:04 | |
*** f843d0 <f843d0!~f843d0@213.61.153.180> has quit IRC | 09:06 | |
*** ustas_ <ustas_!~ustas@46.211.26.137> has quit IRC | 09:07 | |
*** davidinux <davidinux!~davidinux@net-93-66-24-130.cust.vodafonedsl.it> has quit IRC | 09:09 | |
*** davidinux <davidinux!~davidinux@192.145.127.172> has joined #yocto | 09:09 | |
*** f843d0 <f843d0!~f843d0@213.61.153.180> has joined #yocto | 09:13 | |
*** stacktrust <stacktrust!~stacktrus@cpe-24-90-105-219.nyc.res.rr.com> has quit IRC | 09:17 | |
*** hpsy1 <hpsy1!~hpsy@92.118.12.53> has quit IRC | 09:20 | |
*** hpsy <hpsy!~hpsy@92.118.12.53> has joined #yocto | 09:20 | |
*** ustas <ustas!~ustas@46.211.26.137> has joined #yocto | 09:21 | |
*** adam3371 <adam3371!~adam3371@ip5f5ac7d3.dynamic.kabel-deutschland.de> has quit IRC | 09:24 | |
*** adam3371 <adam3371!~adam3371@ip5f5ac7d3.dynamic.kabel-deutschland.de> has joined #yocto | 09:26 | |
*** adam3371 <adam3371!~adam3371@ip5f5ac7d3.dynamic.kabel-deutschland.de> has quit IRC | 09:33 | |
*** rcrudo <rcrudo!~rcrudo@i5387F440.versanet.de> has quit IRC | 09:33 | |
*** rcrudo <rcrudo!~rcrudo@17.120.234.35.bc.googleusercontent.com> has joined #yocto | 09:34 | |
fbre | https://superuser.com/questions/1507278/mount-overlayfs-on-before-systemd-starts is talking about an initramfs /init file. The other user found it in buildroot_directory/fs/cpio. Is there something similar in yocto? | 09:35 |
escalion | https://developer.toradex.com/knowledge-base/initramfs-and-tmpfs | 09:37 |
fbre | They write it is a script, the right place to inject the using of an overlay filesystem | 09:37 |
*** cp- <cp-!~cp-@b157153.ppp.asahi-net.or.jp> has joined #yocto | 09:37 | |
fbre | escalion: (y) | 09:38 |
escalion | tldr; you can find it in oe-core. If you are using poky you will need to check the conf to check which initramfs image it builds | 09:40 |
escalion | :) | 09:40 |
escalion | remember you can use a bbappend to add files to a package | 09:41 |
escalion | fighting a battle myself at the moment. can't get me head around how to make gstreamer1.0-gl to build from https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-multimedia/gstreamer?h=dunfell | 09:42 |
*** rcrudo <rcrudo!~rcrudo@17.120.234.35.bc.googleusercontent.com> has quit IRC | 09:44 | |
*** rcrudo <rcrudo!~rcrudo@i5387F440.versanet.de> has joined #yocto | 09:46 | |
fbre | escalion: Can you tell me the path to oe-core in the yocto/sources dir? | 09:48 |
fbre | escalion: Do you mean yocto/sources/meta-openembedded/meta-oe/recipes-core? | 09:50 |
escalion | https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-core/images/core-image-minimal-initramfs.bb?h=dunfell | 09:51 |
escalion | poky uses this one | 09:51 |
escalion | found the answer to my issue, needed to add wayland to distro_features | 09:58 |
escalion | Something so simple yet crippling xD | 09:59 |
escalion | fbre, did that help btw? | 09:59 |
escalion | or was there something more specific you was trying to achieve? | 09:59 |
fbre | escalion: I've been looking into all those files int poky/recipes-core/images at the moment. But it seems I don't find anything which has to do with a script called by initramfs init process. | 10:02 |
fbre | escalion: you know, I'm looking for a script which mounts the root filesystem. I want to change it to mount an overlay fs instead | 10:03 |
fbre | I suspect it is somewhere in the corner of files where yocto defines the initramfs init stuff | 10:04 |
escalion | you mean here? https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-core/initscripts/initscripts-1.0?h=dunfell | 10:05 |
fbre | escalion: yeah, I get the feeling I'm getting closer to it | 10:08 |
fbre | It's all very complicated and I'm drowning in the flood of scripts | 10:09 |
*** rcrudo <rcrudo!~rcrudo@i5387F440.versanet.de> has quit IRC | 10:12 | |
*** rcrudo <rcrudo!~rcrudo@139.197.242.35.bc.googleusercontent.com> has joined #yocto | 10:12 | |
escalion | break it down, its not as complicated as it looks | 10:15 |
*** sagner <sagner!~ags@2a02:169:3df5::edf> has quit IRC | 10:17 | |
RP | sno: FWIW that patch I hacked up broke all the esdks in automated testing so its not quite right | 10:18 |
*** rcrudo <rcrudo!~rcrudo@139.197.242.35.bc.googleusercontent.com> has quit IRC | 10:20 | |
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC | 10:21 | |
*** rcrudo <rcrudo!~rcrudo@i5387F440.versanet.de> has joined #yocto | 10:22 | |
fbre | What is the master script of those initrdscripts? I don't get it. Script mountall.sh looks promising but too hard to understand its content | 10:25 |
sno | RP: my test still in progress but looks good so far | 10:26 |
RP | fbre: its an init script so its installed by updated-rc.d and run through the init system | 10:28 |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 10:29 | |
fbre | Is it poky/meta/recipes-core/initrdscripts/initramfs-framework/init ? | 10:30 |
*** mbulut_ <mbulut_!~nameclash@ip1f126b1a.dynamic.kabel-deutschland.de> has quit IRC | 10:31 | |
*** pbb <pbb!~quassel@pleroma.petabyte.dev> has quit IRC | 10:32 | |
RP | fbre: more likely the main image init system would call mountall.sh | 10:32 |
RP | fbre: you have two images and two init systems, first the initramfs , then the main image | 10:32 |
*** pbb <pbb!~quassel@pleroma.petabyte.dev> has joined #yocto | 10:32 | |
*** sagner <sagner!~ags@31-10-206-124.static.upc.ch> has joined #yocto | 10:35 | |
*** rcrudo <rcrudo!~rcrudo@i5387F440.versanet.de> has quit IRC | 10:41 | |
*** rcrudo <rcrudo!~rcrudo@17.120.234.35.bc.googleusercontent.com> has joined #yocto | 10:41 | |
*** rcrudo <rcrudo!~rcrudo@17.120.234.35.bc.googleusercontent.com> has quit IRC | 10:45 | |
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto | 10:46 | |
*** malrak <malrak!50ff069b@80.255.6.155> has joined #yocto | 10:47 | |
*** rcrudo <rcrudo!~rcrudo@i5387F440.versanet.de> has joined #yocto | 10:47 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 10:56 | |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 10:58 | |
*** gtristan <gtristan!~tristanva@114.207.54.105> has quit IRC | 11:08 | |
escalion | fbre: you can add an overlay at the mountall.sh point however. Just add the declarations after line 20. Unless you need the overlay to be available in the initramfs | 11:10 |
escalion | you could also use rc system to add overlay | 11:11 |
fbre | OK, friends. Time to go home for today, thank you all very much for your hints, and have a nice weekend! | 11:13 |
*** fbre <fbre!91fdde45@145.253.222.69> has quit IRC | 11:14 | |
*** gtristan <gtristan!~tristanva@114.207.54.105> has joined #yocto | 11:18 | |
*** nslu2-log_ <nslu2-log_!~nslu2-log@milla.nas-admin.org> has joined #yocto | 11:21 | |
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC | 11:23 | |
*** nslu2-log_ is now known as nslu2-log | 11:24 | |
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-oyvnrvxjddgzcgwd> has joined #yocto | 11:26 | |
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC | 11:32 | |
*** davidinux <davidinux!~davidinux@192.145.127.172> has quit IRC | 11:36 | |
*** davidinux <davidinux!~davidinux@net-93-66-24-130.cust.vodafonedsl.it> has joined #yocto | 11:38 | |
*** gaston53 <gaston53!669cfbbb@102.156.251.187> has joined #yocto | 11:38 | |
gaston53 | does yocto support libssl ? | 11:38 |
PaowZ | gaston53: http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-connectivity/openssl/openssl_1.1.1g.bb?h=master | 11:40 |
gaston53 | PaowZ so openssl recipe will add libssl package | 11:42 |
*** berton <berton!~berton@181.220.75.161> has joined #yocto | 11:42 | |
qschulz | gaston53: yes | 11:42 |
gaston53 | qschulz just a question, can I only add libssl package without any other packages related to openssl ? | 11:43 |
sno | RP: seems because of your patch modifies OECORE_NATIVE_SYSROOT which is originally set by toolchain-scripts.bbclass | 11:44 |
qschulz | gaston53: if a package depends on another package, it'll be pulled in anyway | 11:45 |
qschulz | gaston53: so add libssl package and see what's added, maybe that's good enough. If not, either mistake in the recipe or something to tinker with | 11:45 |
gaston53 | qschulz okey thanks | 11:46 |
*** ustas <ustas!~ustas@46.211.26.137> has quit IRC | 11:48 | |
RP | sno: so it has the wrong value? | 11:50 |
* sno nods | 11:50 | |
sno | Maybe that is the conflict I dicovered - I don't really understand the entire ecosystem yet | 11:50 |
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC | 11:52 | |
*** ustas_ <ustas_!~ustas@94.153.16.84> has joined #yocto | 11:59 | |
RP | sno: I've tried another tweak in master-next | 12:02 |
malrak | Is there a way to disable the usage of bsp's *.scc files? What I would love to have is just my custom defconfig with some custom kernel fragments. Is this possible with linux-yocto-rt or do I need to create a fully custom linux-kernel recipe? | 12:03 |
RP | malrak: you should just be able to override the bsp | 12:03 |
malrak | You mean by e.g. not using core2-32-common.inc? | 12:05 |
malrak | RP: You mean by e.g. not using core2-32-common.inc? | 12:05 |
RP | malrak: I don't know. You can usually override pretty much any setting | 12:11 |
malrak | RP: so my main problem is as follows, merge_config.sh accepts my defconfig *and* my config fragments, *however* if i check the configs-variable used in ~do_kernel_configme~ it has loads of additional configurations added from all kinds of sources | 12:15 |
*** ndec is now known as ndec|away | 12:17 | |
sno | RP: https://github.com/rehsack/poky/commit/50ce74ed49a426e0e035632b9bc837f3f8b45864 is probably not that wrong | 12:19 |
RP | malrak: I think it should only touch fragments its told to. zeddii probably can point more specifically if/as/when he's around | 12:20 |
sno | RP: and the openssl / buildtools-tarball is a seond approach | 12:20 |
RP | sno: its isn't correct. buildtools just overwrites that | 12:21 |
sno | RP: yes, the openssl parts | 12:21 |
RP | sno: no, it replaces the entire environment script | 12:21 |
sno | RP: but when layers add stuff into ${D}${SDKPATHNATIVE}/... - they are kept | 12:22 |
sno | I see the files :D | 12:22 |
sno | sdk$ ls -l buildtools/sysroots/x86_64-pokysdk-linux/environment-setup.d/ | 12:23 |
sno | total 8 | 12:23 |
sno | -rw-r--r-- 1 sno sno 73 Aug 7 13:07 openssl.sh | 12:23 |
sno | -rw-r--r-- 1 sno sno 229 Aug 7 13:07 sds.sh | 12:23 |
*** jkimblad <jkimblad!~jacob@h-161-8.A137.corp.bahnhof.se> has joined #yocto | 12:24 | |
*** ericch <ericch!~ericch@pool-108-34-251-214.prvdri.fios.verizon.net> has joined #yocto | 12:25 | |
RP | sno: I mean the top level environment script you add that code to is not included in buildtools tarball. Therefore when you remove these things from buildtools-tarball, it breaks | 12:26 |
sno | RP: yes, that is true and was done to show up the conflict between the ${SDKPATHNATIVE}/environment-setup.d/*.sh and buildtools/environment-setup | 12:28 |
sno | RP: I have no sane idea to fix that and I don't knwo why there're incompatible information | 12:29 |
RP | sno: I *cannot* accept patches that break things | 12:31 |
sno | RP: I also see that cmake-nativesdk installs into a different path than openssl-nativesdk | 12:31 |
*** paulg <paulg!~paulg@198-84-145-15.cpe.teksavvy.com> has joined #yocto | 12:31 | |
sno | RP: agreed - you should not :D | 12:31 |
*** escalion_ <escalion_!~escalion@cpc84165-pool16-2-0-cust116.15-1.cable.virginm.net> has joined #yocto | 12:31 | |
sno | RP: I sent it to have a basement to discuss which of both (existing) ways is wrong | 12:32 |
sno | RP: and maybe you now see why https://github.com/rehsack/poky/commit/50ce74ed49a426e0e035632b9bc837f3f8b45864 cannot use OECORE_NATIVE_SYSROOT | 12:32 |
RP | sno: quite frankly, no :/ | 12:33 |
RP | sno: I'm doing my best to try and untangle this but I still don't understand what exactly you're really trying to fix. I am frustrated you're pushed to have patches merged which fix your use case but as known to break other things | 12:34 |
*** escalion <escalion!~escalion@cpc84165-pool16-2-0-cust116.15-1.cable.virginm.net> has quit IRC | 12:34 | |
sno | RP: that's not my intention - apologies for this | 12:35 |
*** escalion_ <escalion_!~escalion@cpc84165-pool16-2-0-cust116.15-1.cable.virginm.net> has quit IRC | 12:36 | |
*** gtristan <gtristan!~tristanva@114.207.54.105> has quit IRC | 12:37 | |
*** kroon <kroon!~kroon@213.185.29.22> has quit IRC | 12:38 | |
*** gaston53 <gaston53!669cfbbb@102.156.251.187> has quit IRC | 12:41 | |
sno | RP: I try to explain better ... give me a few minutes (I try to figure out what is the right way) | 12:43 |
sno | RP: cmake installs nativesdk related files into ${SDKPATHNATIVE}/environment-setup.d via https://github.com/rehsack/poky/blob/master/meta/recipes-devtools/cmake/cmake_3.17.3.bb#L39-L45 | 12:43 |
sno | RP: cmake-native install into ${D}${base_prefix}/environment-setup.d/cmake.sh via https://github.com/rehsack/poky/blob/master/meta/recipes-devtools/cmake/cmake-native_3.17.3.bb#L48 | 12:43 |
sno | RP: openssl-nativesdk does it similar to cmake-nativesdk -- but only the one of cmake-native is included in the script generated by toolchain-scripts.bbclass | 12:43 |
sno | RP: all I want is to understand how it is meant to add files to sdk to configure for local enhancements | 12:43 |
sno | RP: So please apologize the patches felt being pushed (harder) - that wasn't intentional | 12:44 |
RP | sno: I don't really understand why we'd have a cmake-native environment-setup.d :( | 12:47 |
sno | RP: precisely - me neither | 12:47 |
sno | RP: I understand that the patch breaks things and I'm interested in fixing it - not getting it pushed | 12:48 |
RP | sno: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=b92717ae485dcde5aa0f477d1e5fcc3205ed7a23 | 12:48 |
RP | sno: which SDKMACHINE are you using? | 12:49 |
sno | RP: unfortunately this doesn't explain why only `$OECORE_TARGET_SYSROOT/environment-setup.d/*.sh` and `$OECORE_NATIVE_SYSROOT/environment-setup.d/*.sh` are sourced but not those which are installed in ${SDKPATHNATIVE}/environment-setup.d | 12:50 |
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto | 12:52 | |
sno | RP: SDKMACHINE=x86_64 | 12:52 |
malrak | RP: I think I found my error. I had SRC_URI += and not SRC_URI_append. Now with SRC_URI_append it only pulls in my configs | 12:53 |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 12:55 | |
*** mattsm <mattsm!~mattsm@76-205-175-243.lightspeed.austtx.sbcglobal.net> has quit IRC | 12:56 | |
*** maudat <maudat!~moda@bras-vprn-mtrlpq2848w-lp130-10-174-92-198-55.dsl.bell.ca> has joined #yocto | 12:58 | |
*** tgamblin <tgamblin!~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com> has quit IRC | 13:04 | |
*** tgamblin <tgamblin!~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com> has joined #yocto | 13:05 | |
sno | RP: is my confusion a bit clearer to you? | 13:06 |
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/kiwiirc.com/ip.208.88.110.46> has quit IRC | 13:06 | |
RP | sno: yes, a little. I think we perhaps start by deleting the cmake-native sdk bits... | 13:08 |
sno | RP: :D | 13:08 |
sno | RP: all I'm trying to figure out is: where do I have to add enhancements to get them used by eSDK - and it seems it's `${D}${base_prefix}/environment-setup.d/` - and maybe in a later stage openssl-nativesdk sould be fixed, too | 13:10 |
RP | sno: so you're trying to use this in the eSDK? | 13:12 |
sno | RP: yes, I'm trying to use this in eSDK | 13:13 |
sno | RP: to be more clear - I'm trying to add a script which exports a new shell variable which easy allows doing developer builds using the eSDK and later using devtool for integration steps | 13:14 |
RP | sno: so there is something wrong with the eSDK environment. I then wonder why all the eSDK tests pass :/ | 13:15 |
*** mattsm <mattsm!~mattsm@76-205-175-243.lightspeed.austtx.sbcglobal.net> has joined #yocto | 13:15 | |
sno | RP: maybe it's not used much ¯\_(ツ)_/¯ | 13:16 |
sno | RP: it was very difficult to find examples :) | 13:16 |
RP | sno: but we do have tests which we run regularly | 13:18 |
sno | RP: but what do they expose into the environment-setup.d/*.sh ? | 13:18 |
sno | it's only that - everything else seems to be very sane | 13:18 |
RP | so it suggests we have a gap in the testing. I'd be a lot happier if I could show problems in the tests | 13:18 |
sno | RP: I fully agree - but I do not understand the issue enough to create a sane test for that | 13:19 |
*** matthewzmd <matthewzmd!~user@216-58-109-18.cpe.distributel.net> has joined #yocto | 13:19 | |
*** malrak <malrak!50ff069b@80.255.6.155> has left #yocto | 13:20 | |
sno | RP: is there someone else beside you who can ''guide'' me to create such a test? moto-timo maybe? | 13:28 |
*** hpsy <hpsy!~hpsy@92.118.12.53> has quit IRC | 13:30 | |
*** hpsy <hpsy!~hpsy@92.118.12.53> has joined #yocto | 13:30 | |
RP | sno: esdk experts are bluelightning and myself. A few people could probably help with sdk tests but I don't know who if anyone has time | 13:40 |
sno | RP: when you know that someone has a tuit, please remind this issue | 13:45 |
RP | sno: I am looking at it locally a little more | 13:46 |
sno | RP: thanks | 13:46 |
*** ustas <ustas!~ustas@46.211.79.154> has joined #yocto | 13:48 | |
*** ustas_ <ustas_!~ustas@94.153.16.84> has quit IRC | 13:48 | |
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/kiwiirc.com/ip.208.88.110.46> has joined #yocto | 14:03 | |
f843d0 | Hello Everyone, I was able to set the IMAGE_ROOTFS_SIZE to control /. But for /boot, currently I manually modified poky/scripts/lib/wic/canned-wks/common.wks.inc adding --size to the part directive. Is there a more elegant way to achieve this, maybe via some other *.conf directive? | 14:03 |
*** WillMiles <WillMiles!~Will@209.87.231.80> has joined #yocto | 14:16 | |
RP | sno: I do now understand what you mean about all this. I am however struggling to see the correct way to fix it | 14:19 |
*** PaowZ_ <PaowZ_!~Vince@193.252.149.222> has quit IRC | 14:26 | |
*** PaowZ_ <PaowZ_!~Vince@193.252.149.222> has joined #yocto | 14:26 | |
*** Konsgnx <Konsgnx!~Konsgnx3@66-109-34-138.tvc-ip.com> has joined #yocto | 14:36 | |
*** rcw <rcw!~rcw@45.72.241.84> has joined #yocto | 14:40 | |
sno | RP: no worries - that's all I wanted to reach at the first step and still apologizing for how I did it | 14:41 |
*** ibinderwolf <ibinderwolf!~quassel@etrn.topcontrol.it> has quit IRC | 14:45 | |
RP | sno: np. The issue is that we're mixing native and nativesdk recipes and they don't look to co-exist well. I don't really want people to have to write relocation code twice | 14:47 |
*** sukbeom <sukbeom!~sukbeom@211.222.84.48> has joined #yocto | 14:50 | |
*** matthewzmd <matthewzmd!~user@216-58-109-18.cpe.distributel.net> has quit IRC | 15:01 | |
*** matthewzmd <matthewzmd!~user@216-58-109-18.cpe.distributel.net> has joined #yocto | 15:01 | |
*** escalion <escalion!~escalion@cpc84165-pool16-2-0-cust116.15-1.cable.virginm.net> has joined #yocto | 15:02 | |
RP | sno: basically my conclusion is you may need to add environment-setup to -natives for eSDK and to -nativesdk for SDK | 15:05 |
RP | The code is sourcing the right things but buildtools does need improving to use these scripts in a way which doesn't break eSDK | 15:06 |
sno | RP: I give it a try and will report | 15:09 |
RP | sno: I've written up a summary of what I found and sent to the list | 15:18 |
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/kiwiirc.com/ip.208.88.110.46> has quit IRC | 15:18 | |
sno | RP: cool, thanks | 15:18 |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 15:23 | |
*** sgw1 <sgw1!~swold@c-71-238-119-71.hsd1.or.comcast.net> has joined #yocto | 15:36 | |
*** pbb <pbb!~quassel@pleroma.petabyte.dev> has quit IRC | 15:44 | |
*** gtristan <gtristan!~tristanva@175.211.69.194> has joined #yocto | 15:45 | |
*** davidinux <davidinux!~davidinux@net-93-66-24-130.cust.vodafonedsl.it> has quit IRC | 15:47 | |
*** pbb <pbb!~quassel@pleroma.petabyte.dev> has joined #yocto | 15:49 | |
*** davidinux <davidinux!~davidinux@net-93-66-24-130.cust.vodafonedsl.it> has joined #yocto | 15:49 | |
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto | 15:53 | |
*** davidinux <davidinux!~davidinux@net-93-66-24-130.cust.vodafonedsl.it> has quit IRC | 15:54 | |
*** davidinux <davidinux!~davidinux@192.145.127.172> has joined #yocto | 15:54 | |
*** f843d0 <f843d0!~f843d0@213.61.153.180> has quit IRC | 15:56 | |
kergoth | huh, that's not great.. found an archiver issue. it disables inclusion of the gcc recipes in favor of gcc-source, which is great for the source, but means that ARCHIVER_MODE[dumpdata] and ARCHIVER_MODE[recipe] don't actually work for the gcc recipes. only the gcc-source recipe/data is emitted | 16:05 |
kergoth | thats fine if you're only emitting the data for info on source construction, but not if you're trying to comply with emission of 'build instructions' | 16:06 |
kergoth | not sure if i need to do that anyway, but it's a clear bug. i'll open an issue | 16:07 |
kergoth | also looks like libtool-cross and qemuwrapper-cross don't actually inherit cross, so aren't excluded by removing cross from COPYLEFT_RECIPE_TYPES | 16:08 |
RP | kergoth: cross doesn't actually work for anything not gnu :( | 16:09 |
*** mckoan is now known as mckoan|away | 16:09 | |
RP | kergoth: it really should be called cross-gnu or something | 16:09 |
kergoth | ah, do other buildsystems expect CC, etc to correspond to the target, not build machine in a cross configuration, and rely on BUILD_ or _FOR_CROSS style build machine tooling variables? | 16:11 |
kergoth | makes sense | 16:11 |
kergoth | if that's the case it'd probably be worth splitting the class up. rename the autotools-specific portion and retain a common core | 16:12 |
*** fl0v0 <fl0v0!~fvo@i59F44C21.versanet.de> has quit IRC | 16:14 | |
*** meow` <meow`!~sbourdeli@192.222.239.49> has joined #yocto | 16:15 | |
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/irccloud.com/x-xhnvvofqgmizawiw> has quit IRC | 16:20 | |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 16:37 | |
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 16:38 | |
*** rob_gries <rob_gries!~rob@96.72.222.9> has joined #yocto | 16:40 | |
rob_gries | What is the best way to install a "-dev" package into an image? I know that IMAGE_INSTALL+= " somepackage-dev" might not be allowed according to the documentation. Basically, I want a developer package to be added to my system image so that I can build and test software linking a specific library on a device. | 16:43 |
*** sukbeom <sukbeom!~sukbeom@211.222.84.48> has quit IRC | 16:45 | |
RP | kergoth: I don't remember the issue, I know I found it much safer to not use it for anything that wasn't binutils/gcc/gdb | 16:48 |
*** ustas <ustas!~ustas@46.211.79.154> has quit IRC | 16:49 | |
*** dev1990 <dev1990!~dev@dynamic-78-8-104-31.ssp.dialog.net.pl> has quit IRC | 16:50 | |
*** kaspter <kaspter!~Instantbi@112.64.53.132> has joined #yocto | 16:53 | |
*** ustas_ <ustas_!~ustas@46.211.51.59> has joined #yocto | 16:55 | |
*** escalion <escalion!~escalion@cpc84165-pool16-2-0-cust116.15-1.cable.virginm.net> has quit IRC | 16:57 | |
*** sagner <sagner!~ags@31-10-206-124.static.upc.ch> has quit IRC | 17:07 | |
*** vineela <vineela!vtummala@nat/intel/x-hajunlbucbnlwrtq> has joined #yocto | 17:19 | |
*** mattsm <mattsm!~mattsm@76-205-175-243.lightspeed.austtx.sbcglobal.net> has quit IRC | 17:22 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 17:26 | |
*** mattsm <mattsm!~mattsm@76-205-175-243.lightspeed.austtx.sbcglobal.net> has joined #yocto | 17:26 | |
*** rcrudo <rcrudo!~rcrudo@i5387F440.versanet.de> has quit IRC | 17:27 | |
tlwoerner | i need to use a native objcopy as part of the commands used to create my own image type | 17:43 |
tlwoerner | objcopy comes from binutils | 17:43 |
tlwoerner | but the binutils recipe explicitly deletes the ${bindir} when doing a do_install_class-native | 17:43 |
RP | tlwoerner: those are assumed to come from the host | 17:44 |
RP | although perhaps little uses objcopy | 17:44 |
tlwoerner | RP: oh, okay. sounds good | 17:44 |
RP | tlwoerner: binutils-native is mainly for libbfd-native | 17:44 |
RP | sno: I think I have a patch which at least might improve some of this mess... | 17:47 |
tlwoerner | in my custom image bbclass, is there no easy way to add my artifact to the list of files that are removed during do_clean? | 18:01 |
tlwoerner | there is: do_image_<myimage>[cleandirs] but no do_image_<myimage>[cleanfile] | 18:02 |
tlwoerner | i guess i'll just do a do_clean_append(){}? | 18:03 |
RP | tlwoerner: shouldn't you be installing it via the deploydir mechanism and hence it could be autocleaned? | 18:05 |
tlwoerner | RP: ah, so no manipulating files in ${DEPLOY_DIR_IMAGE} directly then? ;-) | 18:08 |
RP | tlwoerner: not recommended | 18:08 |
*** sukbeom <sukbeom!~sukbeom@211.222.84.48> has joined #yocto | 18:09 | |
sno | RP: cool | 18:11 |
tlwoerner | RP: hmm, the IMAGEDEPLOYDIR doesn't include the kernel, which i need for my custom blob, but i can get that from ${DEPLOY_DIR_IMAGE} i guess | 18:12 |
RP | tlwoerner: its fine to consume from DEPLOY_DIR_IMAGE, just don't write to it | 18:13 |
*** sukbeom <sukbeom!~sukbeom@211.222.84.48> has quit IRC | 18:13 | |
tlwoerner | RP: perfect! thanks :-) | 18:14 |
*** stacktrust <stacktrust!~stacktrus@cpe-24-90-105-219.nyc.res.rr.com> has joined #yocto | 18:16 | |
*** ustas_ <ustas_!~ustas@46.211.51.59> has quit IRC | 18:20 | |
JPEW | RP: Ah, OK. That explaination of the perl bug makes more sense. It's also easier to test for :) | 18:24 |
RP | JPEW: sorry about the confusion! | 18:24 |
JPEW | RP: No problem; did you have a build where it was in the non-arch directory? | 18:24 |
zeddii | aha. nice, my .config analysis enhancement is already getting me fixup patches :D | 18:25 |
RP | JPEW: no, that is the build I've never found :/ | 18:25 |
*** sukbeom <sukbeom!~sukbeom@211.222.84.48> has joined #yocto | 18:25 | |
JPEW | RP: Got it | 18:25 |
*** ustas <ustas!~ustas@18-129-132-95.pool.ukrtel.net> has joined #yocto | 18:26 | |
*** sukbeom <sukbeom!~sukbeom@211.222.84.48> has quit IRC | 18:32 | |
*** gsalazar <gsalazar!5e3ce511@gateway/web/cgi-irc/kiwiirc.com/ip.94.60.229.17> has quit IRC | 18:35 | |
*** Jebee <Jebee!63fa1356@CPE0c9d922c2f00-CM9050ca299b20.cpe.net.cable.rogers.com> has joined #yocto | 18:40 | |
*** sukbeom <sukbeom!~sukbeom@211.222.84.48> has joined #yocto | 18:42 | |
Jebee | Im adding a patch to a bitbake recipe for the kernel, the patch fails to apply and then every subsequent build bitbake says it founds a fence post and is continuing after my patch. How can I force it to actually try and apply the patch each time? | 18:42 |
Jebee | Or at least clean everything all the way so that it will attempt it again. | 18:42 |
Jebee | I have tried a complete clean and rebuild and it does not help, the only thing that will let me retry is if i clone the whole repo, make changes and restart the build. This is quite time consuming. | 18:43 |
zeddii | fence post ? you are on a really old release then. I abandoned that code due to complexity. | 18:43 |
Jebee | It is a build that i received from a vendor for their parts. It is based on thud | 18:43 |
Jebee | Latest patch was Feb 26 2019 ship /etc/drirc in mesa-megadriver | 18:44 |
Jebee | Is there a way to clear these "fence posts"? a folder or file that is stored somewhere? | 18:46 |
zeddii | it's in the kernel source's .git directory, but even though I wrote all that code, I'd have to go look up exactly what it is. | 18:46 |
*** sukbeom <sukbeom!~sukbeom@211.222.84.48> has quit IRC | 18:47 | |
zeddii | actually, if it is looking for fence posts. It should be thud. I just checked and had already removed htat. | 18:47 |
zeddii | s/should/shouldn't/ | 18:47 |
*** berton <berton!~berton@181.220.75.161> has quit IRC | 18:48 | |
Jebee | Whats a good way to check exactly which build / rev I'm using? | 18:48 |
*** berton <berton!~berton@181.220.75.161> has joined #yocto | 18:49 | |
zeddii | sec. I'm checking. I see some remnant code. so it could be thud. there were some transition releases. but they all blur together. | 18:49 |
champagneg | any hints on removing the dependency from do_populate_sysroot tasks to do_install_ptest_base? If I modify a ptest in recipe A and recipe B depends on A, I think recipe B do_compile gets executed because of this dependency. Concrete example is between qtbase and systemd, so triggering a qtbase build is annoying ;p | 18:50 |
zeddii | yah. wow. that's some transition code that I didn't even write. It is checking the name of your patch and comparing it to the internal patch series. if there's a match, it takes that as the fence post. | 18:53 |
Jebee | Hrmm, its strange because it seems to set that post even if the patching fails. | 18:54 |
Jebee | Do you have any suggestions on a good candidate to rebase to? I wouldn't mind trying to upgrade this to a proper stable release (I'm having all sorts of SSTATE_CACHE issues as well which i believe are fixed in newer releases). | 18:57 |
zeddii | dunfell (the latest release), is a good candidate. since it is LTS as well. | 18:57 |
zeddii | Jebee: I don't suppose the layers / kernel for this are public ? I could run a couple of quick tests if they were. | 18:58 |
zeddii | or pastebin the error message and I can look for more details. | 18:59 |
Jebee | @zeddii unfortunately it isnt... and its a complete mess, this particular vendor has completely mangled this entire code base. I tried to rebase it just to the latest release of thud and that cause a ton of issues. | 19:00 |
Jebee | I'm trying the rebuild currently. I'll pastebin the error as soon as I can get it to come up again. | 19:00 |
zeddii | cool. I can very likely get you moving. I'll just have to swap some things back into my memory :D | 19:00 |
*** Jebee_laptop <Jebee_laptop!a5e1d0b2@165.225.208.178> has joined #yocto | 19:06 | |
Jebee | ha, even deleting the whole kernel folder and did a repo sync again, and it still skipped it due to the fence post being found. | 19:08 |
Jebee_laptop | https://pastebin.com/iPb7hYMX | 19:08 |
zeddii | detached head ? ouch. they are doing strange things. | 19:18 |
zeddii | if you can locate your kernel source directory for the build (build/tmp/work-shared/$MACHINE/kernel-source (at least, that's where it is now, I can't remember if we had work-shared in thud, but we should have). | 19:19 |
zeddii | then look in the .git/ directory | 19:19 |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 19:23 | |
Jebee | So the .git directory is there. | 19:27 |
zeddii | is kgit-s2q.last there ? it pretty much has to be, since that is what dumps the message you are seeing. | 19:28 |
Jebee_laptop | Here is a pastebin of when patch actually fails. | 19:29 |
Jebee_laptop | https://pastebin.com/1nBh5pZq | 19:29 |
zeddii | so the patch isn't right for that kernel. but that isn't one of your patches from the SRC_URI ? | 19:30 |
Jebee | that is a patch that i need to include for the kernel being built, Ive created a recipe with a bbappend file that has a SRC_URI append, and a FILESEXTRAPATHS_prepend. | 19:31 |
zeddii | ok, cool, but it isn't valid for where it is being applied, so you need to fixup the patch itself. | 19:32 |
Jebee | Right, I was thinking of modifying the source directory in the do_patch_prepend, and then setting it back in the do_patch_append. | 19:33 |
Jebee | would that work, without having to touch the patch? | 19:33 |
zeddii | you've got some bad paths in the patch, for the actual files being patched: | 19:33 |
zeddii | build/tmp-glibc/work-shared/wnc/kernel-source/ | 19:33 |
zeddii | that shouldn't be there, if its in the patch. | 19:33 |
zeddii | doing a dance with the source directory, I'm not so sure it'd work out. | 19:34 |
Jebee | so the way the vendor delivered this patch is that they just took a diff of the whole folder that is ../ from poky, which includes many module diffs. (seems like a terrible way to send a patch for a system like this) | 19:37 |
Jebee | I need to figure out why my root kernel directory differs from the one that is in wnc/kernel-source/ | 19:39 |
zeddii | your build is using the right directory. | 19:40 |
zeddii | it's the patch that is garbage (to be blunt). | 19:40 |
zeddii | unless I'm misreading it, that's a completely invalid file path specification. | 19:40 |
*** nslu2-log <nslu2-log!~nslu2-log@milla.nas-admin.org> has quit IRC | 19:40 | |
zeddii | and luckily, it isn't my older tools that are the problem. I'm glad about that at least. | 19:41 |
Jebee | I think the real overall question is, (you're correct about the patch being absolute trash), is why am unable to force it to try to reapply the patch on subsequent builds. And thats why you were asking me to check for that kgit-s2q.last file. So let me do that right now. | 19:42 |
*** WillMiles <WillMiles!~Will@209.87.231.80> has quit IRC | 19:42 | |
zeddii | yes. when it sees that file, it knows that's where it left off. | 19:43 |
zeddii | if you remove it, it'll start over. | 19:43 |
Jebee | deleting the entire tmp-glibc/* contents should have the same effect correct? | 19:43 |
zeddii | if the kernel-source directory is in there, then yep. the only place that message you are seeing comes from is the line that detects that file. | 19:45 |
*** hpsy1 <hpsy1!~hpsy@92.118.12.31> has joined #yocto | 19:50 | |
*** hpsy <hpsy!~hpsy@92.118.12.53> has quit IRC | 19:51 | |
*** dreyna_ <dreyna_!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto | 19:52 | |
*** Jebee_laptop <Jebee_laptop!a5e1d0b2@165.225.208.178> has quit IRC | 19:54 | |
*** dreyna_ <dreyna_!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC | 19:56 | |
*** dreyna_ <dreyna_!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto | 19:56 | |
Jebee | So there is no kgit-s2q file in the kernel-source folder. | 20:02 |
zeddii | that is what is doing the patching, it's a tool. the file it is checking is kernel-source/.git/kgit-s2q.last | 20:03 |
Jebee | right, understood. I just mean there is nothing in that folder with the name kgit-sq2* , let me double check. | 20:07 |
zeddii | there's no other way that message can come out. | 20:07 |
zeddii | so without being able to run something here, there's nothing more I can easily suggest. | 20:07 |
*** ustas_ <ustas_!~ustas@46.211.45.179> has joined #yocto | 20:14 | |
Jebee | Thanks zeddii, ill keep poking around, you've been a huge help | 20:14 |
*** ustas <ustas!~ustas@18-129-132-95.pool.ukrtel.net> has quit IRC | 20:15 | |
rob_gries | Does anyone have any helpful workarounds for someone who is getting loads of "Multilib check error" messages when including -dev packages? I'm using this crappy BSP put together by Qualcomm that has been messed with by who knows how many vendors. All I want to do is just link and build with gstreamer natively. | 20:16 |
Jebee | hi rob :) i'm using the same or a very similar bsp put together by the exact same vendor :) | 20:18 |
rob_gries | Do you happen to be using the APQ8053 as well? | 20:19 |
Jebee | No, I'm using a SA2150 AP and a SA415M modem. | 20:20 |
rob_gries | I swear QCOM makes this stuff harder than it needs to be... I've used Linaro's RPB BSP previously and that was a dream compared to this pile of junk that Qualcomm ships. | 20:21 |
RP | rob_gries: having heard about some of what they do, I'd agree with that :/ | 20:21 |
Jebee | Its just awful, and the support is even worse. | 20:21 |
RP | can you turn off multilibs? | 20:21 |
rob_gries | RP: I can if I can solely use lib32 binaries. Some of Qualcomm's proprietary bits only work properly when built in 32Bit. | 20:23 |
RP | rob_gries: I can see that being trickier to arrange | 20:24 |
RP | rob_gries: just thought I'd mention just in case | 20:24 |
rob_gries | RP: I was afraid you'd say that! Do you have tips on how to configure that? The last BSP I used was 64Bit only I haven't run into this before... | 20:25 |
*** maudat <maudat!~moda@bras-vprn-mtrlpq2848w-lp130-10-174-92-198-55.dsl.bell.ca> has quit IRC | 20:27 | |
Jebee | rob_gries how are you including the -dev libs? is your goal to have them in the SDK ? | 20:27 |
rob_gries | Jebee: So far I've tried two methods -- modifying meta-qti-bsp/recipes-products/images/apq8053/apq8053-base-image.inc and adding IMAGE_INSTALL directives for the packages of my choice. The second method I've tried was to modify local.conf and add the IMAGE_INSTALL_append directive that includes the packages of my choice. | 20:30 |
rob_gries | Jebee: I want to include them into the image so that the developers on my team can build on the devkits that they are using. My teammates like that scheme better and generally shy away from setting up a cross-compiler on their systems. | 20:31 |
Jebee | hrmm, and neither of those methods work as you expect? | 20:32 |
RP | rob_gries: I can't see an easy way to do it. If it was turning off lib32 and just leaving the "standard" ones it would be much easier | 20:34 |
*** ustas_ <ustas_!~ustas@46.211.45.179> has quit IRC | 20:34 | |
RP | rob_gries: I was wondering if you could just blacklist the problematic dev packages somehow too | 20:34 |
Jebee | zeddii: I found it, its in poky/.git/kgit-s2q.last | 20:35 |
Jebee | thanks!! | 20:35 |
rob_gries | Jebee: Unfortunately no. Method one (apq8053-base-image.inc) results in an image that cannot find it's firmware blobs when it boots, even though I never touched that part of the BSP. Method two (local.conf) results in multilib check errors and failed builds. | 20:35 |
rob_gries | RP: that would be fantastic. however wouldn't that result in both lib32 and standard versions being blacklisted? | 20:36 |
Jebee | just to double check you used IMAGE_INSTALL_append = " package-dev"? (with the space before the name of the dev package? I assume you did, good to check tho. | 20:38 |
Jebee | in the local.conf file? | 20:38 |
RP | rob_gries: they have separate -dev package names don't they? | 20:39 |
rob_gries | Jebee: Yes | 20:40 |
rob_gries | RP: Also, yes | 20:40 |
*** ustas <ustas!~ustas@holdings.sink.volia.net> has joined #yocto | 20:42 | |
rob_gries | RP: I'm trying the blacklist approach | 20:45 |
rob_gries | RP: Following this from the manual -- https://www.yoctoproject.org/docs/1.7/ref-manual/ref-manual.html#var-PNBLACKLIST | 20:45 |
rob_gries | RP: I'm building with the PNBLACKLIST variables set... Fingers crossed! | 20:49 |
JPEW | Is there any reason dbus is 1.12.x when 1.13.x has been released? | 20:58 |
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC | 20:59 | |
rob_gries | RP: Dang. That didn't work. If you're interested here are my build logs and my blacklist snippet from local.conf -- https://gist.github.com/RobGries/07bd366f4b021143c1f18d6c942a0da8 | 21:01 |
JPEW | Ah, odd-even releases | 21:03 |
RP | rob_gries: you'd need to do it at the package level, not PN | 21:03 |
*** Konsgnx <Konsgnx!~Konsgnx3@66-109-34-138.tvc-ip.com> has quit IRC | 21:05 | |
rob_gries | RP: Hmm never did that before. So forgive me if I sound stupid. Would that just be BLACKLIST[gstreamer-1.0-dev]? Or would I have to go into each recipe and add that syntax? | 21:07 |
*** agust <agust!~agust@p508b628a.dip0.t-ipconnect.de> has quit IRC | 21:08 | |
RP | rob_gries: I don't think its easy to do. If it were me, I'd hack the install_complementary() function in meta/lib/oe/package_manager.py just to skip the ones you don't want | 21:11 |
RP | rob_gries: ah, PACKAGE_EXCLUDE_COMPLEMENTARY | 21:12 |
RP | rob_gries: try that :) | 21:12 |
rob_gries | RP: I'll give it a shot :) That's in Jethro, right? | 21:15 |
RP | rob_gries: er, no idea. That is rather elderly | 21:15 |
rob_gries | RP: Yeah... This is what the vendor give us :-/ | 21:16 |
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has quit IRC | 21:19 | |
RP | rob_gries: how old is that hardware? | 21:19 |
Jebee | So if I wanted to patch something that is in the root directory, lets say something in kernel/*/sound... where would I ideally create the diff for the patch such that i could include it in a bbappend file with SRC_URI? | 21:19 |
rob_gries | RP: Not that old... maybe 2 years old? https://www.qualcomm.com/media/documents/files/apq8053-soc-product-brief.pdf | 21:20 |
RP | rob_gries: based on a release series we stopped updating in Dec 2016 :/ | 21:21 |
rob_gries | RP: I have a suspicion that QCOM flogs it's older mobile targeted silicon to IoT when it stops being profitable. | 21:22 |
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has joined #yocto | 21:22 | |
RP | rob_gries: sounds possible | 21:26 |
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC | 21:28 | |
rob_gries | RP: so I checked over the install_complementary() function in my version of the BSP, and found that PACKAGE_EXCLUDE_COMPLEMENTARY is in fact in there. But I'm not sure if I'm using it correctly. | 21:42 |
rob_gries | RP: this is what I tried in local.conf -- PACKAGE_EXCLUDE_COMPLEMENTARY += " gstreamer-1.0-dev libpng-dev libdb-dev libgmp-dev" | 21:43 |
RP | rob_gries: sounds right. There are a lot of ways this might not work unfortunately :( | 21:46 |
RP | rob_gries: Its 11pm on a Friday here and I really need to step away from the computer, sorry | 21:47 |
rob_gries | RP: I get it, it's nearly 6PM here. Thanks for your help, I appreciate it. | 21:48 |
rob_gries | RP: Enjoy your weekend! | 21:48 |
khem | RP: finally fixed the ppc issue I am hoping, please stage the patch I sent moments ago | 22:21 |
khem | RP: I think we should drop this ppc32 !@#$ from core | 22:22 |
RP | khem: already running on the autobuilder :) | 22:22 |
khem | I spend 2.5 days debugging this issue | 22:22 |
RP | khem: thanks, I know the feeling with things like that... | 22:22 |
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has quit IRC | 22:23 | |
RP | khem: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1241 | 22:23 |
khem | glibc got many changes where things broke so bisecting was not an option | 22:23 |
khem | and upstream only cares for ibm ppc | 22:24 |
RP | khem: ouch. Sounds like it may be an interesting one for issues as it gets wider testing... | 22:24 |
khem | RP: perhaps we should think of replacing it with ppc64 and ask openpower to support us | 22:25 |
* RP really steps away | 22:25 | |
RP | khem: I'd be fine with that but doesn't cisco use the older ppc? | 22:25 |
khem | yeah they do anyone from Cisco here listening ? please share the pain | 22:26 |
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has joined #yocto | 22:26 | |
RP | khem: victor is helpful if you email him | 22:26 |
khem | good idea, I will | 22:26 |
khem | since ppc always eats up time along with mips sometimes but mips I get paid for :) | 22:27 |
*** matthewzmd <matthewzmd!~user@216-58-109-18.cpe.distributel.net> has quit IRC | 22:33 | |
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto | 22:38 | |
armpit | you get paid? | 22:38 |
armpit | we should drop ppc32 for ppc64 ; ) | 22:39 |
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC | 22:49 | |
*** camus1 <camus1!~Instantbi@112.64.53.132> has joined #yocto | 22:52 | |
*** kaspter <kaspter!~Instantbi@112.64.53.132> has quit IRC | 22:54 | |
*** camus1 is now known as kaspter | 22:54 | |
*** vineela <vineela!vtummala@nat/intel/x-hajunlbucbnlwrtq> has quit IRC | 23:03 | |
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto | 23:03 | |
khem | armpit: heh I mean my employer still uses mips32 so indirectly, I am scratching own itch with mips32 | 23:04 |
*** MiskaX <MiskaX!v0liw25rff@2001:2060:72::3> has quit IRC | 23:20 | |
*** MiskaX <MiskaX!gg1nw2etqp@rankki.sonarnerd.net> has joined #yocto | 23:27 | |
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC | 23:32 | |
*** ericch <ericch!~ericch@pool-108-34-251-214.prvdri.fios.verizon.net> has quit IRC | 23:33 | |
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC | 23:33 | |
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto | 23:37 | |
*** rcw <rcw!~rcw@45.72.241.84> has quit IRC | 23:44 | |
*** ustas <ustas!~ustas@holdings.sink.volia.net> has quit IRC | 23:47 | |
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC | 23:50 | |
*** comptroller <comptroller!~comptroll@47-213-220-127.paolcmtc01.res.dyn.suddenlink.net> has quit IRC | 23:51 | |
*** NiksDev <NiksDev!~NiksDev@192.91.75.30> has quit IRC | 23:59 | |
*** comptroller <comptroller!~comptroll@47-213-220-127.paolcmtc01.res.dyn.suddenlink.net> has joined #yocto | 23:59 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!