| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has joined #yocto | 00:01 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has quit IRC | 00:07 | |
| *** itseris <itseris!~emikulin@76.77.65.2> has quit IRC | 00:09 | |
| *** fischerm <fischerm!~mfischer@207-114-172-147.static.twtelecom.net> has quit IRC | 00:15 | |
| *** fischerm <fischerm!~mfischer@207-114-172-147.static.twtelecom.net> has joined #yocto | 00:17 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has joined #yocto | 00:23 | |
| *** joshuagl <joshuagl!~joshuagl@192.198.151.45> has quit IRC | 00:26 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has quit IRC | 00:27 | |
| *** nighty-- <nighty--!~nighty@d246113.ppp.asahi-net.or.jp> has joined #yocto | 00:30 | |
| *** JordonWu <JordonWu!~quassel@221.226.9.57> has joined #yocto | 00:34 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has joined #yocto | 00:41 | |
| *** dscully <dscully!~dscully@24.249.154.174> has quit IRC | 00:41 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has quit IRC | 00:45 | |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC | 00:52 | |
| *** blueness <blueness!~blueness@cpe-67-247-195-186.buffalo.res.rr.com> has joined #yocto | 00:53 | |
| *** dvhart <dvhart!~dvhart@static-50-53-109-124.bvtn.or.frontiernet.net> has joined #yocto | 00:54 | |
| *** blueness <blueness!~blueness@cpe-67-247-195-186.buffalo.res.rr.com> has quit IRC | 00:54 | |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto | 00:54 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has joined #yocto | 01:00 | |
| *** msvb-lab <msvb-lab!~michael@x55b540b0.dyn.telefonica.de> has quit IRC | 01:04 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has quit IRC | 01:05 | |
| *** jairglez <jairglez!~jairdeje@134.134.139.76> has quit IRC | 01:08 | |
| *** msvb-lab <msvb-lab!~michael@x55b540ac.dyn.telefonica.de> has joined #yocto | 01:16 | |
| *** vmeson <vmeson!~rmacleod@192-0-133-4.cpe.teksavvy.com> has joined #yocto | 01:28 | |
| *** dengke <dengke!~dengke@106.120.101.38> has joined #yocto | 01:34 | |
| *** black_13 <black_13!48b62bb7@gateway/web/freenode/ip.72.182.43.183> has joined #yocto | 02:03 | |
| black_13 | when you build the qemu image where does the created image reside | 02:03 |
|---|---|---|
| kergoth | tmp*/deploy/images/, same as for any machine. see also the docs at yoctoproject.org | 02:09 |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has joined #yocto | 02:16 | |
| *** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has quit IRC | 02:18 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has quit IRC | 02:22 | |
| *** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has joined #yocto | 02:25 | |
| black_13 | can that be configured in the conf file? | 02:25 |
| kergoth | see DEPLOY_DIR and DEPLOY_DIR_IMAGE | 02:28 |
| *** bananadev <bananadev!~onlyester@117.6.99.240> has joined #yocto | 02:32 | |
| *** JordonWu <JordonWu!~quassel@221.226.9.57> has quit IRC | 02:33 | |
| *** JordonWu <JordonWu!~quassel@221.226.9.57> has joined #yocto | 02:34 | |
| *** JordonWu <JordonWu!~quassel@221.226.9.57> has quit IRC | 02:50 | |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 02:53 | |
| *** wilblake <wilblake!~wilblake@2804:14c:7d82:17f9:4198:2eba:207f:b18d> has joined #yocto | 02:57 | |
| *** john3 <john3!~john@host86-143-93-24.range86-143.btcentralplus.com> has quit IRC | 03:40 | |
| *** black_13 <black_13!48b62bb7@gateway/web/freenode/ip.72.182.43.183> has quit IRC | 03:54 | |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 03:59 | |
| *** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-fqhgexxiobdonmwf> has quit IRC | 04:05 | |
| *** wilblake <wilblake!~wilblake@2804:14c:7d82:17f9:4198:2eba:207f:b18d> has quit IRC | 04:33 | |
| *** morphis <morphis!~morphis@pD9ED68BD.dip0.t-ipconnect.de> has joined #yocto | 04:49 | |
| *** hbruce1 <hbruce1!~hbruce@192.55.55.41> has quit IRC | 04:50 | |
| *** sugnan <sugnan!~sugnan@134.134.139.77> has joined #yocto | 04:59 | |
| *** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC | 05:04 | |
| *** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 05:09 | |
| *** AndersD <AndersD!~anders@194-237-220-218.customer.telia.com> has joined #yocto | 05:11 | |
| *** bananadev <bananadev!~onlyester@117.6.99.240> has quit IRC | 05:13 | |
| *** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 05:13 | |
| *** bananadev <bananadev!~onlyester@118.70.128.150> has joined #yocto | 05:16 | |
| *** AndersD <AndersD!~anders@194-237-220-218.customer.telia.com> has quit IRC | 05:18 | |
| *** AndersD <AndersD!~anders@194-237-220-218.customer.telia.com> has joined #yocto | 05:19 | |
| *** agust <agust!~agust@p4FCB49B8.dip0.t-ipconnect.de> has joined #yocto | 05:23 | |
| zzeroo | Since I update to the latest poky git:master my custom kernel builds are failing with: "kgit-s2q: command not found" | 05:28 |
| paulg | zzeroo, normally that would be in recipe-sysroot-native/usr/bin/kgit-s2q of your kernel build | 05:36 |
| *** qt-x <qt-x!~Thunderbi@217.10.196.2> has joined #yocto | 05:39 | |
| zzeroo | No isn't there.... I had tryed to include "DEPENDS = "kern-tools-native"' but that dos'nt work, too. https://gist.github.com/95a2d93ae0fe0b09fa9f544bc2981b5f | 05:40 |
| paulg | you shouldn't need to add a depends on kernel tools, if you inherit/use the base kernel stuff. | 05:43 |
| *** hamis <hamis!~irfan@110.93.212.98> has joined #yocto | 05:44 | |
| zzeroo | paulg: I know this was just a test. I fight since two hours on that | 05:46 |
| *** Smitty__ <Smitty__!5843b8bc@gateway/web/freenode/ip.88.67.184.188> has quit IRC | 05:47 | |
| *** MarcWe <MarcWe!~hmw@zimbra.welvaarts.com> has quit IRC | 05:54 | |
| *** MarcWe <MarcWe!~hmw@163.172.44.94> has joined #yocto | 05:59 | |
| paulg | zzeroo, yeah I get how fighting with infrastructural stuff can be frustrating. Have you seen this already? | 06:00 |
| paulg | https://www.yoctoproject.org/docs/1.6.1/kernel-dev/kernel-dev.html | 06:00 |
| *** JaMa <JaMa!~martin@217.30.68.212> has joined #yocto | 06:02 | |
| zzeroo | paulg: I use this https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html | 06:03 |
| paulg | ok, yes - that is a more up to date version. | 06:04 |
| zzeroo | But the whole documtentation dosn't contain on 'kgit' ^^ | 06:04 |
| zzeroo | But the whole documtentation dosn't contain one 'kgit' ^^ | 06:04 |
| *** pohly <pohly!~pohly@p5DE8F2FD.dip0.t-ipconnect.de> has joined #yocto | 06:05 | |
| paulg | not a solution, but an approach -- you could maybe start with a bbappend instead of a custom bb; then you should have all the tools / depends at your fingertips | 06:07 |
| *** hamdyaea <hamdyaea!~root@226.91.60.188.dynamic.wline.res.cust.swisscom.ch> has joined #yocto | 06:07 | |
| zzeroo | A bbappend for a vanilla linux kernel? which | 06:08 |
| *** jonakn_ <jonakn_!c33c449c@gateway/web/freenode/ip.195.60.68.156> has joined #yocto | 06:09 | |
| zzeroo | paulg: but i'll try. This is one thing i hav'nt yeat | 06:10 |
| erbo | Is there anyone here who is using the "testimage" features, also called "automated-runtime-testing" in the dev-manual? I'm trying to use it using the systemd-boot "backend" but it seems like it's not really working out-of-the-box so I'm wondering if there's any current users or if the feature might have been broken at some point. | 06:17 |
| hamdyaea | Someone know why there is nothing in my mkefisik.wks file when I : wic create mkefidisk -e core-image-x11 ? | 06:19 |
| *** paulg <paulg!~paulg@198-84-239-75.cpe.teksavvy.com> has quit IRC | 06:21 | |
| *** vmeson <vmeson!~rmacleod@192-0-133-4.cpe.teksavvy.com> has quit IRC | 06:21 | |
| *** tavish <tavish!~tavish@unaffiliated/tavish> has joined #yocto | 06:22 | |
| hamdyaea | LetoThe2nd, : Hi, do you have knowledge about the wic create command ? | 06:22 |
| *** paulg <paulg!~paulg@198-84-239-75.cpe.teksavvy.com> has joined #yocto | 06:30 | |
| *** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has joined #yocto | 06:36 | |
| *** jku <jku!~jku@192.198.151.44> has joined #yocto | 06:38 | |
| *** Bunio_FH <Bunio_FH!~bunio@89-68-88-224.dynamic.chello.pl> has joined #yocto | 06:46 | |
| *** Bunio_FH <Bunio_FH!~bunio@89-68-88-224.dynamic.chello.pl> has left #yocto | 06:46 | |
| hamdyaea | I added this to my mkefidisk.wks file but I still can't boot part / --source rootfs --ondisk sdb --fstype=ext4 --label platform --align 1024 --size 10240 | 06:50 |
| hamdyaea | someone can help me ? | 06:50 |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 06:50 | |
| hamdyaea | ChrysD, : Are you there ? | 06:52 |
| ChrysD | hamdyaea : Yeah | 06:53 |
| ChrysD | hamdyaea : Are you aware that i'm completely a newbie in yocto ? ahahah | 06:53 |
| hamdyaea | ChrysD, : No I don't know it | 06:53 |
| ChrysD | hamdyaea : I can try to help but still i can't guarantee any result. | 06:54 |
| hamdyaea | ChrysD, : I am very close to what I want now | 06:54 |
| ChrysD | hamdyaea : So what's the problem now ? | 06:55 |
| hamdyaea | ChrysD, : I create the image with the command : wic create mkedifisk -e core-image-x11 and the system don't boot anymore when I flash the .direct. | 06:56 |
| *** tavish <tavish!~tavish@unaffiliated/tavish> has quit IRC | 06:57 | |
| *** t0mmy <t0mmy!~tprrt@217.114.201.133> has joined #yocto | 07:01 | |
| *** yann <yann!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has quit IRC | 07:02 | |
| *** Smitty_ <Smitty_!86bfdc49@gateway/web/freenode/ip.134.191.220.73> has joined #yocto | 07:13 | |
| *** rajm <rajm!~robertmar@167.98.27.226> has joined #yocto | 07:15 | |
| *** yohboy <yohboy!~yohan@162.38.31.56> has joined #yocto | 07:15 | |
| *** mckoan|away is now known as mckoan | 07:15 | |
| ChrysD | hamdyaea : I sent you a message at the top | 07:21 |
| ChrysD | you should see my name at the top of the chat | 07:21 |
| *** ed2 <ed2!~Adium@192.198.151.43> has joined #yocto | 07:26 | |
| *** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto | 07:29 | |
| Smitty_ | The command to build the target OS Image SDK (toolchain and sysroots) is ? Searched the docs, but clearly I'm missing something | 07:29 |
| *** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.217.128.72.97> has quit IRC | 07:35 | |
| *** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.217.128.72.97> has joined #yocto | 07:41 | |
| PinkSnake | @Smitty_ http://www.yoctoproject.org/docs/2.3/sdk-manual/sdk-manual.html#sdk-building-an-sdk-installer ? | 07:41 |
| *** avalluri <avalluri!~avalluri@192.55.55.37> has quit IRC | 07:43 | |
| *** john3 <john3!~john@host86-143-93-24.range86-143.btcentralplus.com> has joined #yocto | 07:44 | |
| *** avalluri <avalluri!~avalluri@192.55.55.37> has joined #yocto | 07:49 | |
| *** john3 <john3!~john@host86-143-93-24.range86-143.btcentralplus.com> has quit IRC | 07:51 | |
| *** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.217.128.72.97> has quit IRC | 07:55 | |
| *** yann <yann!~yann@LFbn-1-12676-32.w90-90.abo.wanadoo.fr> has joined #yocto | 07:59 | |
| *** geoffrey_l <geoffrey_l!~geoffrey_@lns-bzn-39-82-255-32-23.adsl.proxad.net> has joined #yocto | 07:59 | |
| *** toscalix <toscalix!~toscalix@80.91.70.201> has joined #yocto | 08:00 | |
| *** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has joined #yocto | 08:00 | |
| *** Smitty_ <Smitty_!86bfdc49@gateway/web/freenode/ip.134.191.220.73> has quit IRC | 08:02 | |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 08:07 | |
| *** grma <grma!~gruberm@80.93.38.128> has joined #yocto | 08:11 | |
| hamdyaea | ed2, : I have a question about the : mkefidisk.wks can you help me ? | 08:14 |
| ed2 | hamdyaea: sure | 08:14 |
| hamdyaea | ed2, : The last time I have created an image with wic create mkedifisk -e core-image-x11, there was many things already in the mkedifisk.wsk file | 08:15 |
| *** Smitty_ <Smitty_!86bfdc49@gateway/web/freenode/ip.134.191.220.73> has joined #yocto | 08:15 | |
| hamdyaea | ed2, : Now there Is nothing | 08:15 |
| Smitty_ | Sorry, I dropped my connection before I could copy that link. Could you post it again, please | 08:16 |
| hamdyaea | ed2, : I just added : part / --source rootfs --ondisk sdb --fstype=ext4 --label platform --align 1024 --size 10240$ | 08:16 |
| hamdyaea | ed2, : But I don't know why the last time there was many things | 08:16 |
| ed2 | hamdyaea: could it be that you've changed it accidentally or changed the branch? | 08:17 |
| ed2 | hamdyaea: is gid diff shows something for this file? | 08:17 |
| ed2 | git diff | 08:17 |
| *** plcp_ <plcp_!c1382434@gateway/web/freenode/ip.193.56.36.52> has quit IRC | 08:18 | |
| hamdyaea | ed2, : https://pastebin.com/StYG927s there are many diffenrence but I didn't change the branch | 08:20 |
| *** tavish <tavish!~tavish@unaffiliated/tavish> has joined #yocto | 08:20 | |
| ed2 | hamdyaea: looks like you've changed it. "git checkout scripts/lib/wic/canned-wks/mkefidisk.wks" will restore it back | 08:21 |
| ed2 | hamdyaea: however, your last change will be lost | 08:21 |
| ed2 | hamdyaea: I mean the last like you've added | 08:21 |
| hamdyaea | ed2 : I am in the jethro branch I have to do : git checkout jethro scripts/lib/wic/canned-wks/mkefidisk.wks ? | 08:22 |
| ed2 | nope, just what i showed | 08:26 |
| ed2 | it will revert that file to HEAD, which is jethro in your case | 08:26 |
| hamdyaea | ed2, : OK I see, I have a question again : -part /boot --source bootimg-efi --sourceparams="loader=grub-efi" | 08:27 |
| hamdyaea | ed2, : How can I modify it if I don't want the efi ? | 08:27 |
| *** Smitty_ <Smitty_!86bfdc49@gateway/web/freenode/ip.134.191.220.73> has quit IRC | 08:27 | |
| *** Smitty_ <Smitty_!86bfdc49@gateway/web/freenode/ip.134.191.220.73> has joined #yocto | 08:28 | |
| ed2 | hamdyaea: you can look at directdisk.wks. I thought this is what you've used to produce bootable image, no? | 08:28 |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 08:29 | |
| hamdyaea | ed2, : OK I see, so I can do a : wic create directdisk -e core-image-x11 ? | 08:30 |
| ed2 | yes | 08:30 |
| hamdyaea | ed2, : Thanks you saved many many hours :) | 08:30 |
| ed2 | or wic create <your own .wks file> -e core-image-x11 | 08:30 |
| hamdyaea | ed2, : of search | 08:30 |
| ed2 | hamdyaea: anyway, you'd probably benefit from reading the doc: http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#creating-partitioned-images | 08:31 |
| *** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.217.128.72.97> has joined #yocto | 08:31 | |
| ed2 | and reading wic help kickstart too :) | 08:32 |
| hamdyaea | ed2, : OK i will read it | 08:34 |
| ed2 | hamdyaea: I'm actually surprised that your hardware doesn't support EFI boot. Could it be that you've missed it somehow when you looked for it in BIOS settings? | 08:36 |
| *** gtristan <gtristan!~tristanva@110.11.179.72> has joined #yocto | 08:36 | |
| hamdyaea | ed2, : I looked everywhere there is no efi option in the bios and when I try an efi image it don't works.. | 08:39 |
| Smitty_ | Can someone please post the link to the creation of an SDK (toolchain and sysroots) for an OS Image. I cannot find it | 08:39 |
| hamdyaea | ed2, : So it don't work and I don't see the advantage of the efi | 08:39 |
| *** gtristan <gtristan!~tristanva@110.11.179.72> has left #yocto | 08:43 | |
| *** gtristan <gtristan!~tristanva@110.11.179.72> has joined #yocto | 08:43 | |
| *** egavin <egavin!~egavin@24.red-217-126-80.staticip.rima-tde.net> has joined #yocto | 08:57 | |
| *** rburton <rburton!~Adium@home.burtonini.com> has joined #yocto | 09:02 | |
| *** mappy <mappy!b9691ff9@gateway/web/freenode/ip.185.105.31.249> has joined #yocto | 09:02 | |
| PinkSnake | @Smitty_ sure http://www.yoctoproject.org/docs/2.3/sdk-manual/sdk-manual.html#sdk-building-an-sdk-installer ? | 09:05 |
| *** madav <madav!~madav@134.134.139.77> has joined #yocto | 09:24 | |
| *** Smitty_ <Smitty_!86bfdc49@gateway/web/freenode/ip.134.191.220.73> has quit IRC | 09:26 | |
| *** john3 <john3!~john@host86-143-93-24.range86-143.btcentralplus.com> has joined #yocto | 09:38 | |
| *** Smitty_ <Smitty_!86bfdc49@gateway/web/freenode/ip.134.191.220.73> has joined #yocto | 09:40 | |
| Smitty_ | Don't undertsnad why my conneciton keeps dropping !! | 09:40 |
| *** nighty-- <nighty--!~nighty@d246113.ppp.asahi-net.or.jp> has quit IRC | 09:41 | |
| *** Ox4` <Ox4`!~user@5.53.119.222> has joined #yocto | 09:41 | |
| Smitty_ | Anyway, thanks for the link. That confirms my understanding, it's an option to the target image build, rather than a separate target | 09:41 |
| Smitty_ | I'm not sure I undertsand the section about static libraries. "By default, this toolchain does not build static binaries. " How does that make any sense ? | 09:43 |
| ChrysD | this is not because of GPL? | 09:45 |
| Smitty_ | To me to make much more sense for an SDK to include static libs by default, and an OS Image to *not* include those libs. After all, how many people are going to be doing development *inside* their running OS Image ? Yet the whole point of the SDK is to do development - and static libraries are definitely needed there. | 09:46 |
| Smitty_ | And the instructions for addressing this issue is to also include the static libs in the OS Image, which seems unnecessary, even undesirable. | 09:47 |
| *** john3 <john3!~john@host86-143-93-24.range86-143.btcentralplus.com> has quit IRC | 09:48 | |
| ChrysD | Smitty_ : Maybe i'm in another world as i'm a newbie, but because of avoiding lot of issue due to GPL requirement, does it something like... As by default you doesn't build static binaries, and the fact that you have to enable, make you more responsible in case of violation of GPL? | 09:48 |
| Smitty_ | I don't follow your argument. How does a library being static change anything to do with licencing ? | 09:49 |
| Smitty_ | So, again, I ask this question, since the answer I received yesterday was confusing. What's the approved/recommended way to include the static libraries in the SDK only ? | 09:57 |
| ChrysD | RDEPENDS_${PN}-dev = "" ? | 09:58 |
| JoiF | If the library is built using GPL components and is not GPL itself, then the applies as if you were building a statically linked executable. | 10:03 |
| JoiF | If the library is built using GPL components and is not GPL itself, then the same applies as if you were building a statically linked executable. | 10:03 |
| *** john3 <john3!~john@host86-143-93-24.range86-143.btcentralplus.com> has joined #yocto | 10:04 | |
| JoiF | And all of this is the reason why copyright, patent and (perhaps) trademark laws should all be taken out back and shot. | 10:06 |
| JoiF | IMHO | 10:06 |
| ChrysD | JoiF : Maybe i'm not understanding, but are you admitting what i'm seeing ? My english is quite bad. | 10:07 |
| JoiF | Admitting? | 10:07 |
| ChrysD | agreeing or whatever | 10:07 |
| rburton | Smitty_: is your question "how do i put static libraries into a SDK i've built?" | 10:08 |
| JoiF | ChrysD: Probably | 10:08 |
| JoiF | ChrysD: Neither of us are probably offering any help to poor Smitty_ (on my part because I don't know a helpful/practical answer to his question), but I think we're both talking about the same thing, yes. | 10:09 |
| *** Bunio_FH <Bunio_FH!~bunio@89-68-88-224.dynamic.chello.pl> has joined #yocto | 10:10 | |
| ChrysD | JoiF : Yeah it's what I was talking about to be sure that i understand thanks. | 10:10 |
| JoiF | ChrysD: And then I went on (completely off-topic for this channel) to express my opinions on particularly copyright and patent law. ;) | 10:12 |
| rburton | Smitty_: because if it is, the answer is SDKIMAGE_FEATURES_append = " staticdev-pkgs" in either your local.conf for just you, your distro conf as a product-wide default, or an image recipe for per-sdk control | 10:13 |
| rburton | Smitty_: note that poky doesn't build static libraries generally so hopefully you've started constructing your own distro | 10:14 |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 10:15 | |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC | 10:16 | |
| *** blueness <blueness!~blueness@cpe-67-247-195-186.buffalo.res.rr.com> has joined #yocto | 10:16 | |
| *** nighty-- <nighty--!~nighty@s229123.ppp.asahi-net.or.jp> has joined #yocto | 10:25 | |
| *** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-87-53.fbx.proxad.net> has quit IRC | 10:31 | |
| *** yann <yann!~yann@LFbn-1-12676-32.w90-90.abo.wanadoo.fr> has quit IRC | 10:40 | |
| *** toanju <toanju!~toanju@185.27.182.30> has joined #yocto | 10:48 | |
| Smitty_ | Please clarify "...poky doesn't build static libraries generally..." - ~~Shirley~~ that's down to the individual recipes. I mean, there's loads of absolutely standard utilities that are composed of libraries. | 11:06 |
| *** yann <yann!~yann@LFbn-1-12676-32.w90-90.abo.wanadoo.fr> has joined #yocto | 11:06 | |
| RP | Smitty_: it defaults to only building dynamic shared libraries, not static ones | 11:07 |
| Smitty_ | I don't understand how that makes any sense, for the reason I just stated. Plenty of standard utilities are made up of static libs | 11:07 |
| Smitty_ | not dynamic | 11:07 |
| Smitty_ | I'm not sure we're even talking about the same thing here | 11:08 |
| rburton | Smitty_: poky configures autotools to pass —disable-static so vast amounts of the system won't be built statically | 11:08 |
| Smitty_ | WHAT !!! | 11:08 |
| rburton | chill, it's an option. turn it off. | 11:09 |
| *** zeenix <zeenix!~zeenix@83.218.80.243> has joined #yocto | 11:09 | |
| rburton | remember poky is an example. make your own distro. if you want static libraries, don't turn them off. | 11:09 |
| RP | FWIW the system does not need or use those static libraries, we've had no reports of problems due to that change | 11:09 |
| RP | and as rburton says, if it bothers you, enable them | 11:09 |
| Smitty_ | Yeah, maybe this is one of the things I don't understand correctly yet. I keep thinking Poky is a core framework | 11:09 |
| rburton | poky is an example of how to build a distribution using oe-core and bitbake | 11:10 |
| Smitty_ | what is "oe-core" then ? Is it the set of layers that make up the core-image-sato (or minimal) ? | 11:11 |
| rburton | oe-core is basically the meta/ directory in the poky tree | 11:12 |
| rburton | http://git.openembedded.org/openembedded-core/tree/ <— oe-core | 11:12 |
| rburton | as i said yesterday, poky is oe-core + bitbake + meta-poky squashed into a single repo | 11:12 |
| Smitty_ | But, doesn't pretty much everyone use that as a starting point, then maybe add or possibly remove unwanted components from it ? In this sense, it looks very much like a framework | 11:13 |
| rburton | what is that? | 11:13 |
| Smitty_ | poky | 11:13 |
| rburton | some do | 11:13 |
| rburton | some just take bitbake and oe-core directly | 11:13 |
| rburton | if you're building your own distro then you might as well just use oe-core+bitbake directly | 11:14 |
| Smitty_ | but there's hardly anything else in the poky tree | 11:14 |
| rburton | correct | 11:14 |
| nrossi | RP: since you are around, you might be able to answer this question i had regarding RSS -> Is it an intended feature of RSS that any task dependency (even a dependency on say foo:do_deploy) causes the recipe-sysroot population of that dependent task's sysroot components? | 11:14 |
| rburton | Smitty_: the only bits in poky that are not in oe-core and bitbake are the pieces you'll be replacing anyway | 11:14 |
| RP | nrossi: in general, yes but there is logic which limits that dependency tree | 11:15 |
| RP | nrossi: e.g. dependencies of a target recipe on native recipes are not followed | 11:15 |
| RP | nrossi: its the same logic as the "build from sstate" situation would use | 11:16 |
| RP | nrossi: see setscene_depvalid() in sstate.bbclass | 11:16 |
| Smitty_ | is there a description of the layers in poky: meta, meta-poky, meta skeleton, meta-yocto, meta-yocto-bsp, meta-selftest and why they are there ? | 11:17 |
| nrossi | RP: ok, thanks. Just wanted to make sure I was understanding the logic correctly. I am creating a "native" like extend class for a tertiary platform cpu, and it is being populated into the sysroot. Unfortunately I don't see an easy way to prevent that would modifying staging.bbclass like is done for native/multilib/etc. | 11:18 |
| *** Crofton <Crofton!~Crofton@pool-71-171-14-56.ronkva.east.verizon.net> has quit IRC | 11:18 | |
| RP | nrossi: might you be better using multiconfig? | 11:20 |
| RP | nrossi: I know we are missing inter multiconfig dependencies right now but that shouldn't be hard to fix | 11:20 |
| nrossi | RP: yes that what is need from multiconfig to have it working | 11:20 |
| nrossi | RP: but this is all targeted for meta-xilinx's pyro release, but would be great to use multiconfig in the future :) | 11:21 |
| RP | nrossi: I'd love to have the patch to sort that. It shouldn't be hard as we put all the foundations in place... | 11:22 |
| nrossi | RP: i've just worked around the sysroot population issue for now by setting the extension class to use a /usr/<target_sys> | 11:22 |
| *** gtristan <gtristan!~tristanva@110.11.179.72> has quit IRC | 11:26 | |
| Smitty_ | rburton: I'm still missing something. The project that gets downloaded when following http://www.yoctoproject.org/docs/2.3/mega-manual/mega-manual.html#building-images is "poky", which is essentially all the meta data responsible for instructing *some set of tools* to construct an OS image. Some of those tools are of course required as the target OS toolchain, I'm not interested in them. I want to know what the other set of tools | 11:27 |
| nrossi | RP: also just curious, with regards to the staging populating. In your opinion should the image recipes populate things like u-boot, qemu-helper-native, etc. (stuff in EXTRA_IMAGEDEPENDS)? | 11:28 |
| *** blueness <blueness!~blueness@cpe-67-247-195-186.buffalo.res.rr.com> has quit IRC | 11:28 | |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto | 11:28 | |
| Smitty_ | It seems like some of those tools may be specific to the Poky OS image, and so are provided by the poky project I download. Then there's other tools that are bitbake, but, strangely also downloaded when I retrieve poky. (BTW, that's very confusing) | 11:29 |
| rburton | Smitty_: the quick start has you download poky as its quicker/easier than bitbake+oe-core and ensuring you get matching versions | 11:29 |
| rburton | this really isn't complicated. poky is a few projects merged into a single git repo for convenience. | 11:29 |
| Smitty_ | It's not complicated when you understand it | 11:30 |
| RP | nrossi: populate in what sense? you mean the do_populate_sysroot tasks from u-boot and so on? | 11:30 |
| rburton | Smitty_: poky is bitbake + oe-core + meta-poky, in a single git repo, for convenience. | 11:30 |
| *** qt-x <qt-x!~Thunderbi@217.10.196.2> has quit IRC | 11:30 | |
| rburton | use it or not, your choice. | 11:30 |
| rburton | some do, some don't | 11:30 |
| Smitty_ | The clouds are lifting | 11:30 |
| Smitty_ | Did I miss that day in school where that was discussed ? (where is that explained in the documentation ?) | 11:32 |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC | 11:32 | |
| nrossi | RP: yes, whilst u-boot is mostly non-problematic, qemu-helper-native can be in that you can only have one set of qemu binaries despite the usefulness of RSS where you could have two different qemu-helper-native's which provide different sysroots for qemuboot | 11:32 |
| rburton | Smitty_: the quick start definitely skips over it as the purpose of the quick start is to be quick | 11:32 |
| Smitty_ | ok, so I'm not as bad as I feared | 11:32 |
| RP | nrossi: it was originally intentional as we had a lot of trouble actually getting qemu binaries where we could find them to boot images | 11:33 |
| RP | nrossi: I say originally as I'm unsure where we ended up running them from in the end | 11:34 |
| Smitty_ | What do you mean "ensuring you get matching versions" - matching versions of what ? what needs to match ? | 11:34 |
| rburton | Smitty_: bitbake has an API which oe-core uses, so if you use new oe-core with two year old bitbake, the APIs don't match | 11:34 |
| nrossi | RP: from what i can tell it was because of this that qemu was being populated into the images -native sysroot, and that was what qemuboot was pointing at | 11:34 |
| ChrysD | I'm not sure if I say is correct, but you download poky because everything come with same version and everything work... so you don't sometimes " use" poky, but you download the " poky directory". | 11:35 |
| *** tavish <tavish!~tavish@unaffiliated/tavish> has quit IRC | 11:35 | |
| Smitty_ | bitbake "has an API" ? isn't it a collection of commandline tools ? | 11:35 |
| nrossi | RP: but with the recent changes, qemuboot now points to the sysroot of qemu-helper-native | 11:36 |
| RP | nrossi: right, I thought it had changed | 11:36 |
| *** tavish <tavish!~tavish@unaffiliated/tavish> has joined #yocto | 11:36 | |
| RP | Smitty_: bitbake parses the metadata. The format of the metadata is effectively an API and that format can change over time like any API | 11:37 |
| ChrysD | Smitty_ : You have learn yoct at school ? | 11:37 |
| rburton | Smitty_: also there's a python library which the metadata has access to | 11:37 |
| nrossi | RP: previously with the single sysroot, i had a custom QEMU installing into a /usr/bin/qemu-foo/ directory so that both could exist. But now with RSS it would be nice to remove this hack :) | 11:37 |
| ChrysD | Smitty_ : I mean, oe-core bitbake ? | 11:37 |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 11:37 | |
| RP | nrossi: I'm open to ideas... | 11:38 |
| *** berton <berton!~berton@189.114.111.135> has joined #yocto | 11:38 | |
| *** gtristan <gtristan!~tristanva@110.11.179.89> has joined #yocto | 11:39 | |
| nrossi | RP: im not entirely sure, but i would imagine something along the lines of excluding do_deploy tasks from sysroot population, and simply setup qemu-helper-native so that is "deploys" its native sysroot (aka nop deploy task) | 11:40 |
| *** mappy <mappy!b9691ff9@gateway/web/freenode/ip.185.105.31.249> has left #yocto | 11:40 | |
| *** tavish <tavish!~tavish@unaffiliated/tavish> has quit IRC | 11:40 | |
| RP | nrossi: do_deploy tasks are excluded as the sysroot only handles do_populate_sysroot tasks. You mean skip anything which takes a dependency chain through a do_deploy task? | 11:41 |
| nrossi | RP: yes, thats what i mean | 11:41 |
| RP | nrossi: hmm, maybe | 11:44 |
| *** ChrysD_ <ChrysD_!d9804861@gateway/web/freenode/ip.217.128.72.97> has joined #yocto | 11:44 | |
| *** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.217.128.72.97> has quit IRC | 11:46 | |
| *** ChrysD_ <ChrysD_!d9804861@gateway/web/freenode/ip.217.128.72.97> has quit IRC | 11:51 | |
| *** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.217.128.72.97> has joined #yocto | 11:52 | |
| *** mappy <mappy!b9691ff9@gateway/web/freenode/ip.185.105.31.249> has joined #yocto | 11:54 | |
| *** caiortp <caiortp!~inatel@131.221.240.226> has joined #yocto | 11:54 | |
| Smitty_ | That problem exists in loads of other environments, and is solved usually by having the tool not honor (warn or error) on instructions it doesn't understand. It's still the developers problem to get a matching tool and API as expressed in the meta-data | 11:56 |
| rburton | the failure case is an error that the required API version isn't high enough | 11:58 |
| Smitty_ | right, so the tool (bitbake) just says, sorry, I can't understand this, get the right version of bitbake you dummy ! | 11:59 |
| Smitty_ | I didn't realise that Yocto was trying to do all that | 12:00 |
| *** bananadev <bananadev!~onlyester@118.70.128.150> has quit IRC | 12:01 | |
| Smitty_ | ANd, I'm not sure why you would want to try - can someone explain that ? I mean, is there some compelling reason that it's not left to the developer to get the right version of the tools ? | 12:03 |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC | 12:03 | |
| *** blueness <blueness!~blueness@cpe-67-247-195-186.buffalo.res.rr.com> has joined #yocto | 12:04 | |
| *** berton <berton!~berton@189.114.111.135> has quit IRC | 12:04 | |
| *** berton <berton!~berton@189.114.111.135> has joined #yocto | 12:05 | |
| rburton | Smitty_: accidental use of mismatching versions: eg bitbake adds new api that oe-core then uses , if you upgrade oe-core but not bitbake then it will faiu | 12:05 |
| rburton | fail | 12:05 |
| *** joshuagl <joshuagl!~joshuagl@192.198.151.44> has joined #yocto | 12:06 | |
| *** blueness <blueness!~blueness@cpe-67-247-195-186.buffalo.res.rr.com> has quit IRC | 12:06 | |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto | 12:06 | |
| ChrysD | rburton : that's why we download poky to get sure that everything work, not because we want poky itself right? | 12:06 |
| rburton | it saves you the need to track two repos yeah | 12:07 |
| rburton | but generally speaking you'll get a big error if you need to upgrade bitbake | 12:07 |
| rburton | ie http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=66bd8b82472ee6dc91a715ac91410dc5a826f2a3 | 12:07 |
| Smitty_ | Sure, so they get delivered together - that makes sense. But, why deliver them with poky ? Because poky also relies upon specific version of the API ? | 12:07 |
| *** zeeblex <zeeblex!~zeeblex@gate-zro.freescale.com> has quit IRC | 12:07 | |
| rburton | because oe-core and bitbake are separate repositories and they only get delivered together in poky | 12:08 |
| *** vmeson <vmeson!~rmacleod@192-0-133-4.cpe.teksavvy.com> has joined #yocto | 12:08 | |
| Smitty_ | How does that make sense, since their versioning is so tightly coupled, why are they seperate ? | 12:08 |
| Ox4` | guys, how to resolve QA warnings? I have several after building mariadb: http://dpaste.com/0V4FRTK | 12:08 |
| rburton | Smitty_: because bitbake is a generic build system, you don't need to use oe-core | 12:09 |
| Smitty_ | OK, so if you want to use oe-core, you need the right version of bitbake, and if you want to use yocto, you then need the right version of bitbake+oe-core. | 12:10 |
| rburton | yocto isnt software you can download | 12:11 |
| rburton | the yocto project is oe-core + bitbake + lots of other bits of software | 12:11 |
| Smitty_ | yocto is the meta-data | 12:11 |
| Smitty_ | right ? | 12:11 |
| rburton | no, oe-core is the metadata | 12:11 |
| rburton | well, some of the metadata. the core metadata, thus the name. | 12:11 |
| ChrysD | Smitty_ : Yocto is just thename of the project. | 12:11 |
| Smitty_ | which project ? | 12:11 |
| rburton | the yocto project | 12:12 |
| ChrysD | Smitty_ : Yocto Project ahah | 12:12 |
| rburton | ChrysD: ^5 | 12:12 |
| Smitty_ | the project to produce bitbake and oe-core in a manner which can be used to produce an OS Image (or sdk, or whatever) and the example is poky ? | 12:12 |
| ChrysD | Smitty_ : Yocto it's only the name of the project that is : thecombinaison of tools and humans ressources beyond the mecanism that we use in everyday life | 12:12 |
| rburton | Smitty_: yes | 12:12 |
| JoiF | It's like a bunch of little all ladies making pancakes. They call themselves "Lil'Ol'Ladies" but old ladies is not their product.. pancakes is their product.. :p | 12:13 |
| JoiF | s/all/old/ | 12:13 |
| ChrysD | JoiF : thank you. ahahah | 12:13 |
| ChrysD | And Open-Embedded is also the same ? Like it's the name of the project besides oe-core? | 12:14 |
| *** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-87-53.fbx.proxad.net> has joined #yocto | 12:14 | |
| rburton | Smitty_: https://www.slideshare.net/rossburton/the-yocto-project | 12:14 |
| Smitty_ | So, in fact, if I'm a parasitic business, trying to produce a product that requires a full linux distro, and also uses some weird hardware - in fact, I don't care about Yocto, I am really only interested in bitbake and oe-core, and I might have a look at the poky example to get a feel for how to use them | 12:15 |
| *** mappy <mappy!b9691ff9@gateway/web/freenode/ip.185.105.31.249> has quit IRC | 12:15 | |
| ChrysD | Smitty_ : What you mean by " you don't care about yocto ".d. | 12:17 |
| ChrysD | Does the open embedded project still exist and yocto project follow the evolution of oe-core, or now open embedded project doesn't exist anymore and it's the yocto wrokgroup that is in charge of upgrading oe-core? | 12:21 |
| *** zeeblex <zeeblex!~zeeblex@gate-zro.freescale.com> has joined #yocto | 12:21 | |
| *** mappy <mappy!b9691ff9@gateway/web/freenode/ip.185.105.31.249> has joined #yocto | 12:22 | |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC | 12:23 | |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto | 12:23 | |
| Smitty_ | OK, so, once I download poky, I see a bunch of "layers" each in its own directory. How do I know which layer depends upon which ? Can bitbake show me that ? | 12:26 |
| ChrysD | Smitty_ : What you mean by which layers depends upon which ? The purpose of layers is to be not dependant. | 12:27 |
| Smitty_ | then in what way are they layers ? | 12:28 |
| Smitty_ | For example, if I want to build the core-image-minimal, doesn;t that require that some other layer like meta get processed first ? | 12:30 |
| Smitty_ | then meta-skeleton, then meta-yocto (or whatever ? | 12:30 |
| ChrysD | Smitty_ : you need that : https://www.google.fr/search?q=yocto+layers&client=ubuntu&hs=8e0&channel=fs&source=lnms&tbm=isch&sa=X&ved=0ahUKEwjR19e79_bTAhVPZ1AKHc4NBRwQ_AUICigB&biw=1301&bih=671#imgrc=voOjRiJQPtAARM: | 12:31 |
| *** ash_charles <ash_charles!~acharles@2607:fad8:4:6:c8a6:17d:5ad6:1157> has joined #yocto | 12:33 | |
| Smitty_ | right, that's what I thought, so there is a dependence. I can't build a layer I add in for my app that I want to sit on top of core image minimal until I build whichever layer is responsible for the toolchain (oe-core, I guess ???)..Furthermore, I probably want other libraries that are not present until another layer, like meta-poky is built. So, in what way is there not a dependency ? | 12:34 |
| jku | Smitty_: the layer README should state the layers it depends on. The actual dependencies will be from individual recipes depending on recipes in the other layer | 12:34 |
| rburton | Smitty_: meta-skeleton is an example, meta-yocto-bsp are some sample BSPs so unrelated to the image. | 12:35 |
| rburton | also each layer.conf can express layer dependnecies | 12:35 |
| *** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-87-53.fbx.proxad.net> has quit IRC | 12:35 | |
| ChrysD | Smitty_ : I prefer that image http://www.aosabook.org/images/yocto/aosa2.jpg | 12:35 |
| rburton | eg LAYERDEPENDS_meta-python = "core openembedded-layer" | 12:35 |
| jku | rburton: do we use that for something? | 12:36 |
| Smitty_ | I'm getting there.....v e r y s l o w l y ..... | 12:36 |
| rburton | jku: bitbake erros out if they're not satisfied | 12:37 |
| jku | oh right just found it | 12:38 |
| Smitty_ | So, back to yesterdays question. I want to add a static library to core-image-minimal. In fact I really only want it in core-image-minimal' SDK. So, I create a layer for my library. using something like a template (meta-skeleton???) as starting point. | 12:39 |
| *** marka <marka!~masselst@135-23-92-83.cpe.pppoe.ca> has joined #yocto | 12:39 | |
| rburton | use devtool to make a recipe, then add the package to your sdk | 12:39 |
| ChrysD | rburton : RDEPENDS_${PN}-dev shuold help there and specify a package which include the static library ? | 12:40 |
| *** jku <jku!~jku@192.198.151.44> has quit IRC | 12:40 | |
| rburton | ChrysD: more logical to use the right variable to add the static library pakage to the sdk | 12:40 |
| rburton | SDKTARGETSOMETHINGOROTHER | 12:40 |
| Smitty_ | why do I use devtool ? is copying meta-skeleton and editing it not a good idea ? | 12:41 |
| ChrysD | Smitty_ : Because some people in the yocto project spend our doing that tool ? lool | 12:42 |
| ChrysD | Smitty_ : Because some people in the yocto project spend hour doing that tool ? lool | 12:42 |
| Smitty_ | And I want a layer , not just a recipe , don't I ? | 12:42 |
| Smitty_ | because I don't want to change the existing layers, which I am quite happy with. I should just add a layer on top of them | 12:43 |
| ChrysD | Smitty_ : Yeah but you have also some tools to do a layer | 12:44 |
| Smitty_ | Sorry, I don't understand - "to do a layer" | 12:45 |
| Smitty_ | you mean create a new layer ? | 12:45 |
| ChrysD | Smitty_ : to create | 12:45 |
| *** rj_ <rj_!58d39085@gateway/web/freenode/ip.88.211.144.133> has joined #yocto | 12:45 | |
| Smitty_ | and I don;t copy skeleton why ? what's it for ? | 12:45 |
| ChrysD | Smitty_ : For example skeleton show you how to do a recipe of a kernel module | 12:46 |
| ChrysD | Smitty_ : How to do a recipe for a service | 12:46 |
| Smitty_ | Aaaaaaarrrrrrrrrgggggghhhhhhh | 12:46 |
| Smitty_ | you mean like skel the kernel module example ? | 12:46 |
| rj_ | Hey, i'm trying to build the 3.4 kernel for my yocto build but it says it can't find the kernel even though it exists. Does anyone know why it doesn't work? http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/recipes-kernel/linux/linux-yocto_3.4.bb?id=28fb81ab56fda2c2ef5b7c8f84610a35efcdaba6 | 12:46 |
| ChrysD | Smitty_ : in meta-skeleton/recipes-skeleton/service you ahve an example of recipe for a service | 12:47 |
| Smitty_ | from the famous book by gkh ? | 12:47 |
| *** gattuso <gattuso!~gattuso@pompel.me> has quit IRC | 12:48 | |
| abelloni | I think the modul is scull ;) | 12:48 |
| ChrysD | Smitty_ : I don't remember but I think meta-yocto-bsp is also an example of bsp layer | 12:48 |
| Smitty_ | yeah, that's kind of obvious from the name, unlike skeleton which sounds like a "bare-bones' generic layer for *something* | 12:49 |
| ChrysD | Smitty_ : meta-skeleton is a bunch of lot recipes examples for various thinks | 12:49 |
| BaloneyGeek|work | Hi, how do I rebuild a single recipe in such a way that do_install_append() defined inside the recipe is run again? | 12:50 |
| BaloneyGeek|work | A couple of sanity checks inside do_populate_sysroot in meta-qt5 fails and I've added a few sed commands to the do_install_append func, but they don't seem to have any effect | 12:51 |
| BaloneyGeek|work | I even tried to do echo something ?? /home/user/hello.txt but that file isn't created | 12:51 |
| BaloneyGeek|work | Just to check if the func was executing | 12:52 |
| BaloneyGeek|work | Err echo something >> hello.txt | 12:53 |
| rj_ | BaloneyGeek|work: I think you can also just clean that package, and then rebuild | 12:53 |
| BaloneyGeek|work | bitbake -c clean qtbase && bitbake qtbase? | 12:53 |
| rj_ | BaloneyGeek|work: Something like bitbake -c clean <packagename> and then rebuild | 12:53 |
| BaloneyGeek|work | It didn't have any effect the last time but let's try again. | 12:53 |
| rj_ | BaloneyGeek|work: i think that would work yea | 12:53 |
| *** sugnan <sugnan!~sugnan@134.134.139.77> has quit IRC | 12:55 | |
| *** madav <madav!~madav@134.134.139.77> has quit IRC | 12:55 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC | 12:57 | |
| *** AndersD <AndersD!~anders@194-237-220-218.customer.telia.com> has quit IRC | 12:59 | |
| *** Bunio_FH <Bunio_FH!~bunio@89-68-88-224.dynamic.chello.pl> has quit IRC | 13:00 | |
| *** Bunio_FH <Bunio_FH!~bunio@89-68-88-224.dynamic.chello.pl> has joined #yocto | 13:00 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 13:01 | |
| *** ant_work <ant_work!~ant__@host108-181-dynamic.31-79-r.retail.telecomitalia.it> has joined #yocto | 13:02 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has joined #yocto | 13:05 | |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 13:10 | |
| BaloneyGeek|work | rj_: Nope, that failed | 13:11 |
| BaloneyGeek|work | echo ${D} >> /home/builder/helo.txt <-- that line's in do_install_append | 13:12 |
| rj_ | BaloneyGeek|work: Aww, i expected it to work | 13:12 |
| BaloneyGeek|work | I don't see that file being created either | 13:12 |
| *** gattuso <gattuso!~gattuso@pompel.me> has joined #yocto | 13:13 | |
| rj_ | howabout something like... touch /home/user/test | 13:13 |
| BaloneyGeek|work | Hang on, clean and make will take a while :-/ | 13:14 |
| BaloneyGeek|work | In the meantime, does this sed command look okay? | 13:15 |
| BaloneyGeek|work | sed -i -E "s@-L(.*)/opt/vc/lib@-L/opt/vc/lib@g" ${D}/${libdir}/pkgconfig/Qt5*.pc | 13:15 |
| BaloneyGeek|work | It's supposed to basically fix -L/home/builder/.../opt/vc/lib to -L/opt/vc/lib | 13:16 |
| rj_ | I honestly don't know that much about sed, as i am quite new to linux/yocto | 13:16 |
| PinkSnake | @rj_ PREFERRED_PROVIDER_virtual/kernel is correctly set ? | 13:16 |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 13:17 | |
| rj_ | PinkSnake: In the machine.conf? | 13:17 |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 13:17 | |
| PinkSnake | @rj_ yep | 13:17 |
| PinkSnake | @rj_ to select the kernel kernel | 13:17 |
| rj_ | PinkSnake: it's not there at all, i only have: PREFERRED_VERSION_linux-yocto_genericx86-64 ?= "3.4%" | 13:18 |
| PinkSnake | @rj_ and PREFERRED_VERSION_virtual/kernel | 13:18 |
| PinkSnake | @rj_ maybe check in board configuraiton maybe an other kernel is selected | 13:18 |
| rj_ | PinkSnake: Ah, its in the .inc: PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" | 13:18 |
| rj_ | Should i change that to "3.4%" ? | 13:19 |
| PinkSnake | @rj_ maybe try 3.4 but normaly 3.4% is ok | 13:19 |
| PinkSnake | no no | 13:19 |
| PinkSnake | you have to set like that : | 13:19 |
| PinkSnake | PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" | 13:19 |
| rj_ | Yea, i have that atm | 13:20 |
| *** tavish <tavish!~tavish@unaffiliated/tavish> has joined #yocto | 13:20 | |
| PinkSnake | PREFERRED_VERSION_virtual/kernel = "3.4" | 13:20 |
| PinkSnake | provider and version are used to select the correct kernel recipe | 13:20 |
| rj_ | aaah okay ill try | 13:21 |
| *** madisox <madisox!~madison@216-75-232-11.static.wiline.com> has joined #yocto | 13:23 | |
| BaloneyGeek|work | rj_: Nope, same error, file not touched | 13:26 |
| *** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-ofnsrnhoaxnkjkmt> has joined #yocto | 13:27 | |
| *** Aethenelle <Aethenelle!~Aethenell@mobile-166-175-61-41.mycingular.net> has joined #yocto | 13:30 | |
| rj_ | BaloneyGeek|work: That's weird... it should work, since i have the same method only in do_configure_append | 13:32 |
| *** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-87-53.fbx.proxad.net> has joined #yocto | 13:32 | |
| *** nighty-- <nighty--!~nighty@s229123.ppp.asahi-net.or.jp> has quit IRC | 13:36 | |
| *** toanju <toanju!~toanju@185.27.182.30> has quit IRC | 13:38 | |
| BaloneyGeek|work | Any other ideas? | 13:39 |
| PinkSnake | @BaloneyGeek|work you to add the file inside the rootfs target ? | 13:41 |
| PinkSnake | you want* | 13:41 |
| *** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-87-53.fbx.proxad.net> has quit IRC | 13:41 | |
| BaloneyGeek|work | PinkSnake: No, I was trying to test if the do_install_append function was being executed at all | 13:42 |
| *** lamego <lamego!~jose@134.134.139.82> has joined #yocto | 13:42 | |
| BaloneyGeek|work | What I want to do is execute this line before do_populate_sysroot is ru | 13:43 |
| BaloneyGeek|work | sed -i -E "s@-L(.*)/opt/vc/lib@-L/opt/vc/lib@g" ${D}/${libdir}/pkgconfig/Qt5*.pc | 13:43 |
| BaloneyGeek|work | So I put this command into do_install_append inside qtbase_git.bb (the function was already there) | 13:43 |
| BaloneyGeek|work | But it doesn't seem to have any effect | 13:43 |
| PinkSnake | @BaloneyGeek|work do_install_append is inside recipe.bb ? | 13:44 |
| *** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-87-53.fbx.proxad.net> has joined #yocto | 13:45 | |
| BaloneyGeek|work | PinkSnake: yes | 13:46 |
| Smitty_ | BaloneyGeek, what's the parens for ? | 13:47 |
| BaloneyGeek|work | parens? | 13:48 |
| Smitty_ | (.*) | 13:48 |
| Smitty_ | that part | 13:48 |
| PinkSnake | @BaloneyGeek|work do_install_append is not only in .bbappend ? | 13:48 |
| BaloneyGeek|work | The idea is to convert -L/home/builder/.../opt/vc/lib to -L/opt/vc/lib | 13:48 |
| BaloneyGeek|work | I independently verified that the sed command is correct | 13:49 |
| BaloneyGeek|work | PinkSnake: it's in the .bb file. There's no .bbappend | 13:49 |
| Smitty_ | OK, so you are not asking any more for support for the sed itself ? | 13:49 |
| PinkSnake | @BaloneyGeek|work don't modifie recipe directly should use .bbappend | 13:50 |
| BaloneyGeek|work | Smitty_: No, because I'm pretty confident that the sed command is correct | 13:50 |
| Smitty_ | OK | 13:50 |
| BaloneyGeek|work | Unless ${D}/${libdir}/pkgconfig/Qt5*.pc is wrong? | 13:50 |
| BaloneyGeek|work | PinkSnake: I'd need to have my own layer for that right? | 13:51 |
| BaloneyGeek|work | Seems overkill for one sed line | 13:51 |
| *** AndersD <AndersD!~anders@h83-209-191-235.cust.se.alltele.net> has joined #yocto | 13:51 | |
| Smitty_ | OK, still trying to figure out how a layer is added when *not* added by me to build/conf/somefile.conf - I mean, clearly something is adding the layers to the build, what is it ? | 13:53 |
| rj_ | Smitty_: Layers aren't added automatically right? | 13:53 |
| Smitty_ | That's right, as far as I have been told. It's not like simply the presence of a subdirectory of my project source directory that looks like a layer is enough to get it added | 13:54 |
| BaloneyGeek|work | I tried to add a new function called do_populate_sysroot_prepend and do the stuff there if that worked, but no joy there either | 13:54 |
| rj_ | Smitty_: indeed, i always had to manually add it to build/conf/bblayers.conf | 13:55 |
| rburton | Smitty_: if its not in bblayers.conf it won't be read at all | 13:55 |
| rj_ | BaloneyGeek|work: How about do_configure_append() ? | 13:55 |
| *** dreyna <dreyna!~dreyna@96-68-167-113-static.hfc.comcastbusiness.net> has joined #yocto | 13:55 | |
| JoiF | Smitty_: Are you confusing a "layer" with a recipe that's included in a layer? | 13:56 |
| JoiF | a "layer" normally has a "conf/layer.conf" associated with it | 13:57 |
| *** joshuagl <joshuagl!~joshuagl@192.198.151.44> has quit IRC | 13:58 | |
| Smitty_ | Yeah, I am slowly groking this stuff. So, we for some reason have a file still called bblayers.conf.sample that is copied to MYBUILD_DIR/conf/bblayers.conf I *must* get used to this idea that these files are *generated* dynamically by a standard process | 14:00 |
| PinkSnake | @BaloneyGeek|work yes but it's yocto friendly | 14:00 |
| Smitty_ | are not generated | 14:00 |
| *** Ox4` <Ox4`!~user@5.53.119.222> has quit IRC | 14:00 | |
| *** Aethenelle <Aethenelle!~Aethenell@mobile-166-175-61-41.mycingular.net> has quit IRC | 14:00 | |
| *** Ox4 <Ox4!~user@unaffiliated/zloy> has joined #yocto | 14:01 | |
| BaloneyGeek|work | PinkSnake: Yeah but would there be other solutions in case I didn't want the overhead of a new layer right now? | 14:01 |
| *** nighty-- <nighty--!~nighty@s229123.ppp.asahi-net.or.jp> has joined #yocto | 14:01 | |
| Smitty_ | BBLAYERS_NON_REMOVABLE doesn;t appear in mega manual. What is it ? | 14:02 |
| rburton | Smitty_: if i say it doesn't matter and you can ignore it, will you just ignore it? | 14:04 |
| rburton | just pretend its not there | 14:04 |
| CTtpollard | close your eyes | 14:05 |
| Smitty_ | It's kind of weird, whoever created our bblayers.conf file left it there, but duplicated meta and meta-yocto in BBLAYERS. Is it actually required ? | 14:05 |
| rburton | the NON_REMOVABLE assignment is for toaster | 14:06 |
| rburton | i think there's a better way of doing what it does but thats for later | 14:07 |
| Smitty_ | yeah, another tool I know nothing about - really, what is toaster ? (please tell me there's a good reason for that name) | 14:07 |
| PinkSnake | @BaloneyGeek|work it's up to you but in my opinion it's better to use .bbappend, for example I created a .bbappend on the kernel recipe juste to save .config file ... | 14:08 |
| JoiF | Smitty_: It's for creating a pretty picture such as this one: https://www.jof.guru/temppics/non-remove.png This was Hob, now deprecated, toaster is a web-based GUI thingee for messing about. | 14:09 |
| Smitty_ | Sorry, I am a detail guy, I really struggle to move past stuff that seems wrong (and my definition of wrong includes anything that looks duplicated) | 14:09 |
| *** dreyna_ <dreyna_!~dreyna@96-68-167-113-static.hfc.comcastbusiness.net> has joined #yocto | 14:09 | |
| Smitty_ | OK, so there's some gui tool that's trying to sanity check on editing a config file (which is wrong, since there is already a tool that has to parse the config file, it should do the sanity check) | 14:11 |
| rburton | Smitty_: its not sanity checking but please just don't rathole into what toaster is | 14:11 |
| JoiF | Not exactly. Toaster is a GUI for configuring | 14:11 |
| Smitty_ | right, I don't care. | 14:12 |
| *** dreyna <dreyna!~dreyna@96-68-167-113-static.hfc.comcastbusiness.net> has quit IRC | 14:12 | |
| JoiF | Errr.. You asked.. :) | 14:13 |
| *** aehs29 <aehs29!~aehernan@134.134.139.75> has joined #yocto | 14:13 | |
| *** Bunio_FH <Bunio_FH!~bunio@89-68-88-224.dynamic.chello.pl> has left #yocto | 14:15 | |
| *** JPEWhacker <JPEWhacker!cc4da374@gateway/web/freenode/ip.204.77.163.116> has joined #yocto | 14:17 | |
| *** Crofton|work <Crofton|work!~balister@pool-71-171-14-56.ronkva.east.verizon.net> has quit IRC | 14:21 | |
| Smitty_ | So, oe-init-build-env calls oe-setup-builddir which wants a file (oddly it wants it already in the build directory) that indicates which layers to be built. If it doesn't find it it looks for the bblayers.conf.sample file, and moves that into the build directory (under conf). I am struggling to understand the mindset that devised this. I really don't get the idea that I should ever pre-populate *anything* inside a build directory | 14:22 |
| Smitty_ | ...or put files in my source directory that just get copied into the build directory | 14:22 |
| Smitty_ | as configuration | 14:23 |
| Smitty_ | why not just read the configuration out of the source directory ? | 14:23 |
| *** Crofton|work <Crofton|work!~balister@pool-71-171-12-170.nwrknj.east.verizon.net> has joined #yocto | 14:23 | |
| *** zeeblex <zeeblex!~zeeblex@gate-zro.freescale.com> has quit IRC | 14:24 | |
| rburton | i'm strugging to wonder why you're still worrying about this. you need to configure the layers that are available. it can't auto-detect because it has no way of knowing where you've put them, and mandating a layer placement policy would be silly and annoy people who routinely add/remove layers. | 14:26 |
| rburton | please just accept thats what oe-init-build-env does, and move on. | 14:27 |
| majuk | lol, he's still going? Lawd. | 14:31 |
| Smitty_ | It's a question of comprehending how to do what seems like a simple task - add a layer to a project so that another developer can retrieve the project and *just build it*. without having to edit build/conf/bblayers.conf and add in my layer - which if I follow every piece of documentation on how to add a layer, is what he would have to do. | 14:31 |
| rburton | Smitty_: as discussed yesterday it's either 1) document to edit bblayers.conf, or 2) provide your own bblayers.conf.sample. | 14:32 |
| *** rj_ <rj_!58d39085@gateway/web/freenode/ip.88.211.144.133> has quit IRC | 14:32 | |
| ant_work | Smitty_, maybe it's easier if you see how Yocto was built around OE | 14:32 |
| ant_work | pls check out https://www.openembedded.org/wiki/OE-Core_Standalone_Setup | 14:33 |
| ant_work | Smitty_, the idea was, we must not scare Corp. developers :) | 14:33 |
| Smitty_ | WHat does that mean ? | 14:33 |
| ant_work | it means you can just start with bitbake + oe-core | 14:34 |
| *** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has joined #yocto | 14:34 | |
| rburton | we went through this earlier today | 14:34 |
| ant_work | ah, sorry then | 14:34 |
| rburton | np | 14:34 |
| ChrysD | Smitty_ : What's bad about bblayers.conf? | 14:34 |
| ChrysD | Smitty_ : I mean, what's bad with the idea of telling which layer you would like to the specific build you are doing ? | 14:39 |
| BaloneyGeek|work | Okay I'm a fully laden ocean going idiot. I was editing the file in the wrong git clone. | 14:39 |
| BaloneyGeek|work | Works now | 14:39 |
| ChrysD | Smitty_ : And what about a script you can make in other to source " automatically" and download " automatically" the good git repo and editing "automatically" the bblayers.conf for the developper you would like to give | 14:39 |
| rburton | ChrysD: no need for that, the git repo can provide a correct sample | 14:41 |
| rburton | (which is what poky does) | 14:41 |
| ChrysD | rburton : what you mean? | 14:42 |
| rburton | oe-core and meta-poky provide bblayer.conf.sample files, which are different | 14:42 |
| Smitty_ | You know, sometimes it's the little things that cause confusion. Just call the file bblayers.conf (remove the .sample) Enough said. Sorry for being a pain. | 14:43 |
| rburton | Smitty_: why? that would be wrong. its not bblayers.conf mainly because if you used it as-is it would fail to parse | 14:43 |
| Smitty_ | what do you mean ? Why would it fail to parse ? | 14:44 |
| rburton | bblayers.conf.template i can see as being a sightly more descriptive filename | 14:44 |
| rburton | BBLAYERS ?= " \ | 14:44 |
| rburton | ##OEROOT##/meta \ | 14:44 |
| rburton | " | 14:44 |
| Smitty_ | yeah, that's what mine looks like | 14:44 |
| rburton | thats the sample | 14:44 |
| rburton | the ##OEROOT## gets replaced for you | 14:45 |
| rburton | to be a real path | 14:45 |
| rburton | then its not a template but a working file | 14:45 |
| Smitty_ | Exactly, so, call it bblayers.conf | 14:45 |
| Smitty_ | it's the confuigraiton file for the layers | 14:45 |
| rburton | but it won't parse with ##OEROOT## in! | 14:45 |
| Smitty_ | it will when you run setupdir | 14:45 |
| Smitty_ | which - let's face it - is mandatory | 14:46 |
| rburton | which is when the template gets copied to bblayers.conf | 14:46 |
| rburton | and is no longer a template | 14:46 |
| rburton | copied *and modified* | 14:46 |
| Smitty_ | so what ? by then it's in the build directory, it's not something I want to control at that point. | 14:47 |
| Smitty_ | I want to control it before it gets used by the build system, not after | 14:47 |
| Smitty_ | and oe-init.XXX is part of the build system, | 14:48 |
| *** ed2 <ed2!~Adium@192.198.151.43> has quit IRC | 14:49 | |
| *** joshuagl <joshuagl!~joshuagl@192.198.151.43> has joined #yocto | 14:50 | |
| Smitty_ | Don't you see why that is confusing ? | 14:51 |
| *** AndersD <AndersD!~anders@h83-209-191-235.cust.se.alltele.net> has quit IRC | 14:57 | |
| *** dreyna_ <dreyna_!~dreyna@96-68-167-113-static.hfc.comcastbusiness.net> has quit IRC | 14:59 | |
| *** dreyna <dreyna!~dreyna@96-68-167-113-static.hfc.comcastbusiness.net> has joined #yocto | 15:01 | |
| *** nighty-- <nighty--!~nighty@s229123.ppp.asahi-net.or.jp> has quit IRC | 15:02 | |
| *** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-xymwxlxwsdqmhixg> has joined #yocto | 15:02 | |
| zzeroo | does someone here the `meta-rust-bin` layer? | 15:04 |
| zzeroo | +know | 15:04 |
| *** ChrysD_ <ChrysD_!d9804861@gateway/web/freenode/ip.217.128.72.97> has joined #yocto | 15:05 | |
| zzeroo | I ask because of this bug i discovered yesterday https://github.com/rust-embedded/meta-rust-bin/issues/19 | 15:06 |
| *** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.217.128.72.97> has quit IRC | 15:06 | |
| *** dreyna_ <dreyna_!~dreyna@96-68-167-113-static.hfc.comcastbusiness.net> has joined #yocto | 15:07 | |
| *** dreyna <dreyna!~dreyna@96-68-167-113-static.hfc.comcastbusiness.net> has quit IRC | 15:09 | |
| *** ant_work <ant_work!~ant__@host108-181-dynamic.31-79-r.retail.telecomitalia.it> has quit IRC | 15:10 | |
| *** zeeblex <zeeblex!~zeeblex@gate-zro.freescale.com> has joined #yocto | 15:12 | |
| *** dreyna_ <dreyna_!~dreyna@96-68-167-113-static.hfc.comcastbusiness.net> has quit IRC | 15:12 | |
| *** dfaught <dfaught!~dfaught@163.188.client.vntx.net> has joined #yocto | 15:15 | |
| *** jairglez <jairglez!~jairdeje@134.134.139.73> has joined #yocto | 15:15 | |
| *** dfaught <dfaught!~dfaught@163.188.client.vntx.net> has quit IRC | 15:16 | |
| *** msvb-lab <msvb-lab!~michael@x55b540ac.dyn.telefonica.de> has quit IRC | 15:17 | |
| *** MarcWe <MarcWe!~hmw@163.172.44.94> has quit IRC | 15:19 | |
| *** dfaught <dfaught!~dfaught@163.188.client.vntx.net> has joined #yocto | 15:19 | |
| *** ChrysD_ <ChrysD_!d9804861@gateway/web/freenode/ip.217.128.72.97> has quit IRC | 15:20 | |
| *** dfaught <dfaught!~dfaught@163.188.client.vntx.net> has quit IRC | 15:21 | |
| *** dfaught <dfaught!~dfaught@163.188.client.vntx.net> has joined #yocto | 15:21 | |
| *** chbae <chbae!~chbae@59.10.135.122> has joined #yocto | 15:23 | |
| *** mappy <mappy!b9691ff9@gateway/web/freenode/ip.185.105.31.249> has quit IRC | 15:27 | |
| *** msvb-lab <msvb-lab!~michael@x55b540ac.dyn.telefonica.de> has joined #yocto | 15:37 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC | 15:40 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 15:41 | |
| *** yohboy <yohboy!~yohan@162.38.31.56> has quit IRC | 15:43 | |
| *** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-xymwxlxwsdqmhixg> has quit IRC | 15:48 | |
| *** hamis <hamis!~irfan@110.93.212.98> has quit IRC | 15:49 | |
| JoiF | Smitty_: Look at this, as an example: http://freescale.github.io/#download the section "Download the source code" | 15:52 |
| JoiF | So they're using repo to get all kinds of stuff. One of them is this repo: https://github.com/Freescale/fsl-community-bsp-base | 15:56 |
| JoiF | Which contains both a setup-environment script as well as conf/bblayers.conf | 15:57 |
| JoiF | So if you need your coworker to "just build it", you could set up a "repo" repository that fetches everything and does what he needs | 15:58 |
| majuk | also, repo is just a wrapper for git | 16:01 |
| *** dreyna <dreyna!~dreyna@75-57-9-97.lightspeed.sntcca.sbcglobal.net> has joined #yocto | 16:03 | |
| *** itseris <itseris!~emikulin@76.77.65.2> has joined #yocto | 16:05 | |
| kergoth | aye, repo is one of many multiple git repo management tools. repo is one of the most popular, others use git submodules, myrepos, or use combo-layer or git-subtree to maintain a monolithic repo | 16:05 |
| *** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has left #yocto | 16:07 | |
| *** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-87-53.fbx.proxad.net> has quit IRC | 16:08 | |
| *** chbae <chbae!~chbae@59.10.135.122> has quit IRC | 16:09 | |
| *** rajm <rajm!~robertmar@167.98.27.226> has quit IRC | 16:09 | |
| *** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC | 16:11 | |
| *** nemunaire <nemunaire!~nemunaire@2a01:e35:8bb7:3c60::a> has quit IRC | 16:16 | |
| *** nemunaire <nemunaire!~nemunaire@2a01:e35:8bb7:3c60::a> has joined #yocto | 16:16 | |
| *** geoffrey_l <geoffrey_l!~geoffrey_@lns-bzn-39-82-255-32-23.adsl.proxad.net> has quit IRC | 16:18 | |
| *** peacememories <peacememories!~textual@e247-139.eduroam.tuwien.ac.at> has joined #yocto | 16:34 | |
| *** zeenix <zeenix!~zeenix@83.218.80.243> has quit IRC | 16:37 | |
| JoiF | Exactly. Hence the "example" :p | 16:41 |
| *** ne-o <ne-o!32cab972@gateway/web/freenode/ip.50.202.185.114> has joined #yocto | 16:41 | |
| *** ne-o <ne-o!32cab972@gateway/web/freenode/ip.50.202.185.114> has quit IRC | 16:42 | |
| *** stephano <stephano!~stephano@134.134.139.70> has joined #yocto | 16:42 | |
| *** t0mmy <t0mmy!~tprrt@217.114.201.133> has quit IRC | 16:44 | |
| *** cogitoergobum <cogitoergobum!~cogitoerg@213.74.244.66> has joined #yocto | 16:47 | |
| *** JoiF <JoiF!~jofr@193.182.166.3> has quit IRC | 16:49 | |
| *** cogitoergobum <cogitoergobum!~cogitoerg@213.74.244.66> has quit IRC | 16:50 | |
| *** cogitoergobum <cogitoergobum!~cogitoerg@213.74.244.66> has joined #yocto | 16:50 | |
| *** neverpan1c <neverpan1c!~clemens@towel.neverpanic.de> has joined #yocto | 16:52 | |
| *** neverpanic <neverpanic!~clemens@towel.neverpanic.de> has quit IRC | 16:52 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC | 16:53 | |
| JPEWhacker | Does anyone know where packagegroup-core-ssh-openssh is defined? There are a bunch of these packagegroups in meta/classes/core-image.bbclass that I can't seem to find the RDEPENDS for | 16:54 |
| *** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has quit IRC | 16:57 | |
| *** gdg <gdg!803b166e@gateway/web/cgi-irc/kiwiirc.com/ip.128.59.22.110> has joined #yocto | 16:58 | |
| joshuagl | meta/recipes-core/packagegroups/packagegroup-core-ssh-openssh.bb | 16:59 |
| gdg | how can I configure the kernel? is bitbake linux-xlnx -c menuconfig the right command to display the kernel menuconfig panel? | 16:59 |
| top22 | hello, when adding a recipe with Proprietary license, bitbake complains about not finding it in the collected licenses; isn't proprietary license supposed to be already defined ? | 17:01 |
| *** sjolley <sjolley!~sjolley@134.134.139.76> has quit IRC | 17:03 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 17:07 | |
| JaMa | top22: IIRC that exception works only with CLOSED | 17:07 |
| *** martinkelly <martinkelly!~martin@65-122-179-226.dia.static.qwest.net> has quit IRC | 17:08 | |
| *** martinkelly <martinkelly!~martin@66-162-141-202.static.twtelecom.net> has joined #yocto | 17:09 | |
| *** egavin <egavin!~egavin@24.red-217-126-80.staticip.rima-tde.net> has quit IRC | 17:11 | |
| *** toscalix <toscalix!~toscalix@80.91.70.201> has quit IRC | 17:12 | |
| *** berton <berton!~berton@189.114.111.135> has joined #yocto | 17:13 | |
| *** sameo <sameo!samuel@nat/intel/x-nrflgiabgmmgwodn> has joined #yocto | 17:18 | |
| *** john3 <john3!~john@host86-143-93-24.range86-143.btcentralplus.com> has quit IRC | 17:19 | |
| *** martinkelly <martinkelly!~martin@66-162-141-202.static.twtelecom.net> has quit IRC | 17:22 | |
| top22 | JaMa: poky/meta/files/common-licenses/ contains Proprietary but not CLOSED | 17:24 |
| top22 | strange | 17:25 |
| *** pohly <pohly!~pohly@p5DE8F2FD.dip0.t-ipconnect.de> has quit IRC | 17:28 | |
| *** pohly <pohly!~pohly@p5DE8F2FD.dip0.t-ipconnect.de> has joined #yocto | 17:29 | |
| *** martinkelly <martinkelly!~martin@65-122-179-226.dia.static.qwest.net> has joined #yocto | 17:40 | |
| *** sjolley <sjolley!~sjolley@134.134.139.78> has joined #yocto | 17:42 | |
| *** peacememories <peacememories!~textual@e247-139.eduroam.tuwien.ac.at> has quit IRC | 17:48 | |
| *** peacememories <peacememories!~textual@e247-139.eduroam.tuwien.ac.at> has joined #yocto | 17:50 | |
| *** msvb-lab <msvb-lab!~michael@x55b540ac.dyn.telefonica.de> has quit IRC | 17:53 | |
| *** john3 <john3!~john@host86-143-93-24.range86-143.btcentralplus.com> has joined #yocto | 17:56 | |
| *** msvb-lab <msvb-lab!~michael@x55b540ac.dyn.telefonica.de> has joined #yocto | 18:03 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has quit IRC | 18:13 | |
| JPEWhacker | joshuagl: Doh, that makes sense. Thanks | 18:22 |
| *** clopez <clopez!~tau@neutrino.es> has quit IRC | 18:23 | |
| *** tavish <tavish!~tavish@unaffiliated/tavish> has quit IRC | 18:23 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has joined #yocto | 18:24 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has quit IRC | 18:28 | |
| itseris | Is it possible to define PREFERRED_VERSIONs of packages in image recipes? It doesn't seem to be working for me and I'm wondering if it's intentional or not | 18:31 |
| *** JaMa <JaMa!~martin@217.30.68.212> has quit IRC | 18:33 | |
| fray | no.. PREFERRED_VERSION is a system wide setting.. it affects what is -built- (which then affects what is installed)... | 18:33 |
| fray | image is 'too late', in that everything is already built | 18:34 |
| itseris | Ahhh I see, thanks! | 18:35 |
| *** tavish <tavish!~tavish@unaffiliated/tavish> has joined #yocto | 18:38 | |
| *** SoniaLeon <SoniaLeon!~sleonbau@134.134.139.73> has joined #yocto | 18:48 | |
| *** SoniaLeon <SoniaLeon!~sleonbau@134.134.139.73> has quit IRC | 18:58 | |
| *** peacememories <peacememories!~textual@e247-139.eduroam.tuwien.ac.at> has quit IRC | 18:59 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has joined #yocto | 19:00 | |
| *** peacememories <peacememories!~textual@e247-139.eduroam.tuwien.ac.at> has joined #yocto | 19:00 | |
| *** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-ykvxjblxhwqzqnbt> has joined #yocto | 19:03 | |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 19:06 | |
| *** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 19:06 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has quit IRC | 19:07 | |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 19:08 | |
| *** th <th!~thintze@threllis.net> has quit IRC | 19:10 | |
| *** th <th!~thintze@unaffiliated/th> has joined #yocto | 19:10 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has joined #yocto | 19:10 | |
| seebs | FWIW, I saw the thing about pseudo and /etc/group but I haven't had time to look closely. Will try to get a look at it "soon". | 19:17 |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 19:18 | |
| fray | lol, then you are ahead of me.. I must have overlooked it | 19:21 |
| seebs | ... oh, i see, they just sent it to me directly, not oe-core | 19:21 |
| seebs | long story short, the fakepass stuff has static char foo[PSEUDO_PWD_MAX], which is 4096, because who would need more than 4096 characters for a line in /etc/group? | 19:22 |
| seebs | answer, someone who's making a group with >350 members | 19:22 |
| JPEWhacker | seebs: How are you managing your user recipes and their dependencies? | 19:24 |
| JPEWhacker | I'm currently working on a user management related problem | 19:24 |
| seebs | I am not! | 19:25 |
| fray | ahh.. a 'real bug', but an odd one to have that many folks in a group | 19:25 |
| JPEWhacker | ah, misunderstood | 19:25 |
| seebs | I don't actually use Yocto anymore, it's just that pseudo is my baby and I want to keep working on it. :P | 19:25 |
| JPEWhacker | ok | 19:25 |
| JPEWhacker | Well then, anyone else have pointers? I want to create a bunch of groups (essentially to allow a non-root user access to what would normally be privileged hardware), and then have a single user get assigned to the correct groups based on some configuration variables | 19:28 |
| JPEWhacker | I currently have a recipe per group, but managing the dependencies for the main user is a pain | 19:29 |
| *** grma <grma!~gruberm@80.93.38.128> has quit IRC | 19:29 | |
| *** joshuagl <joshuagl!~joshuagl@192.198.151.43> has quit IRC | 19:30 | |
| *** Snert__ <Snert__!~LoginName@106-24-237-24.gci.net> has joined #yocto | 19:43 | |
| majuk | Anyone experienced problems with openssl recognizing certs after build? I am drowning. | 19:44 |
| *** Snert <Snert!~LoginName@106-24-237-24.gci.net> has quit IRC | 19:45 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC | 19:47 | |
| *** joshuagl <joshuagl!~joshuagl@192.198.151.43> has joined #yocto | 19:50 | |
| *** peacememories <peacememories!~textual@e247-139.eduroam.tuwien.ac.at> has quit IRC | 19:52 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 19:52 | |
| *** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC | 19:55 | |
| *** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto | 19:59 | |
| *** morphis <morphis!~morphis@pD9ED68BD.dip0.t-ipconnect.de> has quit IRC | 20:03 | |
| *** Ox4 <Ox4!~user@unaffiliated/zloy> has quit IRC | 20:07 | |
| *** dfaught <dfaught!~dfaught@163.188.client.vntx.net> has quit IRC | 20:11 | |
| *** twallis <twallis!~tom@72.142.74.74> has joined #yocto | 20:13 | |
| twallis | hello | 20:13 |
| twallis | I take it that plenty of people come through here to ask technical questions, but i'm new to the whole embedded linux field and I am receiving some errors building my setup | 20:15 |
| twallis | and considering the error is coming from standard GNU software (GDBM) i was wondering if anyone knew how to help me | 20:15 |
| *** gtristan <gtristan!~tristanva@110.11.179.89> has quit IRC | 20:16 | |
| *** msvb-lab <msvb-lab!~michael@x55b540ac.dyn.telefonica.de> has quit IRC | 20:16 | |
| *** dfaught <dfaught!~dfaught@163.188.client.vntx.net> has joined #yocto | 20:25 | |
| kergoth | twallis: if you have a particular problem or question, ask it, or post the error | 20:28 |
| kergoth | asking if you can ask is not useful | 20:28 |
| twallis | fair enough | 20:28 |
| twallis | chmod: gdbm.h: new permissions are r-xrwxrwx, not r-xr-xr-x | 20:28 |
| twallis | | Makefile:168: recipe for target 'gdbm.h' failed | 20:28 |
| twallis | i'm receiving this error while attempting to 'do_compile' gdbm_1.8.3.bb | 20:29 |
| kergoth | what version? | 20:29 |
| kergoth | could be a pseudo issue, seebs, ever see anything like that? | 20:29 |
| twallis | no, this is a fresh yocto build | 20:30 |
| twallis | I did retry the bitbake command and it proceeded after but it noted that this job was in error | 20:30 |
| twallis | https://pastebin.com/wg1ix4LD | 20:32 |
| twallis | ^^error log | 20:32 |
| denix | twallis: is it master or pyro or morty? | 20:32 |
| twallis | krogoth | 20:33 |
| *** sjolley <sjolley!~sjolley@134.134.139.78> has quit IRC | 20:36 | |
| kergoth | thank you denix for clarifying, apparently 'what version' was unclear regarding what it was referring to | 20:38 |
| twallis | ah, well gdbm version 1.8.3, yocto krogoth release, and if it counts, I'm trying to build the TI processor SDK version 3.03.04 | 20:41 |
| seebs | hmm. that's a very odd set of permissions, to put it mildly. | 20:47 |
| *** dreyna_ <dreyna_!~dreyna@75-57-9-97.lightspeed.sntcca.sbcglobal.net> has joined #yocto | 20:47 | |
| twallis | could that have been something to do with my build environment prior to calling bitbake? | 20:48 |
| seebs | bitbake's pretty good about setting its own permissions. | 20:48 |
| *** dfaught <dfaught!~dfaught@163.188.client.vntx.net> has quit IRC | 20:48 | |
| seebs | We did have an issue at one point involving explicit chmod calls on hard-linked trees, but I don't think that would have produced this. | 20:49 |
| twallis | was the problem something similar to this? | 20:49 |
| *** msvb-lab <msvb-lab!~michael@x55b540ac.dyn.telefonica.de> has joined #yocto | 20:50 | |
| *** dreyna <dreyna!~dreyna@75-57-9-97.lightspeed.sntcca.sbcglobal.net> has quit IRC | 20:51 | |
| seebs | no, it was that a second build of the same package would add user-write permissions to the files. | 20:53 |
| twallis | hmm | 20:53 |
| twallis | any idea what would cause something like I'm having though? I'm reading back through the logs and trying to find when/why chmod is configuring the file the way it is | 20:55 |
| twallis | but this is the first time I've built a linux image like this and I'm not getting very far finding that | 20:56 |
| denix | twallis: can you see where that chmod is coming from? | 20:56 |
| *** caiortp <caiortp!~inatel@131.221.240.226> has quit IRC | 20:57 | |
| denix | chmod -w gdbm.h | 20:58 |
| denix | chmod: gdbm.h: new permissions are r-xrwxrwx, not r-xr-xr-x | 20:58 |
| denix | so, chmod -w only affects owner permissions, not all | 20:58 |
| *** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has joined #yocto | 20:59 | |
| denix | from the manual - If no references are specified it defaults to “all” but modifies only the permissions allowed by the umask. | 20:59 |
| fray | denix isn't it based on the umask? | 21:00 |
| fray | (w/o the 'who' part?) | 21:00 |
| fray | tahts why I always do ugo-w | 21:00 |
| fray | or similar | 21:00 |
| denix | fray: per the manual I cited above, yes | 21:00 |
| twallis | it's getting called in a makefile, as -w yeah. hmm, I wonder if I ran the build scripts as root if that would make a difference. i'm running as a sudoer, but not directly as root | 21:00 |
| denix | so, if gdbm wants to properly change permissions, it shouldn't use chmod -w | 21:00 |
| fray | yup | 21:00 |
| twallis | Right now I'm trying to find the makefile that was called so I can change that chmod call | 21:01 |
| kergoth | you should not be building as root at all, ever | 21:01 |
| twallis | okay | 21:01 |
| denix | twallis: what's your filesystem you are running this on? | 21:02 |
| *** dfaught <dfaught!~dfaught@gateway/vpn/privateinternetaccess/dfaught> has joined #yocto | 21:02 | |
| twallis | just a straight ubuntu 16.04 lts | 21:03 |
| twallis | i am however running the build on an external hard drive | 21:03 |
| twallis | the drive was clean when I started this build | 21:04 |
| twallis | that could have something to do with file permissions, actually | 21:04 |
| denix | is it fat by any chance? | 21:04 |
| denix | that would explain all rwx permissions for new files... | 21:04 |
| twallis | ntfs | 21:05 |
| denix | not much better :) | 21:05 |
| fray | ya.. ya fat/ntfs doesn't have real permissions.. | 21:05 |
| twallis | what should it be formatted as? | 21:05 |
| *** marka <marka!~masselst@135-23-92-83.cpe.pppoe.ca> has quit IRC | 21:05 | |
| kergoth | i'd be amazed if that was anywhere near working | 21:05 |
| fray | (well ntfs 'kind of might) | 21:05 |
| denix | you need to use real unix fs | 21:05 |
| twallis | so the actual mounted hard drive, not an external | 21:06 |
| denix | can be external, just need to be ext3/ext4/xfs/btrfs, etc | 21:06 |
| twallis | ah | 21:06 |
| twallis | I'll give that a shot | 21:07 |
| *** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-ofnsrnhoaxnkjkmt> has quit IRC | 21:07 | |
| twallis | thank you very much! | 21:07 |
| fray | if you don't have control over your hard disk partitions, you can also do a loop back (will be slower) but it's a workaround for those who are prevented by IT policy from having a working system | 21:07 |
| denix | twallis: so, mkfs.ext4 would be fast fix, since you said the harddrive was empty | 21:07 |
| twallis | was, yeah. all it has on it is the build environment, so that's not too hard to replicate after a format | 21:08 |
| *** sjolley <sjolley!~sjolley@134.134.139.76> has joined #yocto | 21:10 | |
| *** dfaught <dfaught!~dfaught@gateway/vpn/privateinternetaccess/dfaught> has quit IRC | 21:10 | |
| *** ketemphor <ketemphor!~ketemphor@rrcs-96-10-28-210.se.biz.rr.com> has joined #yocto | 21:11 | |
| *** twallis <twallis!~tom@72.142.74.74> has quit IRC | 21:11 | |
| *** ant_home <ant_home!~ant__@host134-11-dynamic.32-79-r.retail.telecomitalia.it> has joined #yocto | 21:12 | |
| *** sjolley1 <sjolley1!sjolley@nat/intel/x-urabivuyykznyvmj> has joined #yocto | 21:15 | |
| *** sjolley <sjolley!~sjolley@134.134.139.76> has quit IRC | 21:15 | |
| *** berton <berton!~berton@189.114.111.135> has quit IRC | 21:15 | |
| *** itseris <itseris!~emikulin@76.77.65.2> has quit IRC | 21:22 | |
| *** itseris <itseris!~emikulin@76.77.65.2> has joined #yocto | 21:23 | |
| *** ash_charles <ash_charles!~acharles@2607:fad8:4:6:c8a6:17d:5ad6:1157> has quit IRC | 21:34 | |
| *** stephano <stephano!~stephano@134.134.139.70> has quit IRC | 21:35 | |
| *** sameo <sameo!samuel@nat/intel/x-nrflgiabgmmgwodn> has quit IRC | 21:38 | |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 21:44 | |
| *** itseris <itseris!~emikulin@76.77.65.2> has quit IRC | 21:48 | |
| *** sgw_ <sgw_!sgw_@nat/intel/x-xyknssroyufdjwmv> has quit IRC | 21:52 | |
| *** sgw_ <sgw_!~sgw_@134.134.139.73> has joined #yocto | 21:53 | |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 21:56 | |
| *** lamego <lamego!~jose@134.134.139.82> has quit IRC | 21:57 | |
| *** msvb-lab <msvb-lab!~michael@x55b540ac.dyn.telefonica.de> has quit IRC | 22:04 | |
| *** JPEWhacker <JPEWhacker!cc4da374@gateway/web/freenode/ip.204.77.163.116> has quit IRC | 22:05 | |
| *** ant_home <ant_home!~ant__@host134-11-dynamic.32-79-r.retail.telecomitalia.it> has quit IRC | 22:11 | |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 22:11 | |
| *** tavish <tavish!~tavish@unaffiliated/tavish> has quit IRC | 22:14 | |
| *** rburton <rburton!~Adium@home.burtonini.com> has quit IRC | 22:14 | |
| *** dreyna_ <dreyna_!~dreyna@75-57-9-97.lightspeed.sntcca.sbcglobal.net> has quit IRC | 22:18 | |
| *** sjolley <sjolley!sjolley@nat/intel/x-rilwrsjpwfxplkuu> has joined #yocto | 22:19 | |
| *** sjolley1 <sjolley1!sjolley@nat/intel/x-urabivuyykznyvmj> has quit IRC | 22:19 | |
| *** Smitty_ <Smitty_!86bfdc49@gateway/web/freenode/ip.134.191.220.73> has quit IRC | 22:28 | |
| *** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has quit IRC | 22:36 | |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 22:40 | |
| *** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 22:47 | |
| *** dreyna <dreyna!~dreyna@75-57-9-97.lightspeed.sntcca.sbcglobal.net> has joined #yocto | 22:53 | |
| *** john3 <john3!~john@host86-143-93-24.range86-143.btcentralplus.com> has quit IRC | 22:57 | |
| *** aehs29 <aehs29!~aehernan@134.134.139.75> has quit IRC | 23:00 | |
| *** agust <agust!~agust@p4FCB49B8.dip0.t-ipconnect.de> has quit IRC | 23:06 | |
| *** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 23:16 | |
| *** Aethenelle <Aethenelle!~Aethenell@199.15.128.78> has quit IRC | 23:21 | |
| *** neverpan1c <neverpan1c!~clemens@towel.neverpanic.de> has quit IRC | 23:25 | |
| *** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 23:28 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC | 23:32 | |
| *** neverpanic <neverpanic!~clemens@towel.neverpanic.de> has joined #yocto | 23:37 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 23:37 | |
| *** itseris <itseris!~emikulin@76.77.65.2> has joined #yocto | 23:40 | |
| *** itseris <itseris!~emikulin@76.77.65.2> has quit IRC | 23:43 | |
| *** joshuagl <joshuagl!~joshuagl@192.198.151.43> has quit IRC | 23:46 | |
| *** msvb-lab <msvb-lab!~michael@x55b540ac.dyn.telefonica.de> has joined #yocto | 23:47 | |
| *** jairglez <jairglez!~jairdeje@134.134.139.73> has quit IRC | 23:49 | |
| *** iseris <iseris!4c4d4102@gateway/web/cgi-irc/kiwiirc.com/ip.76.77.65.2> has joined #yocto | 23:49 | |
| *** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-ykvxjblxhwqzqnbt> has quit IRC | 23:50 | |
| *** behanw <behanw!uid110099@gateway/web/irccloud.com/x-ckxdjbznotzmqhql> has joined #yocto | 23:50 | |
| *** majuk <majuk!~majuk@50-233-77-210-static.hfc.comcastbusiness.net> has quit IRC | 23:53 | |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!
