Friday, 2020-08-07

*** adam3371 <adam3371!> has joined #yocto00:00
*** goliath <goliath!> has quit IRC00:04
*** vineela <vineela!~vtummala@> has quit IRC00:07
adam3371hey 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 what00:11
adam3371possibly I can do to solve this problem?00:11
adam3371thank you in advance ;)00:12
*** dev1990 <dev1990!> has quit IRC00:24
*** adam3371 <adam3371!> has quit IRC00:58
*** rdude <rdude!> has joined #yocto01:00
*** stephano <stephano!> has quit IRC01:14
*** Nooks <Nooks!> has left #yocto01:15
*** gsalazar <gsalazar!5e3ce511@gateway/web/cgi-irc/> has quit IRC01:21
*** kaspter <kaspter!~Instantbi@> has joined #yocto01:47
*** ustas_ <ustas_!~ustas@> has quit IRC01:48
*** kaspter <kaspter!~Instantbi@> has quit IRC02:12
*** ustas <ustas!~ustas@> has joined #yocto02:16
*** hpsy1 <hpsy1!~hpsy@> has joined #yocto02:30
*** mattsm <mattsm!> has quit IRC02:30
*** mattsm <mattsm!> has joined #yocto02:31
*** hpsy <hpsy!~hpsy@> has quit IRC02:31
kergothhuh, 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!> has quit IRC02:39
*** mattsm <mattsm!> has joined #yocto02:41
*** meow` <meow`!~sbourdeli@> has quit IRC02:53
*** NiksDev <NiksDev!~NiksDev@> has quit IRC03:26
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto03:26
*** ustas <ustas!~ustas@> has quit IRC03:48
*** nslu2-log_ <nslu2-log_!> has joined #yocto03:51
*** nslu2-log <nslu2-log!> has quit IRC03:53
*** nslu2-log_ is now known as nslu2-log03:54
*** sgw2 <sgw2!> has quit IRC04:01
*** ustas_ <ustas_!~ustas@> has joined #yocto04:11
*** kroon <kroon!~kroon@> has joined #yocto04:39
*** paulg <paulg!> has quit IRC04:47
*** ssajal <ssajal!> has quit IRC04:58
*** ssajal <ssajal!> has joined #yocto05:00
*** sgw2 <sgw2!> has joined #yocto05:08
*** dreyna <dreyna!> has quit IRC05:09
*** rdude <rdude!> has quit IRC05:11
*** sgw2 <sgw2!> has quit IRC05:14
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC05:17
*** radsquirrel <radsquirrel!> has quit IRC05:20
*** dreyna <dreyna!> has joined #yocto05:27
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC05:32
*** dreyna <dreyna!> has quit IRC05:40
*** radsquirrel <radsquirrel!> has joined #yocto05:47
*** wooosaiiii <wooosaiiii!> has joined #yocto05:50
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:07
*** matthewzmd <matthewzmd!> has quit IRC06:13
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has joined #yocto06:37
*** mbulut <mbulut!> has joined #yocto06:44
*** ustas_ <ustas_!~ustas@> has quit IRC06:48
*** gsalazar <gsalazar!5e3ce511@gateway/web/cgi-irc/> has joined #yocto06:52
*** ustas <ustas!~ustas@> has joined #yocto06:54
*** mckoan|away is now known as mckoan06:54
*** fl0v0 <fl0v0!> has joined #yocto06:59
*** goliath <goliath!> has joined #yocto07:17
*** sagner <sagner!~ags@2a02:169:3df5::edf> has quit IRC07:20
*** sagner <sagner!~ags@2a02:169:3df5::edf> has joined #yocto07:21
*** fbre <fbre!91fdde45@> has joined #yocto07:25
*** ustas <ustas!~ustas@> has quit IRC07:26
fbreHi! 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
*** ustas <ustas!~ustas@> has joined #yocto07:32
LetoThe2ndfbre: 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
fbreI 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@> has joined #yocto07:40
LetoThe2ndfbre: the cmdline.txt part is absolutely rpi specific. agreed on that the script runs in userland but it again is pretty rpi specific07:41
*** PaowZ_ <PaowZ_!~Vince@> has quit IRC07:41
LetoThe2ndfbre: 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@> has quit IRC07:45
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC07:49
*** ustas <ustas!> has joined #yocto07:50
*** PaowZ_ <PaowZ_!~Vince@> has joined #yocto07:56
fbreI 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
LetoThe2ndinit is run. and depending on which init you have, this decides what gets run in which order.07:57
fbreI just can see /sbin/init which is a binary. What does /sbin/init do?07:58
fbreIt's a link to /lib/systemd/systemd08:00
snoRP: 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
snoI give it a shot and tell you how it behaves08:00
*** luneff <luneff!~yury@> has joined #yocto08:00
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto08:01
LetoThe2ndfbre: 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
LetoThe2ndfbre: see:
*** gtristan <gtristan!~tristanva@> has joined #yocto08:03
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto08:05
fbreLetoThe2nd: cool, thanx! That's a good trace to further follow up to :]08:05
*** dev1990 <dev1990!> has joined #yocto08:06
*** davidinux <davidinux!~davidinux@> has quit IRC08:10
*** davidinux <davidinux!> has joined #yocto08:12
*** luneff <luneff!~yury@> has quit IRC08:13
*** adam3371 <adam3371!> has joined #yocto08:19
*** f843d0 <f843d0!~f843d0@> has joined #yocto08:20
f843d0Hello 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 in08:23
f843d0advance for your kind attention08:23
LetoThe2ndf843d0: iso images are probably ro by default, as they are supposed to end up on ro media...08:27
*** beneth <beneth!> has joined #yocto08:27
LetoThe2ndf843d0: so my guess is that iso is just not the image type that you actually want.08:28
f843d0LetoThe2nd: thanks, so for example for importing the solution in VBox, should I go for vmdk somehow?08:28
*** escalion <escalion!> has joined #yocto08:29
LetoThe2ndf843d0: why "somehow"?08:30
LetoThe2ndand why zeus? :P08:30
f843d0LetoThe2nd: is the stable, ain't it?! :)08:30
LetoThe2ndf843d0: um, no?08:31
*** Jebee <Jebee!> has quit IRC08:32
LetoThe2ndf843d0: ok, and what is saying that zeus is the latest stable there?08:32
f843d0LetoThe2nd: Zeus 3.0 October 2019 3.0.3 Stable 22.0.3 1.4408:32
LetoThe2ndDunfell 3.1 April 2020 3.1.1 Long Term Stable08:33
erbofbre: Have you looked at I'm using raspberry pi + read-only-rootfs, and it works well.08:34
LetoThe2nderbo: its about the overlayfs magic (again)08:34
erboOk, I figured the interest in that was in order to find a way to achieve what the magic already achieves. :)08:36
fbreerbo: I opened your link and searched for "overlay" but there aint no such phrase08:36
erbofbre: 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
LetoThe2nderbo: really? (/me is not so sure about that, but would love to be proven wrong)08:38
erboOn my rpi image built with read-only-rootfs, I have overlays for /var/spool/, /var/cache and /var/lib08:39
LetoThe2nderbo: really overlays, or rather just tmpfs mounts?08:40
erbomount 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
fbreerbo: My idea is to support a factory reset which throws all done system updates over board08:40
erbothat's an extra overlay I added for convenience08:41
fbreerbo: therefore everything coming from an update must be in the upper overlay filesystem.08:41
LetoThe2nderbo: did you add that, or does meta-raspberrypi bring that?08:41
erbofbre: ah, so you want changes to be persistent, but in an overlay so it can be reset?08:41
erboLetoThe2nd: I just added the /home/root overlay, the other stuff is out-of-the-box08:42
fbreerbo: 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
erboLetoThe2nd: the volatile binds are provided by poky/meta/recipes-core/volatile-binds/volatile-binds.bb08:43
LetoThe2nderbo: yup, but every incarntion i've seen so far just goes for tmpfs.08:43
fbreThe use case so to speak is simply to support an easy total factory reset.08:44
erboLetoThe2nd: yes, it use a tmpfs in /var/volatile/ and then use overlays to put parts of the filesystem there.08:45
fbreI think it's not enough to have overlays in a few subdirs08:45
erbofbre: 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 root08:45
fbreerbo: ok, thanx!08:46
escaliontmpfs 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 levelling08:46
escalionMorning all, btw08:47
LetoThe2ndmoinmoin :)08:49
*** runde <runde!sid228344@gateway/web/> has quit IRC08:50
f843d0LetoThe2nd: thanks, I've created wic.vmdk and everything looks fine :)08:50
LetoThe2ndf843d0: :)08:50
*** ustas_ <ustas_!~ustas@> has joined #yocto08:52
*** ustas <ustas!> has quit IRC08:53
*** dreyna <dreyna!> has joined #yocto09:00
*** paulbarker_tmp <paulbarker_tmp!pbarkermat@gateway/shell/> has quit IRC09:00
*** ndec[m] <ndec[m]!ndecmatrix@gateway/shell/> has quit IRC09:00
*** Dracos-Carazza_ is now known as Dracos-Carazza09:01
*** mbulut_ <mbulut_!> has joined #yocto09:03
*** mbulut <mbulut!> has quit IRC09:04
*** f843d0 <f843d0!~f843d0@> has quit IRC09:06
*** ustas_ <ustas_!~ustas@> has quit IRC09:07
*** davidinux <davidinux!> has quit IRC09:09
*** davidinux <davidinux!~davidinux@> has joined #yocto09:09
*** f843d0 <f843d0!~f843d0@> has joined #yocto09:13
*** stacktrust <stacktrust!> has quit IRC09:17
*** hpsy1 <hpsy1!~hpsy@> has quit IRC09:20
*** hpsy <hpsy!~hpsy@> has joined #yocto09:20
*** ustas <ustas!~ustas@> has joined #yocto09:21
*** adam3371 <adam3371!> has quit IRC09:24
*** adam3371 <adam3371!> has joined #yocto09:26
*** adam3371 <adam3371!> has quit IRC09:33
*** rcrudo <rcrudo!> has quit IRC09:33
*** rcrudo <rcrudo!> has joined #yocto09:34
fbre   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
fbreThey write it is a script, the right place to inject the using of an overlay filesystem09:37
*** cp- <cp-!> has joined #yocto09:37
fbreescalion: (y)09:38
escaliontldr; 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 builds09:40
escalionremember you can use a bbappend to add files to a package09:41
escalionfighting a battle myself at the moment. can't get me head around how to make gstreamer1.0-gl to build from
*** rcrudo <rcrudo!> has quit IRC09:44
*** rcrudo <rcrudo!> has joined #yocto09:46
fbreescalion: Can you tell me the path to oe-core in the yocto/sources dir?09:48
fbreescalion: Do you mean yocto/sources/meta-openembedded/meta-oe/recipes-core?09:50
escalionpoky uses this one09:51
escalionfound the answer to my issue, needed to add wayland to distro_features09:58
escalionSomething so simple yet crippling xD09:59
escalionfbre, did that help btw?09:59
escalionor was there something more specific you was trying to achieve?09:59
fbreescalion: 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
fbreescalion: you know, I'm looking for a script which mounts the root filesystem. I want to change it to mount an overlay fs instead10:03
fbreI suspect it is somewhere in the corner of files where yocto defines the initramfs init stuff10:04
escalionyou mean here?
fbreescalion: yeah, I get the feeling I'm getting closer to it10:08
fbreIt's all very complicated and I'm drowning in the flood of scripts10:09
*** rcrudo <rcrudo!> has quit IRC10:12
*** rcrudo <rcrudo!> has joined #yocto10:12
escalionbreak it down, its not as complicated as it looks10:15
*** sagner <sagner!~ags@2a02:169:3df5::edf> has quit IRC10:17
RPsno: FWIW that patch I hacked up broke all the esdks in automated testing so its not quite right10:18
*** rcrudo <rcrudo!> has quit IRC10:20
*** dreyna <dreyna!> has quit IRC10:21
*** rcrudo <rcrudo!> has joined #yocto10:22
fbreWhat is the master script of those initrdscripts? I don't get it. Script looks promising but too hard to understand its content10:25
snoRP: my test still in progress but looks good so far10:26
RPfbre: its an init script so its installed by updated-rc.d and run through the init system10:28
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:29
fbreIs it poky/meta/recipes-core/initrdscripts/initramfs-framework/init ?10:30
*** mbulut_ <mbulut_!> has quit IRC10:31
*** pbb <pbb!> has quit IRC10:32
RPfbre: more likely the main image init system would call mountall.sh10:32
RPfbre: you have two images and two init systems, first the initramfs , then the main image10:32
*** pbb <pbb!> has joined #yocto10:32
*** sagner <sagner!> has joined #yocto10:35
*** rcrudo <rcrudo!> has quit IRC10:41
*** rcrudo <rcrudo!> has joined #yocto10:41
*** rcrudo <rcrudo!> has quit IRC10:45
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto10:46
*** malrak <malrak!50ff069b@> has joined #yocto10:47
*** rcrudo <rcrudo!> has joined #yocto10:47
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC10:56
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto10:58
*** gtristan <gtristan!~tristanva@> has quit IRC11:08
escalionfbre: you can add an overlay at the point however. Just add the declarations after line 20. Unless you need the overlay to be available in the initramfs11:10
escalionyou could also use rc system to add overlay11:11
fbreOK, 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@> has quit IRC11:14
*** gtristan <gtristan!~tristanva@> has joined #yocto11:18
*** nslu2-log_ <nslu2-log_!> has joined #yocto11:21
*** nslu2-log <nslu2-log!> has quit IRC11:23
*** nslu2-log_ is now known as nslu2-log11:24
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto11:26
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC11:32
*** davidinux <davidinux!~davidinux@> has quit IRC11:36
*** davidinux <davidinux!> has joined #yocto11:38
*** gaston53 <gaston53!669cfbbb@> has joined #yocto11:38
gaston53does yocto support libssl ?11:38
gaston53PaowZ so openssl recipe will add libssl package11:42
*** berton <berton!~berton@> has joined #yocto11:42
qschulzgaston53: yes11:42
gaston53qschulz just a question, can I only add libssl package without any other packages related to openssl ?11:43
snoRP: seems because of your patch modifies OECORE_NATIVE_SYSROOT which is originally set by toolchain-scripts.bbclass11:44
qschulzgaston53: if a package depends on another package, it'll be pulled in anyway11:45
qschulzgaston53: 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 with11:45
gaston53qschulz okey thanks11:46
*** ustas <ustas!~ustas@> has quit IRC11:48
RPsno: so it has the wrong value?11:50
* sno nods11:50
snoMaybe that is the conflict I dicovered - I don't really understand the entire ecosystem yet11:50
*** goliath <goliath!> has quit IRC11:52
*** ustas_ <ustas_!~ustas@> has joined #yocto11:59
RPsno: I've tried another tweak in master-next12:02
malrakIs 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
RPmalrak: you should just be able to override the bsp12:03
malrakYou mean by e.g. not using
malrakRP: You mean by e.g. not using
RPmalrak: I don't know. You can usually override pretty much any setting12:11
malrakRP: so my main problem is as follows, 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 sources12:15
*** ndec is now known as ndec|away12:17
snoRP: is probably not that wrong12:19
RPmalrak: I think it should only touch fragments its told to. zeddii probably can point more specifically if/as/when he's around12:20
snoRP: and the openssl / buildtools-tarball is a seond approach12:20
RPsno: its isn't correct. buildtools just overwrites that12:21
snoRP: yes, the openssl parts12:21
RPsno: no, it replaces the entire environment script12:21
snoRP: but when layers add stuff into ${D}${SDKPATHNATIVE}/... - they are kept12:22
snoI see the files :D12:22
snosdk$ ls -l buildtools/sysroots/x86_64-pokysdk-linux/environment-setup.d/12:23
snototal 812:23
sno-rw-r--r-- 1 sno sno  73 Aug  7 13:07 openssl.sh12:23
sno-rw-r--r-- 1 sno sno 229 Aug  7 13:07 sds.sh12:23
*** jkimblad <jkimblad!> has joined #yocto12:24
*** ericch <ericch!> has joined #yocto12:25
RPsno: 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 breaks12:26
snoRP: yes, that is true and was done to show up the conflict between the ${SDKPATHNATIVE}/environment-setup.d/*.sh and buildtools/environment-setup12:28
snoRP: I have no sane idea to fix that and I don't knwo why there're incompatible information12:29
RPsno: I *cannot* accept patches that break things12:31
snoRP: I also see that cmake-nativesdk installs into a different path than openssl-nativesdk12:31
*** paulg <paulg!> has joined #yocto12:31
snoRP: agreed - you should not :D12:31
*** escalion_ <escalion_!> has joined #yocto12:31
snoRP: I sent it to have a basement to discuss which of both (existing) ways is wrong12:32
snoRP: and maybe you now see why cannot use OECORE_NATIVE_SYSROOT12:32
RPsno: quite frankly, no :/12:33
RPsno: 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 things12:34
*** escalion <escalion!> has quit IRC12:34
snoRP: that's not my intention - apologies for this12:35
*** escalion_ <escalion_!> has quit IRC12:36
*** gtristan <gtristan!~tristanva@> has quit IRC12:37
*** kroon <kroon!~kroon@> has quit IRC12:38
*** gaston53 <gaston53!669cfbbb@> has quit IRC12:41
snoRP: I try to explain better ... give me a few minutes (I try to figure out what is the right way)12:43
snoRP: cmake installs nativesdk related files into ${SDKPATHNATIVE}/environment-setup.d via
snoRP: cmake-native install into ${D}${base_prefix}/environment-setup.d/ via
snoRP: openssl-nativesdk does it similar to cmake-nativesdk -- but only the one of cmake-native is included in the script generated by toolchain-scripts.bbclass12:43
snoRP: all I want is to understand how it is meant to add files to sdk to configure for local enhancements12:43
snoRP: So please apologize the patches felt being pushed (harder) - that wasn't intentional12:44
RPsno: I don't really understand why we'd have a cmake-native environment-setup.d :(12:47
snoRP: precisely - me neither12:47
snoRP: I understand that the patch breaks things and I'm interested in fixing it - not getting it pushed12:48
RPsno: which SDKMACHINE are you using?12:49
snoRP: 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.d12:50
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto12:52
snoRP: SDKMACHINE=x86_6412:52
malrakRP: 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 configs12:53
*** Bunio_FH <Bunio_FH!> has joined #yocto12:55
*** mattsm <mattsm!> has quit IRC12:56
*** maudat <maudat!> has joined #yocto12:58
*** tgamblin <tgamblin!> has quit IRC13:04
*** tgamblin <tgamblin!> has joined #yocto13:05
snoRP: is my confusion a bit clearer to you?13:06
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/> has quit IRC13:06
RPsno: yes, a little. I think we perhaps start by deleting the cmake-native sdk bits...13:08
snoRP: :D13:08
snoRP: 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, too13:10
RPsno: so you're trying to use this in the eSDK?13:12
snoRP: yes, I'm trying to use this in eSDK13:13
snoRP: 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 steps13:14
RPsno: so there is something wrong with the eSDK environment. I then wonder why all the eSDK tests pass :/13:15
*** mattsm <mattsm!> has joined #yocto13:15
snoRP: maybe it's not used much  ¯\_(ツ)_/¯13:16
snoRP: it was very difficult to find examples :)13:16
RPsno: but we do have tests which we run regularly13:18
snoRP: but what do they expose into the environment-setup.d/*.sh ?13:18
snoit's only that - everything else seems to be very sane13:18
RPso it suggests we have a gap in the testing. I'd be a lot happier if I could show problems in the tests13:18
snoRP: I fully agree - but I do not understand the issue enough to create a sane test for that13:19
*** matthewzmd <matthewzmd!> has joined #yocto13:19
*** malrak <malrak!50ff069b@> has left #yocto13:20
snoRP: is there someone else beside you who can ''guide'' me to create such a test? moto-timo maybe?13:28
*** hpsy <hpsy!~hpsy@> has quit IRC13:30
*** hpsy <hpsy!~hpsy@> has joined #yocto13:30
RPsno: esdk experts are bluelightning and myself. A few people could probably help with sdk tests but I don't know who if anyone has time13:40
snoRP: when you know that someone has a tuit, please remind this issue13:45
RPsno: I am looking at it locally a little more13:46
snoRP: thanks13:46
*** ustas <ustas!~ustas@> has joined #yocto13:48
*** ustas_ <ustas_!~ustas@> has quit IRC13:48
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/> has joined #yocto14:03
f843d0Hello 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/ 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@> has joined #yocto14:16
RPsno: I do now understand what you mean about all this. I am however struggling to see the correct way to fix it14:19
*** PaowZ_ <PaowZ_!~Vince@> has quit IRC14:26
*** PaowZ_ <PaowZ_!~Vince@> has joined #yocto14:26
*** Konsgnx <Konsgnx!> has joined #yocto14:36
*** rcw <rcw!~rcw@> has joined #yocto14:40
snoRP: no worries - that's all I wanted to reach at the first step and still apologizing for how I did it14:41
*** ibinderwolf <ibinderwolf!> has quit IRC14:45
RPsno: 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 twice14:47
*** sukbeom <sukbeom!~sukbeom@> has joined #yocto14:50
*** matthewzmd <matthewzmd!> has quit IRC15:01
*** matthewzmd <matthewzmd!> has joined #yocto15:01
*** escalion <escalion!> has joined #yocto15:02
RPsno: basically my conclusion is you may need to add environment-setup to -natives for eSDK and to -nativesdk for SDK15:05
RPThe code is sourcing the right things but buildtools does need improving to use these scripts in a way which doesn't break eSDK15:06
snoRP: I give it a try and will report15:09
RPsno: I've written up a summary of what I found and sent to the list15:18
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/> has quit IRC15:18
snoRP: cool, thanks15:18
*** Bunio_FH <Bunio_FH!> has quit IRC15:23
*** sgw1 <sgw1!> has joined #yocto15:36
*** pbb <pbb!> has quit IRC15:44
*** gtristan <gtristan!~tristanva@> has joined #yocto15:45
*** davidinux <davidinux!> has quit IRC15:47
*** pbb <pbb!> has joined #yocto15:49
*** davidinux <davidinux!> has joined #yocto15:49
*** dreyna <dreyna!> has joined #yocto15:53
*** davidinux <davidinux!> has quit IRC15:54
*** davidinux <davidinux!~davidinux@> has joined #yocto15:54
*** f843d0 <f843d0!~f843d0@> has quit IRC15:56
kergothhuh, 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 emitted16:05
kergoththats 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
kergothnot sure if i need to do that anyway, but it's a clear bug. i'll open an issue16:07
kergothalso looks like libtool-cross and qemuwrapper-cross don't actually inherit cross, so aren't excluded by removing cross from COPYLEFT_RECIPE_TYPES16:08
RPkergoth: cross doesn't actually work for anything not gnu :(16:09
*** mckoan is now known as mckoan|away16:09
RPkergoth: it really should be called cross-gnu or something16:09
kergothah, 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
kergothmakes sense16:11
kergothif that's the case it'd probably be worth splitting the class up. rename the autotools-specific portion and retain a common core16:12
*** fl0v0 <fl0v0!> has quit IRC16:14
*** meow` <meow`!~sbourdeli@> has joined #yocto16:15
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has quit IRC16:20
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC16:37
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC16:38
*** rob_gries <rob_gries!~rob@> has joined #yocto16:40
rob_griesWhat 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@> has quit IRC16:45
RPkergoth: I don't remember the issue, I know I found it much safer to not use it for anything that wasn't binutils/gcc/gdb16:48
*** ustas <ustas!~ustas@> has quit IRC16:49
*** dev1990 <dev1990!> has quit IRC16:50
*** kaspter <kaspter!~Instantbi@> has joined #yocto16:53
*** ustas_ <ustas_!~ustas@> has joined #yocto16:55
*** escalion <escalion!> has quit IRC16:57
*** sagner <sagner!> has quit IRC17:07
*** vineela <vineela!vtummala@nat/intel/x-hajunlbucbnlwrtq> has joined #yocto17:19
*** mattsm <mattsm!> has quit IRC17:22
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto17:26
*** mattsm <mattsm!> has joined #yocto17:26
*** rcrudo <rcrudo!> has quit IRC17:27
tlwoerneri need to use a native objcopy as part of the commands used to create my own image type17:43
tlwoernerobjcopy comes from binutils17:43
tlwoernerbut the binutils recipe explicitly deletes the ${bindir} when doing a do_install_class-native17:43
RPtlwoerner: those are assumed to come from the host17:44
RPalthough perhaps little uses objcopy17:44
tlwoernerRP: oh, okay. sounds good17:44
RPtlwoerner: binutils-native is mainly for libbfd-native17:44
RPsno: I think I have a patch which at least might improve some of this mess...17:47
tlwoernerin 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
tlwoernerthere is: do_image_<myimage>[cleandirs] but no do_image_<myimage>[cleanfile]18:02
tlwoerneri guess i'll just do a do_clean_append(){}?18:03
RPtlwoerner: shouldn't you be installing it via the deploydir mechanism and hence it could be autocleaned?18:05
tlwoernerRP: ah, so no manipulating files in ${DEPLOY_DIR_IMAGE} directly then? ;-)18:08
RPtlwoerner: not recommended18:08
*** sukbeom <sukbeom!~sukbeom@> has joined #yocto18:09
snoRP: cool18:11
tlwoernerRP: 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 guess18:12
RPtlwoerner: its fine to consume from DEPLOY_DIR_IMAGE, just don't write to it18:13
*** sukbeom <sukbeom!~sukbeom@> has quit IRC18:13
tlwoernerRP: perfect! thanks :-)18:14
*** stacktrust <stacktrust!> has joined #yocto18:16
*** ustas_ <ustas_!~ustas@> has quit IRC18:20
JPEWRP: Ah, OK. That explaination of the perl bug makes more sense. It's also easier to test for :)18:24
RPJPEW: sorry about the confusion!18:24
JPEWRP: No problem; did you have a build where it was in the non-arch directory?18:24
zeddiiaha. nice, my .config analysis enhancement is already getting me fixup patches :D18:25
RPJPEW: no, that is the build I've never found :/18:25
*** sukbeom <sukbeom!~sukbeom@> has joined #yocto18:25
JPEWRP: Got it18:25
*** ustas <ustas!> has joined #yocto18:26
*** sukbeom <sukbeom!~sukbeom@> has quit IRC18:32
*** gsalazar <gsalazar!5e3ce511@gateway/web/cgi-irc/> has quit IRC18:35
*** Jebee <Jebee!> has joined #yocto18:40
*** sukbeom <sukbeom!~sukbeom@> has joined #yocto18:42
JebeeIm 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
JebeeOr at least clean everything all the way so that it will attempt it again.18:42
JebeeI 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
zeddiifence post ? you are on a really old release then. I abandoned that code due to complexity.18:43
JebeeIt is a build that i received from a vendor for their parts. It is based on thud18:43
JebeeLatest patch was Feb 26 2019 ship /etc/drirc in mesa-megadriver18:44
JebeeIs there a way to clear these "fence posts"? a folder or file that is stored somewhere?18:46
zeddiiit'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@> has quit IRC18:47
zeddiiactually, if it is looking for fence posts. It should be thud. I just checked and had already removed htat.18:47
*** berton <berton!~berton@> has quit IRC18:48
JebeeWhats a good way to check exactly which build / rev I'm using?18:48
*** berton <berton!~berton@> has joined #yocto18:49
zeddiisec. 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
champagnegany 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 ;p18:50
zeddiiyah. 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
JebeeHrmm, its strange because it seems to set that post even if the patching fails.18:54
JebeeDo 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
zeddiidunfell (the latest release), is a good candidate. since it is LTS as well.18:57
zeddiiJebee: I don't suppose the layers / kernel for this are public ? I could run a couple of quick tests if they were.18:58
zeddiior 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
JebeeI'm trying the rebuild currently. I'll pastebin the error as soon as I can get it to come up again.19:00
zeddiicool. I can very likely get you moving. I'll just have to swap some things back into my memory :D19:00
*** Jebee_laptop <Jebee_laptop!a5e1d0b2@> has joined #yocto19:06
Jebeeha, 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
zeddiidetached head ? ouch. they are doing strange things.19:18
zeddiiif 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
zeddiithen look in the .git/ directory19:19
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC19:23
JebeeSo the .git directory is there.19:27
zeddiiis kgit-s2q.last there ? it pretty much has to be, since that is what dumps the message you are seeing.19:28
Jebee_laptopHere is a pastebin of when patch actually fails.19:29
zeddiiso the patch isn't right for that kernel. but that isn't one of your patches from the SRC_URI ?19:30
Jebeethat 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
zeddiiok, cool, but it isn't valid for where it is being applied, so you need to fixup the patch itself.19:32
JebeeRight, 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
Jebeewould that work, without having to touch the patch?19:33
zeddiiyou've got some bad paths in the patch, for the actual files being patched:19:33
zeddiithat shouldn't be there, if its in the patch.19:33
zeddiidoing a dance with the source directory, I'm not so sure it'd work out.19:34
Jebeeso 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
JebeeI need to figure out why my root kernel directory differs from the one that is in wnc/kernel-source/19:39
zeddiiyour build is using the right directory.19:40
zeddiiit's the patch that is garbage (to be blunt).19:40
zeddiiunless I'm misreading it, that's a completely invalid file path specification.19:40
*** nslu2-log <nslu2-log!> has quit IRC19:40
zeddiiand luckily, it isn't my older tools that are the problem. I'm glad about that at least.19:41
JebeeI 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@> has quit IRC19:42
zeddiiyes. when it sees that file, it knows that's where it left off.19:43
zeddiiif you remove it, it'll start over.19:43
Jebeedeleting the entire tmp-glibc/* contents should have the same effect correct?19:43
zeddiiif 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@> has joined #yocto19:50
*** hpsy <hpsy!~hpsy@> has quit IRC19:51
*** dreyna_ <dreyna_!> has joined #yocto19:52
*** Jebee_laptop <Jebee_laptop!a5e1d0b2@> has quit IRC19:54
*** dreyna_ <dreyna_!> has quit IRC19:56
*** dreyna_ <dreyna_!> has joined #yocto19:56
JebeeSo there is no kgit-s2q file in the kernel-source folder.20:02
zeddiithat is what is doing the patching, it's a tool. the file it is checking is kernel-source/.git/kgit-s2q.last20:03
Jebeeright, understood. I just mean there is nothing in that folder with the name kgit-sq2* , let me double check.20:07
zeddiithere's no other way that message can come out.20:07
zeddiiso without being able to run something here, there's nothing more I can easily suggest.20:07
*** ustas_ <ustas_!~ustas@> has joined #yocto20:14
JebeeThanks zeddii, ill keep poking around, you've been a huge help20:14
*** ustas <ustas!> has quit IRC20:15
rob_griesDoes 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
Jebeehi rob :)  i'm using the same or a very similar bsp put together by the exact same vendor :)20:18
rob_griesDo you happen to be using the APQ8053 as well?20:19
JebeeNo, I'm  using a SA2150 AP and a SA415M modem.20:20
rob_griesI 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
RProb_gries: having heard about some of what they do, I'd agree with that :/20:21
JebeeIts just awful, and the support is even worse.20:21
RPcan you turn off multilibs?20:21
rob_griesRP: I can if I can solely use lib32 binaries. Some of Qualcomm's proprietary bits only work properly when built in 32Bit.20:23
RProb_gries: I can see that being trickier to arrange20:24
RProb_gries: just thought I'd mention just in case20:24
rob_griesRP: 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!> has quit IRC20:27
Jebeerob_gries how are you including the -dev libs? is your goal to have them in the SDK ?20:27
rob_griesJebee: So far I've tried two methods -- modifying meta-qti-bsp/recipes-products/images/apq8053/ 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_griesJebee: 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
Jebeehrmm, and neither of those methods work as you expect?20:32
RProb_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 easier20:34
*** ustas_ <ustas_!~ustas@> has quit IRC20:34
RProb_gries: I was wondering if you could just blacklist the problematic dev packages somehow too20:34
Jebeezeddii: I found it, its in poky/.git/kgit-s2q.last20:35
rob_griesJebee: Unfortunately no. Method one ( 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_griesRP: that would be fantastic. however wouldn't that result in both lib32 and standard versions being blacklisted?20:36
Jebeejust 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
Jebeein the local.conf file?20:38
RProb_gries: they have separate -dev package names don't they?20:39
rob_griesJebee: Yes20:40
rob_griesRP: Also, yes20:40
*** ustas <ustas!> has joined #yocto20:42
rob_griesRP: I'm trying the blacklist approach20:45
rob_griesRP: Following this from the manual --
rob_griesRP: I'm building with the PNBLACKLIST variables set... Fingers crossed!20:49
JPEWIs there any reason dbus is 1.12.x when 1.13.x has been released?20:58
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC20:59
rob_griesRP: Dang. That didn't work. If you're interested here are my build logs and my blacklist snippet from local.conf --
JPEWAh, odd-even releases21:03
RProb_gries: you'd need to do it at the package level, not PN21:03
*** Konsgnx <Konsgnx!> has quit IRC21:05
rob_griesRP: 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!> has quit IRC21:08
RProb_gries: I don't think its easy to do. If it were me, I'd hack the install_complementary() function in meta/lib/oe/ just to skip the ones you don't want21:11
RProb_gries: try that :)21:12
rob_griesRP: I'll give it a shot :) That's in Jethro, right?21:15
RProb_gries: er, no idea. That is rather elderly21:15
rob_griesRP: Yeah... This is what the vendor give us :-/21:16
*** sakoman <sakoman!> has quit IRC21:19
RProb_gries: how old is that hardware?21:19
JebeeSo 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_griesRP: Not that old... maybe 2 years old?
RProb_gries: based on a release series we stopped updating in Dec 2016 :/21:21
rob_griesRP: I have a suspicion that QCOM flogs it's older mobile targeted silicon to IoT when it stops being profitable.21:22
*** sakoman <sakoman!> has joined #yocto21:22
RProb_gries: sounds possible21:26
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC21:28
rob_griesRP: 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_griesRP: this is what I tried in local.conf -- PACKAGE_EXCLUDE_COMPLEMENTARY += " gstreamer-1.0-dev libpng-dev libdb-dev libgmp-dev"21:43
RProb_gries: sounds right. There are a lot of ways this might not work unfortunately :(21:46
RProb_gries: Its 11pm on a Friday here and I really need to step away from the computer, sorry21:47
rob_griesRP: I get it, it's nearly 6PM here. Thanks for your help, I appreciate it.21:48
rob_griesRP: Enjoy your weekend!21:48
khemRP: finally fixed the ppc issue I am hoping, please stage the patch I sent moments ago22:21
khemRP: I think we should drop this ppc32 !@#$ from core22:22
RPkhem: already running on the autobuilder :)22:22
khemI spend 2.5 days debugging this issue22:22
RPkhem: thanks, I know the feeling with things like that...22:22
*** sakoman <sakoman!> has quit IRC22:23
khemglibc got many changes where things broke so bisecting was not an option22:23
khemand upstream only cares for ibm ppc22:24
RPkhem: ouch. Sounds like it may be an interesting one for issues as it gets wider testing...22:24
khemRP: perhaps we should think of replacing it with ppc64 and ask openpower to support us22:25
* RP really steps away22:25
RPkhem: I'd be fine with that but doesn't cisco use the older ppc?22:25
khemyeah they do anyone from Cisco here listening ? please share the pain22:26
*** sakoman <sakoman!> has joined #yocto22:26
RPkhem: victor is helpful if you email him22:26
khemgood idea, I will22:26
khemsince ppc always eats up time along with mips sometimes but mips I get paid for :)22:27
*** matthewzmd <matthewzmd!> has quit IRC22:33
*** goliath <goliath!> has joined #yocto22:38
armpityou get paid?22:38
armpitwe should drop ppc32 for ppc64 ; )22:39
*** leon-anavi <leon-anavi!~Leon@> has quit IRC22:49
*** camus1 <camus1!~Instantbi@> has joined #yocto22:52
*** kaspter <kaspter!~Instantbi@> has quit IRC22:54
*** camus1 is now known as kaspter22:54
*** vineela <vineela!vtummala@nat/intel/x-hajunlbucbnlwrtq> has quit IRC23:03
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto23:03
khemarmpit: heh I mean my employer still uses mips32 so indirectly, I am scratching own itch with mips3223:04
*** MiskaX <MiskaX!v0liw25rff@2001:2060:72::3> has quit IRC23:20
*** MiskaX <MiskaX!> has joined #yocto23:27
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC23:32
*** ericch <ericch!> has quit IRC23:33
*** goliath <goliath!> has quit IRC23:33
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto23:37
*** rcw <rcw!~rcw@> has quit IRC23:44
*** ustas <ustas!> has quit IRC23:47
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC23:50
*** comptroller <comptroller!> has quit IRC23:51
*** NiksDev <NiksDev!~NiksDev@> has quit IRC23:59
*** comptroller <comptroller!> has joined #yocto23:59

Generated by 2.17.2 by Marius Gedminas - find it at!