Monday, 2019-01-14

*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC00:03
*** xperia64 <xperia64!> has joined #yocto00:10
*** ant_home <ant_home!~ant__@> has quit IRC00:14
*** lazyape <lazyape!> has joined #yocto00:21
*** comptroller <comptroller!> has quit IRC00:23
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has joined #yocto00:24
*** comptroller <comptroller!> has joined #yocto00:27
*** gtristan_ <gtristan_!~tristanva@> has joined #yocto00:43
*** dev1990 <dev1990!> has quit IRC01:09
*** awe00 <awe00!~awe00@unaffiliated/awe00> has quit IRC01:15
*** paul_99_ <paul_99_!~paul@> has joined #yocto01:26
*** paul_99 <paul_99!~paul@> has quit IRC01:26
*** BlauskaerM <BlauskaerM!~Fever@> has quit IRC01:33
*** BlauskaerM <BlauskaerM!~Fever@> has joined #yocto01:40
*** gtristan_ <gtristan_!~tristanva@> has quit IRC02:20
*** learningc <learningc!> has joined #yocto02:38
*** xperia64 <xperia64!> has quit IRC02:43
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has quit IRC02:47
*** kanavin <kanavin!~kanavin@> has quit IRC02:59
*** kanavin <kanavin!~kanavin@> has joined #yocto03:00
*** xperia64 <xperia64!> has joined #yocto03:13
*** robbawebba <robbawebba!~rob@> has joined #yocto03:17
*** User__ <User__!> has joined #yocto03:23
*** learningc <learningc!> has quit IRC03:27
*** Willy-- <Willy--!~william@> has quit IRC03:40
*** geissonator <geissonator!> has joined #yocto03:49
*** geissonator <geissonator!> has quit IRC04:09
*** onlyesterday16 <onlyesterday16!~onlyester@> has joined #yocto04:18
*** learningc <learningc!> has joined #yocto04:24
*** saraf_ <saraf_!~a_saraf@> has quit IRC04:25
*** User__ <User__!> has quit IRC04:27
*** comptroller <comptroller!> has quit IRC05:12
*** dv_ <dv_!~dv@> has quit IRC05:23
*** learningc <learningc!> has quit IRC05:27
*** learningc <learningc!> has joined #yocto05:28
*** dv_ <dv_!~dv@> has joined #yocto05:37
*** hamis <hamis!~irfan@> has joined #yocto05:52
*** User__ <User__!> has joined #yocto05:58
*** learningc <learningc!> has quit IRC06:00
*** AndersD <AndersD!> has joined #yocto06:08
*** sno <sno!> has quit IRC06:15
*** AndersD <AndersD!> has quit IRC06:22
*** AndersD <AndersD!~AndersD@> has joined #yocto06:23
*** sno <sno!~sno@2a01:598:b101:28bc:7576:fcb2:44be:3a28> has joined #yocto06:41
*** cvasilak <cvasilak!> has joined #yocto06:41
*** jobroe <jobroe!~manjaro-u@> has joined #yocto06:44
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:51
*** Carton__ <Carton__!~jo@2a02:120b:7ff:51a0:f093:4a7d:8d11:17ae> has joined #yocto07:00
*** yann <yann!> has quit IRC07:18
*** User__ <User__!> has quit IRC07:50
*** learningc <learningc!> has joined #yocto07:52
*** learningc <learningc!> has joined #yocto07:53
*** [Sno] <[Sno]!~sno@2a01:598:b101:28bc:3c5c:c5a3:8aa2:2a3d> has joined #yocto07:54
*** sno <sno!~sno@2a01:598:b101:28bc:7576:fcb2:44be:3a28> has quit IRC07:54
*** lusus <lusus!~lusus@> has joined #yocto07:57
*** frsc <frsc!~frsc@2003:a:e7a:6200:246c:2a8b:f45a:a33d> has joined #yocto08:02
*** fl0v0 <fl0v0!> has joined #yocto08:11
*** toanju <toanju!~toanju@> has joined #yocto08:15
*** ant_work <ant_work!> has joined #yocto08:15
*** [Sno] <[Sno]!~sno@2a01:598:b101:28bc:3c5c:c5a3:8aa2:2a3d> has quit IRC08:20
*** mckoan|away is now known as mckoan08:22
mckoangood morning08:22
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto08:24
*** sno <sno!~sno@2a01:598:b101:28bc:3120:6449:6f5:a635> has joined #yocto08:27
*** agust <agust!> has joined #yocto08:27
*** nighty- <nighty-!> has quit IRC08:28
*** lucaceresoli <lucaceresoli!> has joined #yocto08:29
*** yann <yann!> has joined #yocto08:30
yoctiNew news from stackoverflow: Yocto toolchain build fail <>08:31
*** TobSnyder <TobSnyder!> has joined #yocto08:41
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:49
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC08:49
*** thannoy_ <thannoy_!> has joined #yocto08:51
*** thannoy <thannoy!> has quit IRC08:54
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:03
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto09:10
*** Amit_T <Amit_T!~amit@> has joined #yocto09:16
Amit_THi, while building gstreamer 1.14.0 , facing this issue "autoreconf: failed to run autopoint: No such file or directory09:19
Amit_Tautoreconf: autopoint is needed because this package uses Gettext09:19
Amit_TERROR: autoreconf execution failed."09:19
Amit_Tcan anyone point me out how it can resolved ?09:20
*** aleblanc <aleblanc!~aleblanc@2607:f2c0:95d9:8500:71cc:17fd:71b4:e9ab> has quit IRC09:20
*** saraf__ <saraf__!~a_saraf@> has joined #yocto09:20
*** aleblanc <aleblanc!> has joined #yocto09:21
*** csanchezdll <csanchezdll!> has joined #yocto09:21
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto09:23
*** cquast <cquast!~cquast@> has joined #yocto09:31
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:33
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC09:37
*** zagor <zagor!~zagor@rockbox/developer/Zagor> has joined #yocto09:45
RPkanavin: any news on perl? I think we may need to single thread this until we resolve the problem09:47
RPkanavin: too many AB failures :(09:47
*** Bunio_FH <Bunio_FH!> has joined #yocto09:55
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto09:55
*** csanchezdll <csanchezdll!> has quit IRC10:18
*** csanchezdll <csanchezdll!> has joined #yocto10:18
kanavinRP: I will send a patch in a moment10:24
*** toanju <toanju!~toanju@> has quit IRC10:25
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto10:34
RPkanavin: thanks!10:35
*** rburton <rburton!> has joined #yocto10:41
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has joined #yocto10:43
*** comptroller <comptroller!> has joined #yocto10:43
*** berton <berton!~berton@> has joined #yocto10:45
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC10:48
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto10:48
*** awe00 <awe00!~awe00@unaffiliated/awe00> has joined #yocto10:49
*** berton <berton!~berton@> has quit IRC10:52
*** berton <berton!~berton@> has joined #yocto10:55
kanavinRP: hope that's the last of them :-/10:56
*** interruptguy <interruptguy!> has joined #yocto10:59
*** zagor <zagor!~zagor@rockbox/developer/Zagor> has quit IRC11:01
*** zagor <zagor!~zagor@rockbox/developer/Zagor> has joined #yocto11:02
*** saraf__ <saraf__!~a_saraf@> has quit IRC11:04
RPkanavin: we'll see!11:14
RPrburton: any thoughts on -next?11:22
* rburton looks11:23
rburtondrop the qemu/wic patch11:24
*** comptroller <comptroller!> has quit IRC11:25
rburtonRP: apart from that, fine by me11:26
RPrburton: I already did! :) thanks11:27
*** saraf__ <saraf__!~a_saraf@> has joined #yocto11:28
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:31
*** sno <sno!~sno@2a01:598:b101:28bc:3120:6449:6f5:a635> has quit IRC11:32
rburtonreboot time bbiab11:32
*** rburton <rburton!> has quit IRC11:33
*** rburton <rburton!> has joined #yocto11:36
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has left #yocto11:39
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has joined #yocto11:39
*** comptroller <comptroller!> has joined #yocto11:41
*** malanecora <malanecora!b23cc82c@gateway/web/freenode/ip.> has joined #yocto12:00
malanecoraHi everyone!12:00
malanecoraI'm trying to use the openssl1.1.0 recipe instead of openssl1.0.1 in Yocto Rocko, as consequence lots of packages that depend on openssl1.0.1 fail to build...12:02
malanecoraSomeone has experienced something similar? Is there a known patch to fix this (I haven't found it...)?12:03
*** sno <sno!> has joined #yocto12:04
kanavinmalanecora: sadly openssl has botched the transition, 1.1 and 1.0 series are API incompatible12:19
kanavinmalanecora: the easiest way is to upgrade to thud, where everything (at least in oe-core) has transitioned to 1.1, and should just work12:20
malanecorathose are terribly bad news... :(12:20
kanavinwhy do you want 1.1.0?12:21
malanecoraIt's a system requirement, I'm not sure but maybe openjdk-8 has something to do here...12:23
malanecoraI'm afraid some previous work could be lost "upgrading" to Thud12:23
kanavinyou should upgrade continously, otherwise you'll end up in situations like this12:24
kanavin* cue expensive Yocto consultants12:24
malanecoraYes, now I know...haha12:25
LetoThe2ndoO( if you're afraid of losing worktime due to new versions, software development probably is not for you )12:25
*** saraf_ <saraf_!~a_saraf@> has joined #yocto12:25
LetoThe2ndkanavin: cheap ones too?12:25
*** saraf__ <saraf__!~a_saraf@> has quit IRC12:25
kanavincheap Yocto consultants do not exist :)12:25
rburtonmalanecora: i'd double check where the requirement actually is.  you might be fine with 1.012:26
malanecoraLetoThe2nd: I just came across with this project by "heritage"12:27
malanecorarburton: I will, thank you!12:28
LetoThe2ndmalanecora: don't take me too seriously, i know most of the things how one ends up in those situations.12:28
*** cvasilak <cvasilak!> has quit IRC12:31
*** onlyesterday16 <onlyesterday16!~onlyester@> has quit IRC12:33
*** skynet <skynet!91fdde45@gateway/web/freenode/ip.> has joined #yocto12:34
malanecoraLetoThe2nd: don't worry, I don't haha...I'll just check if changing from Rocko to Thud can lead to conflict or on the contrary it is just a straightforward step12:35
malanecorakanavin: btw, thank you too!12:35
skynetHi, how to I force bitbake to rebuild? I manually removed some cache dirs and the deploy dir, but 'bitbake -c cleanall' says there's nothing to do12:35
kanavinskynet: bitbake -c cleansstate <recipe>12:36
LetoThe2ndskynet: "removed some cache dirs" sounds pretty fishy12:36
LetoThe2ndbesides that, see kanavin :)12:36
rburtonskynet: easiest way is bitbake [recipe] -C unpack12:37
tgoodwinSo long as <recipe> isn't human_genome or something like that, skynet.12:37
skynetusing kanavin's hint it just says in the end: NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and all succeeded.12:38
LetoThe2ndtgoodwin: actually, i expect "skynet" to be capable of doing that12:39
rburtonskynet: cleansstate just cleans, you'll need to rebuild the recipe next.12:39
tgoodwinLetoThe2nd: sure it's capable (just please don't ...)12:39
skynetLetoThe2nd: unfortunately T1000 is on vacation ;)12:40
skynetFor instance 'core-image-minimal' such a <recipe>, right?12:42
*** jofr <jofr!~jofr@> has joined #yocto12:44
LetoThe2ndskynet: thats an image recipe. it does not have any real own artifacts, so cleaning and rebuilding it will just reassemble whatever is already there.12:45
rburtonskynet: telling that to rebuild won't cause everything else to rebuild.12:45
malanecoraIs there a "recommended" upgrading way? Or shall I just checkout the desired version branch/tag?12:45
rburtonmalanecora: switch to the right branch, read release notes, make changes.12:46
LetoThe2ndskynet: so if you really want a total full rebuild, wipe your sstate and tmp12:46
skynetWhat should I use for <recipe> then?12:46
rburtonskynet: what do you want to rebuild?12:46
LetoThe2ndskynet: maybe you should start telling us what you *REALLY* want to do.12:47
rburtonif you want to force a clean build of everything, easy way is to delete tmp and sstate.  that's very rare though.  if this is for CI purposes (ie "do a clean build every night") then do the build with a new sstate dir.12:48
*** Carton__ <Carton__!~jo@2a02:120b:7ff:51a0:f093:4a7d:8d11:17ae> has left #yocto12:50
skynetOK, First I had a standard yocto. I called "DISTRO=fsl-imx-wayland MACHINE=imx8mqevk source -b build-wayland" and after that "core-image-minimal". After that I added my own custom layer to yocto following  . After that I wanted to bitbake my new yocto but after both commands as mentioned in the beginning bitbake12:51
skynetSo I manually removed the cache dirs and deploy dirs.12:52
skynetBut bitbake still says there's nothing to do.12:52
LetoThe2ndmaybe your layer jsut has no effect?12:53
skynetThe layer adds a helloworld.c and the recipe for it12:54
LetoThe2ndthat guide is interesting but pretty complicated in some places, easy to get things wrong.12:54
LetoThe2ndwell does that hello world thing compile?12:54
LetoThe2nde.g. bitbake helloworld12:54
rburtonskynet: adding a layer doesn't add it to the image12:54
LetoThe2ndrburton: i suspect that the append is buggy or forgotten. and while that guide is interesting, imho it shows quite some really bad practises.12:55
skynetHmm, where can I find a simple newbie tutorial how to add a simple helloworld program to the yocto system in the right way?12:56
rburtonthe official manual :)12:56
LetoThe2ndskynet: let me explain: that guide shows how to mangle source code into the metadata (bad) and appends a standard image (not exacly bad, but also not good)12:57
LetoThe2ndskynet: its way cleaner to create your own layer with a custom image recipe first, and add something that already exists. just to get into the modification workflow12:57
*** paul_99_ <paul_99_!~paul@> has quit IRC12:58
skynethmm, OK, so it's not good to follow that tutorial12:58
LetoThe2ndskynet: the tutorial is like googling the symptoms of a disease. frightening and misleading for standard people, but might be helpful for a medically trained person.12:59
LetoThe2ndskynet: it has some nice points that can be useful. but certainly not for a beginner.12:59
*** learningc <learningc!> has quit IRC12:59
*** paul_99 <paul_99!~paul@> has joined #yocto12:59
skynetI'm having a look at chapter "3.2.1. Customizing Images Using local.conf" right now (following rburton's hint). Many questions appear :) First one: Where is that local.conf (in which directory)?13:01
skynetCrofton: thank you13:04
LetoThe2ndskynet: by the way, thats 5. of the dornerworks tutorial.13:04
LetoThe2nd(so if you had actually read and followed it by the letter, you would'be known) </SCNR>13:04
skynetlocal.conf is not mentioned at dornerworks13:05
*** lusus <lusus!~lusus@> has quit IRC13:06
*** tprrt <tprrt!~tprrt@> has joined #yocto13:07
LetoThe2ndah yes. its bblayers.conf. my bad then for misreading.13:07
*** cengiz_io <cengiz_io!542c0ee2@gateway/web/freenode/ip.> has joined #yocto13:07
rburtonany tutorial for yocto that doesn't mention local.conf is misguided13:07
LetoThe2ndrburton: hrhr13:07
cengiz_iohello! whenever I modify a recipe with `devtool modify`, my new commit file gets a duplicate sequence number (0001-a.patch 0002-b.patch 0003-c.patch 0001-new_modification.patch). is this intended? how can I correct this?13:09
skynetChapter "3.2. Customizing Images" is written way more complicated than the dornerworks stuff. I don't get it reading it the second time... The good thing of the dornerworks is it just says mkdir this and edit that... but I don't want to complain...13:09
LetoThe2ndskynet: ?13:10
LetoThe2ndskynet:  To add a package to your image using the local configuration file, use the IMAGE_INSTALL variable with the _append operator:13:11
LetoThe2nd     IMAGE_INSTALL_append = " strace"13:11
LetoThe2ndok, to help us improve - what is complicated here?13:11
LetoThe2nd(being serious!)13:11
malanecoraLetoThe2nd: Well, to be fair Yocto itself is quite complicated at beginning! I guess he just has to get used to the system...13:17
skynetwell, after I have managed to run a standard yocto on my eval board, my next aim is to add a simple helloworld.c to the system for having that program on my eval board additionally. My feeling is it's just a couple of files and lines to be added in a few conf files. But scrolling through chapter 3.2 I don't see it clearly in a fast way.13:18
skynetNo doubt the docs are great though I cannot see the quick start. :)13:18
LetoThe2ndmalanecora: not argueing that in the least. but claiming that a roughly 30 line paragraph is more complicated than a multipage how-to-create-your-own-layer-and-custom-compile-recipe is... surprising, to say the least.13:19
LetoThe2ndskynet: *sigh* because it does only *ONE* thing. it add the package "strace" to your image. we want to show you the necessary steps one by one. not all mangled together, like that "tutorial" does.13:19
cengiz_iolet's release some tension by talking about my super simple problem: patch file sequence numbering. how can I re-number patches in a recipe?13:21
malanecoraLetoThe2nd: touché...just saying haha13:21
* cengiz_io hides under desk13:21
LetoThe2ndmalanecora: :-)13:21
*** lusus <lusus!~lusus@> has joined #yocto13:23
LetoThe2ndskynet: once you understood how to add something to your image, you can proceed to creating a custom "something" that is added. thats how it usually is done.13:24
LetoThe2ndcengiz_io: no need to hide, probably just nobody knows.13:24
LetoThe2ndcengiz_io: while devtool is great for some usecases, it still has some rough corners. i wouldn't rule out a bug at all, so you might want to report it through bugzilla (or whatever we use these days)13:25
*** interruptguy <interruptguy!> has quit IRC13:27
*** saraf_ <saraf_!~a_saraf@> has quit IRC13:27
cengiz_ioLetoThe2nd: I don't have the knowledge to decide whether it's a bug or not13:27
*** saraf_ <saraf_!~a_saraf@> has joined #yocto13:28
cengiz_iopatch gets appended to tail of the SRC_URI but the number bugs me13:28
cengiz_ioLetoThe2nd: oh wait. someone already asked it in lists:
*** geissonator <geissonator!~geissonat@> has joined #yocto13:29
LetoThe2ndcengiz_io: :)13:29
*** cvasilak <cvasilak!> has joined #yocto13:34
skynetReading chapter 3.2.1: It says I should use a variable IMAGE_INSTALL_append. Well, but my local.conf does not contain a line whit that variable. What do the docs mean with "use"? Should I insert such line? The it tells it's possible to extend to IMAGE_INSTALL_append_pn-core-image-minimal. Should I do that now or not? You see, it's quite blurry...13:39
skynetI actually need a concrete listing of commands and edit steps for copy'n'paste. Yes, it's good if it's explained what it means. But in the first run I don't want to read the explanation. I just want to use it for now.13:39
LetoThe2ndskynet: "i just want to use" is a good mindset for a doorhandle. for a distribution building system, less so.13:40
LetoThe2ndskynet: so yes, you just insert the line13:40
skynetThis is just my hint from the silly user's point of view ;-) No offending, just friendly meant. Sorry if it's too harsh13:41
LetoThe2ndskynet: i seriously suggest to work through the getting started documentation:
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC13:42
LetoThe2ndskynet: its written the way it is for a reason. after it, you'll have custom layer to add your stuff, and have a general idea of the local.conf file.13:42
skynetThanks for the links! I thing I have something to read now :-)13:42
LetoThe2nd(instead of a radnom bunch of "type this here" snippets, and no clue why they fail afterwards)13:42
* derRichard wonders why poky has -meta-*/ in .gitignore13:43
derRichardwhat is the use case? except that you don't see new files in layers? :(13:43
skynetWell, the schedule wants us to benchmark by using some custom programs on the eval board in a short time. So it would be nice if I had such 'type this here' snippets ;)13:43
LetoThe2ndskynet: then tell the person that gave you the schedule that you don't have the required knowledge, and that you either need longer or somebody else has to do it. thats the real life13:44
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto13:45
skynetno solution ;) I recommend quick start docs for adding plain custom programs instead of reading the full monty13:45
LetoThe2ndskynet: not meaning to be overly harsh either. but reaching out for a really complex product without prior knowledge means either invest time (yor own) or money (for a consultant). and expecting simple copy and paste instructions for exactly your case just is not going to work13:46
LetoThe2ndskynet: alternative option: install debian/ubuntu and just compile in-target13:49
LetoThe2ndskynet: way simpler for a one-of benchmark13:49
* skynet is ordering a round of free beer for the whole chat13:51
skynetOK, thanks! Cheers and thanks13:51
* LetoThe2nd gets drunk on duty13:51
*** Willy-- <Willy--!~william@> has joined #yocto13:54
*** interruptguy <interruptguy!> has joined #yocto13:57
yates_homewhere are the files for kernel-dev specified?13:58
rburtonderRichard: yes, that.  no chance to accidently commit new layers to poky.13:58
yates_homei've smart installed both kernel-dev and kernel-srcdev yet there seems to be files missing in /lib/module/..., e.g., the main module Makefile, which should bin in /lib/module/$(uname -r)/build13:59
yates_homes/should bin/should be/14:00
yates_homein fact the entire build directory is missing14:00
yates_homeand there is no Makefile at all under /lib/modules14:00
yates_homei'm trying to build a LKM on the target14:01
yates_homethe kerne-dev package seems to lacking a lot of files:
*** cengiz_io <cengiz_io!542c0ee2@gateway/web/freenode/ip.> has quit IRC14:07
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has quit IRC14:08
rburtonyates_home: easier to just make a recipe to build the module in bitbake? :)14:09
yates_home"easier" depends on your metric for "easy"... :)14:11
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC14:12
yates_homei'm in the first stage of development, so i'll probably be making lots of blunders and needing to rebuild 100 times a day. you really think bitbaking is faster in this scenario?14:12
RPyates_home: would be for me14:13
RPwrite the recipe once, not have to worry thereafter14:13
yates_homeworry about what? i have to worry about the module src no matter which way i develop.14:14
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto14:14
LetoThe2ndespecially if you have to reflash or upgrade something on the image, you'll accidentially lose your src at least once.14:14
LetoThe2ndspeaking from experience.14:14
zeddiiyates_home. was it you, or someone else that was also just asking this question about a week ago ? you want kernel-devsrc, not kernel-dev14:14
LetoThe2ndand then, you develop out of target :)14:14
rburtonyates_home: on-target building should work, and we test that on the ab, so i'd ask zeddii14:14
rburtonoh thanks zeddii :)14:15
yates_homeyes it was me, and i've installed kernel-devsrc14:15
zeddiieverything you need is definitely there.14:15
zeddiizero doubts about that.14:15
yates_homei still do not have the necessary Makefile, namely, /lib/modules/$(uname -r)/build/Makefile14:15
RPyates_home: it will get built the same way each time and installed in the image - not needing to worry about documenting that or doing it again14:15
zeddiiyates_home, what release are you using ?14:16
yates_homeLetoThe2nd: got that covered - the file is under source control14:16
yates_homezeddii: there's the rub: morty14:16
zeddiiah yes.14:16
zeddiithat's the problem14:16
*** bjobjo <bjobjo!~bjobjo@2a01:79d:3e81:5208::7b0> has joined #yocto14:16
zeddiithe re-worked devsrc wasn't even a glimmer then.14:16
zeddiiyates_home, the souce is under /usr/src/kernel, IIRC14:17
zeddiiin that release.14:17
yates_homeyes, i was just noticing the stuff there.14:17
zeddiimake a symlink from the /lib/modules structure if you have Makefiles looking there.14:17
yates_homeok, let me crunch on that more.14:18
zeddiiand you will need to do a "make ARCH=<your arch> scripts" in that directory to get the reset of the build infrastructure re-created.14:18
yates_homeok, good to know!14:18
*** flying_sausages <flying_sausages!> has quit IRC14:18
yates_homethanks zeddii14:19
bjobjoHi all, I'm wondering about the difference between the docker containers provided by the crops-project - specifically crops/poky and crops/yocto - which one is recommended to use, and in the case of crops/yocto, should one use the -base or the -builder tags?14:21
*** OpenSorceress <OpenSorceress!~opensorce@unaffiliated/screamingbanshee> has joined #yocto14:24
skynetYEAH, there was an image directory "build-wayland" in the yocto project root dir, it's in parallel to directory "downloads" and "sources". I removed that "build-wayland" and called again "bitbake core-image-minimal", and now it rebuilds everything. :-D Big jubilation here!!14:25
* skynet is ordering another round of free beer for the chat14:25
jofrskynet: You do know that there are 240 people in here..? That is A LOT of beer you're buying...14:27
yates_homezeddii: is the ARCH i specify in the make command the result of the "arch" command (armv71 for my target)?14:29
*** zino_ <zino_!> has quit IRC14:29
*** OpenSorceress <OpenSorceress!~opensorce@unaffiliated/screamingbanshee> has quit IRC14:29
*** learningc <learningc!~learningc@> has joined #yocto14:29
skynetjofr: the price of chat beer is cheap, just 4 bytes LOL14:30
yates_homeor should it just be "arm"? that's the closest i see under the arch directory14:30
RPskynet: careful or we might now think we're worthless ;-)14:31
skynethehehe :)14:31
zeddiiyates_home. yes. that should be it.14:32
* zeddii isn't sure how much mileage everything has running natively on an arm target14:32
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC14:33
*** flying_sausages <flying_sausages!> has joined #yocto14:47
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto14:49
*** saraf__ <saraf__!~a_saraf@> has joined #yocto14:54
*** saraf_ <saraf_!~a_saraf@> has quit IRC14:54
*** gtristan_ <gtristan_!~tristanva@> has joined #yocto14:55
*** gtristan_ is now known as gristan14:55
*** gristan is now known as gtristan14:55
*** AndersD <AndersD!~AndersD@> has quit IRC14:57
kanavinyay patchbomb :)15:04
*** la_croix <la_croix!~la_croix@> has quit IRC15:04
RPkanavin: not sure I dare look15:04
*** la_croix <la_croix!~la_croix@> has joined #yocto15:05
kanavinRP: you can read my msg to openembedded-architecture then :)15:09
*** geissonator <geissonator!~geissonat@> has quit IRC15:11
derRichardrburton: ok, got the use case.15:13
*** marka <marka!~masselst@> has joined #yocto15:13
*** luq <luq!> has joined #yocto15:14
*** luq_ <luq_!> has joined #yocto15:14
*** learningc <learningc!~learningc@> has quit IRC15:15
yates_homesuccess building my first "hello world" LKM on target!15:17
*** kanavin <kanavin!~kanavin@> has quit IRC15:17
*** jobroe <jobroe!~manjaro-u@> has quit IRC15:23
*** kanavin <kanavin!~kanavin@> has joined #yocto15:23
*** hamis <hamis!~irfan@> has quit IRC15:23
*** didile <didile!b07ff51a@gateway/web/freenode/ip.> has joined #yocto15:25
didileI'm writing a recipe for the monocypher library:
didileHere it is:
didilebut I get an error at do_package_qa: QA Issue: -dev package contains non-symlink .so: monocypher-dev path '/work/cortexa9hf-neon-poky-linux-gnueabi/monocypher/2.0.5-r0/packages-split/monocypher-dev/usr/lib/' [dev-elf]15:27
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has joined #yocto15:27
didileI disabled the package split15:28
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has quit IRC15:28
RPkanavin: looks good :) I assume people can still select SDL?15:28
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has joined #yocto15:28
didileany idea how to solve this?15:28
kanavinRP: yes, of course!15:30
*** flying_sausages <flying_sausages!> has quit IRC15:32
*** interruptguy <interruptguy!> has quit IRC15:33
*** interruptguy <interruptguy!> has joined #yocto15:33
kanavinRP: also runqemu still defaults to non-gl variant with vmware vga driver15:34
*** interruptguy <interruptguy!> has quit IRC15:35
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC15:39
*** xperia64 <xperia64!> has quit IRC15:40
*** bernardoaraujo <bernardoaraujo!> has joined #yocto15:44
didileok I found that I need to add INSANE_SKIP_${PN}-dev = "dev-elf"15:44
*** jij <jij!jonashg@nat/axis/x-itgpjsfectcvugzn> has quit IRC15:44
RPkanavin: makes sense, thanks for confirming :)15:45
bernardoaraujosometimes I see BitBake processing more than one recipe in one thread, with a + sign between them... like recipe_1+recipe_2... where can I find some info about that kind of behavior?15:46
rburtondidile: don't disable package split, fix the packaging15:46
*** robbawebba <robbawebba!~rob@> has quit IRC15:46
didilerburton: how should I do that?15:46
rburtondidile: well why did you disable the package split?15:50
*** jij <jij!jonashg@nat/axis/x-ngovvzmlpdgutjfn> has joined #yocto15:51
didilerburton: I disable -dbg and -doc packages actually15:53
didilerburton: because I don't need them15:53
didilerbuton: it saves a lot of compilation time15:55
*** WillMiles <WillMiles!> has joined #yocto15:55
rburtonthat's not really anything to do with package splitting, that's just not building stuff15:56
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC15:57
didilethe variables are INHIBIT_PACKAGE_DEBUG_SPLIT = "1" and INHIBIT_PACKAGE_STRIP = "1"15:58
rburtonkanavin: boo to needing to build all of gtk+3-native :(15:58
rburtondidile: you do realise that just leave the debug symbols in the main package, so making them a lot larger15:58
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has quit IRC15:59
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has joined #yocto15:59
RPrburton: I'm dreading to think of the performance implications :/16:00
rburtonkanavin: dropping the gtk2 icon cache thing means that gtk2 and gtk3 can't coexist16:01
rburtonas they ship the same binary16:01
didilerburton: you mean INHIBIT_PACKAGE_DEBUG_SPLIT = "1" and INHIBIT_PACKAGE_STRIP = "1" make the packages a lot bigger?16:02
didileI see16:02
rburtonyou're not splitting out the debug symbols, so unless you've ensured they're not generated in the first place they'll be there still16:02
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto16:02
didilerburton: no I didn't know that16:02
tgoodwinIs there a way to bbappend a recipe that has its PV overridden by a different bbappend?  For example,, a_%.bbappend (sets PV to 1.1), a_1.1.bbappend (results in "no recipes available")16:03
*** malanecora <malanecora!b23cc82c@gateway/web/freenode/ip.> has quit IRC16:04
didilerburton: how could I remove the debug symbols instead?16:05
rburtondidile: don't pass -g to the compiler.  For a small library the difference will be <1s.16:06
rburtondidile: why don't you just use the makefile provided?16:07
didilerburton: because it installs manpages too16:07
rburtonall your package splitting problems are because you're building it yourself instead of using the makefile16:07
rburtonso? they'll be in monocypher-doc and not installed unless you want them16:08
*** xperia64 <xperia64!> has joined #yocto16:08
rburtona lot of upstream makefiles are pretty dumb, but don't reinvent the wheel unless you've verified this16:09
didileI should package man pages with FILES_${PN˘16:09
rburtonno need, default does the right thing.16:09
rburtonnote that your hand-coded CC is building a library with the wrong name16:09
*** saraf__ <saraf__!~a_saraf@> has quit IRC16:10
didilerburton: oe_runmake install DESTDIR=${D} gives me this error:
*** stephano <stephano!~stephano@> has joined #yocto16:10
*** zino_ <zino_!> has joined #yocto16:11
rburtondidile: look at the makefile to see what you need to set16:11
didilerburton: I only see DESTDIR to be empty16:12
rburtonmakefile correctly defaults to PREFIX=usr/local16:13
rburtonbut system packages install into $prefix, which is /usr16:13
rburtonso pass PREFIX=${prefix} in the recipe16:13
*** skynet <skynet!91fdde45@gateway/web/freenode/ip.> has quit IRC16:14
*** cvasilak <cvasilak!> has quit IRC16:16
didilerburton: I removed the PACKAGE_SPLIT var so it's compiling a few things...16:16
*** martinkelly <martinkelly!> has quit IRC16:17
*** martinkelly <martinkelly!> has joined #yocto16:17
*** ant_work <ant_work!> has quit IRC16:22
didilerburton: it works fine :)16:23
didilerburton: the new recipe:
*** TobSnyder <TobSnyder!> has quit IRC16:27
*** vmeson <vmeson!> has quit IRC16:27
*** vmeson <vmeson!> has joined #yocto16:28
*** amit_ <amit_!~amit@> has joined #yocto16:29
*** Amit_T <Amit_T!~amit@> has quit IRC16:30
*** flying_sausages <flying_sausages!> has joined #yocto16:31
*** xperia64 <xperia64!> has quit IRC16:33
*** Bunio_FH <Bunio_FH!> has quit IRC16:34
*** sgw <sgw!~sgw@> has quit IRC16:38
*** prabhakarlad <prabhakarlad!~prabhakar@> has joined #yocto16:39
*** frsc <frsc!~frsc@2003:a:e7a:6200:246c:2a8b:f45a:a33d> has quit IRC16:39
*** prabhakarlad <prabhakarlad!~prabhakar@> has left #yocto16:40
*** prabhakarlad <prabhakarlad!~prabhakar@> has joined #yocto16:40
*** rburton <rburton!> has quit IRC16:40
*** rburton <rburton!~rburton@> has joined #yocto16:41
*** gabrbedd <gabrbedd!> has quit IRC16:44
prabhakarladHi all, what is the good idea to apply a patch depending on the MACHINE type in a recipe ?16:44
rburtonprabhakarlad: use machine overrides to add to SRC_URI selectively16:44
*** gabrbedd <gabrbedd!> has joined #yocto16:46
*** lusus <lusus!~lusus@> has quit IRC16:47
*** vmeson <vmeson!> has joined #yocto16:48
rburtonkanavin: can you sling your qemu x11 patch to qemu-devel@nongnu.org16:48
rburtoniirc, you get moderated but not rejected16:48
rburton(as a non-member)16:48
*** robbawebba <robbawebba!~rob@> has joined #yocto16:50
prabhakarladrburton: thank you :)16:52
* RP wonders why shell code is being fed to the python parser16:54
*** gtristan <gtristan!~tristanva@> has quit IRC16:58
RPah, its not, its inline python in shell. gah16:59
*** xperia64 <xperia64!> has joined #yocto17:00
*** robbawebba <robbawebba!~rob@> has quit IRC17:06
*** fl0v0 <fl0v0!> has quit IRC17:08
*** didile <didile!b07ff51a@gateway/web/freenode/ip.> has quit IRC17:16
*** gtristan <gtristan!~tristanva@> has joined #yocto17:16
*** yann <yann!> has quit IRC17:16
*** gaulishcoin <gaulishcoin!> has joined #yocto17:22
*** cquast <cquast!~cquast@> has quit IRC17:23
*** [Sno] <[Sno]!> has joined #yocto17:33
*** sno <sno!> has quit IRC17:33
*** tprrt <tprrt!~tprrt@> has quit IRC17:35
*** xperia64 <xperia64!> has quit IRC17:40
*** bernardoaraujo <bernardoaraujo!> has quit IRC17:40
*** robbawebba <robbawebba!~rob@> has joined #yocto17:42
*** amit_ <amit_!~amit@> has quit IRC17:43
*** mckoan is now known as mckoan|away17:46
*** maudat <maudat!~moda@> has joined #yocto17:56
*** xperia64 <xperia64!> has joined #yocto18:07
kanavinrburton: all of gtk+3-native is actually not that much, as many of the bits were already needed for g-i and qemu18:08
kanavinrburton: I guess we'll have to sort the conflict between gtk 2 and 3, but I can't honestly see the benefit of choosing between the two implementations of icon cache binary at this point18:11
rburtonwell we need to rename one or both, but then themes need to call the binary, so surely alternatives is the way forwards (unless we universally drop gtk2 and then have the same problem with gtk4)18:18
*** [Sno] <[Sno]!> has quit IRC18:23
*** awe00 <awe00!~awe00@unaffiliated/awe00> has quit IRC18:27
kanavinrburton: yep, there theoretically could be a gtk2-only system I suppose18:31
*** dev1990 <dev1990!> has joined #yocto18:32
kanavinin all other cases (gtk2+gtk3, gtk3 only) shipping the 3.x version of the utility should simply work without doing the alternatives thing18:32
kanavinI'll drop the patch, there was some reason I had to make it though18:33
tgoodwinIf a layer is exposing a series of vendor-specific drivers for various hardware (and the vendor kernel), is that an appropriate use of adding MACHINE_FEATURES for each driver or is it more appropriate still to define specific machines?18:36
*** yann <yann!> has joined #yocto18:46
*** sno <sno!> has joined #yocto18:46
Croftontgoodwin, public layer?18:55
khemtgoodwin: maybe its ok to do so18:56
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:59
alimonRP: I looked at the result parser in runtime ptest and is very elaborate is supposed to do a simple thing, :/19:07
tgoodwinCrofton: might become one, yes19:16
tgoodwinWhere I'm tripping up is whether or not to set the default kernel parameters based a certain machine feature being set in a user's configuration, for example19:17
tgoodwinseems wrong19:17
*** gtristan <gtristan!~tristanva@> has quit IRC19:20
*** feddischson <feddischson!> has joined #yocto19:20
*** martinkelly <martinkelly!> has quit IRC19:33
*** martinkelly <martinkelly!> has joined #yocto19:33
aehs29alimon: so you better start working on it right away :)19:40
*** gtristan <gtristan!~tristanva@> has joined #yocto19:44
*** awe00 <awe00!~awe00@unaffiliated/awe00> has joined #yocto19:47
*** kroon <kroon!> has joined #yocto19:57
kroonIs there a point in using uninative+yocto sstate while keeping up with master ? I'm using "" but I never see any sstate reuse ..19:59
*** berton <berton!~berton@> has quit IRC20:17
khemwith master doesnt help much20:21
khemwith release branches it might make sense20:21
*** gtristan <gtristan!~tristanva@> has quit IRC20:29
RPalimon: I feel like that about a lot of oeqa :/20:32
RPalimon: if it can be simplified I'm all for it20:32
*** sgw <sgw!~sgw@> has joined #yocto20:34
yoctiNew news from stackoverflow: Generating callstack from inside system call <>20:34
*** hyde <hyde!uid25660@gateway/web/> has joined #yocto20:40
*** hyde <hyde!uid25660@gateway/web/> has left #yocto20:41
*** kaspter <kaspter!~Instantbi@> has quit IRC20:48
*** kaspter <kaspter!~Instantbi@> has joined #yocto20:49
Piratyw00t?? did you replace the opkg-0.4.0 tarball with a real release one ?? checksum changed again and not is missing. guys, this is really bad20:49
Piratyon top of that, it refuses to build20:53
RPadelcast: ^^^20:54
adelcasthey Piraty, you are talking about the binaries at
Piratyyeah. saturday (for whatever reason) the checksum changed (from it's friday state)20:58
adelcastAFAIK, those binaries were only posted once, was there a delta of time where 2 different versions were uploaded?20:59
Piratyand i would swear to you they had an and now they don't21:00
adelcastI usually create the releases, and as part of my release process I run, then remove it (as well as other stuff, like .git, etc)21:01
adelcastso I am completely certain there has never been an on those tarballs21:01
Piratyok lemme check, probably i screwed up and came yelling at you :-/21:02
*** robbawebba <robbawebba!~rob@> has quit IRC21:02
*** balister_ <balister_!~balister@2601:5c0:c100:b84:c22d:c40:ab44:9e37> has joined #yocto21:03
adelcastok, lemme know if you still think there was an issue, I can check with yocto's IT contact to see if something changed on the backend21:04
*** ernstp_ <ernstp_!sid168075@gateway/web/> has joined #yocto21:04
*** flynn378__ <flynn378__!sid63564@gateway/web/> has joined #yocto21:04
Piratyso because you run already, i should not have to use autoconf or the other tools, that correct?21:05
Piratylibtool wants me to run autoconf21:07
*** xperia64 <xperia64!> has quit IRC21:07
rburtonPiraty: 99% sure the tarball you originally had was actually a cgit generated archive21:07
rburtonyou said the checksums matched, which wouldn't be the case for a cgit link vs the tarball adelcast built21:08
*** balister_ is now known as Crofton|work21:08
rburtonalso, we'd have noticed if it changed, as the autobuilder would have warned21:08
Piratyi guess what happened, i changed the distfile string and it used the tarball from the cache, therefore there was present and when is switched machines, it had to download from the new mirror (which then was the real download.yocto...)21:08
Piratymy bad21:09
derRichardis it known that oe-init-build-env does not work with dash?21:10
Crofton|workI think so21:11
Piratythanks rburton adelcast , and sorry for confusion21:11
derRichard(the default /bin/sh on ubuntu)21:11
*** flynn378 <flynn378!sid63564@gateway/web/> has quit IRC21:11
*** ernstp <ernstp!sid168075@gateway/web/> has quit IRC21:11
*** armpit <armpit!~armpit@2601:202:4180:c33:bde0:cd61:908d:9500> has quit IRC21:11
*** Crofton <Crofton!~balister@2601:5c0:c100:b84:c22d:c40:ab44:9e37> has quit IRC21:11
derRichardjust tracked this down on a ubuntu docker :-\21:11
*** flynn378__ is now known as flynn37821:11
*** ernstp_ is now known as ernstp21:11
RPderRichard: it should, how was it failing? Or you mean the ability to specify the build directory?21:12
*** armpit <armpit!~armpit@2601:202:4180:c33:8d08:b580:d449:6594> has joined #yocto21:12
Piratyadelcast: what's this with your libtool version (see my attached faillog)21:14
Piraty2.4.6 is latest stable21:14
RPPiraty: libtool hasn't released in years which means people are using git snapshot versions21:16
derRichardRP: it fails to find the internal script: Can't open /scratch/rw/testing/new/scripts/oe-buildenv-internal21:17
derRichardbut i passed the builddir as parameter21:18
derRichardlet me try without21:18
derRichardnope, also wthout it fails21:18
RPderRichard: I thought it did work but dash is limited :/21:19
kroonit does on my setup21:19
*** maudat <maudat!~moda@> has quit IRC21:20
kroondebian 9 uses dash as well21:20
RPderRichard: does it help if you change to the directory first?21:20
RPkroon: but are you in a dash shell when starting the build?21:20
kroonRP, doh. no, sorry21:21
* kroon shuts up21:21
derRichardRP: where should it change to?21:21
RPderRichard: I mean instead of "source /foo/bar/oe-init-build-env", "cd /foo/bar; source oe-init-env"21:22
derRichardna, it fails differently21:22
RPderRichard: You may already be doing that in which case ignore me21:22
derRichardbtw. dash has no "source"21:23
derRichardjust "."21:23
RPtry ./oe-init-build-env21:23
RPderRichard: I knew it didn't have one or the other, guessed wrong :)21:23
derRichard./ also does not help, it cannot find oe-buildenv-internal21:23
derRichardno big deal here. i hate dash anyways with passion :)21:24
derRichardone of my docker scripts just used /bin/sh and ubuntu has brain dead defaults </rant>21:24
* RP isn't keen21:24
kroonderRichard, you're not setting OEROOT in the env ?21:24
derRichardnope. should i?21:25
derRichardi never set it21:25
kroonbut if I do, I get a similar error message21:25
derRichardjust checked, OEROOT is not set in my shell21:25
*** ant_home <ant_home!> has joined #yocto21:26
derRichardmaybe we should just note in the manual that bash should be used? :-D21:27
krooni get the same error as well when run from dash21:28
derRichardgood. at least it is not me :)21:28
kroonmaybe add sanity check in oe-init-build-env21:28
RPthat is surprisingly hard to do :/21:30
kroonor maybe oe-init-build-env is just has a bug that needs to be fixed..21:30
derRichardRP: just check whether $BASH_VERSION is something sane?21:31
RPderRichard: then the people who use csh complain (and so on)21:32
JPEWI though dash worked.... there was a bugzilla for it that was assigned to me, I tested it, and closed....21:32
derRichard*does* oe-init-build-env worth with csh?21:32
kroonderRichard, does it work if you run it from the same dir ?21:32
RPderRichard: I'm sure I remember patches but who knows21:32
kroonderRichard, cause it does here21:33
JPEWYOCTO #1177521:34
kroonIOW ". ./oe-init-build-env" does work on my debian 921:34
ant_homederRichard, we almost documented it years ago
kroon". openembedded-core/oe-init-build-env" does not, and I get a similar error message21:35
ant_homeI always do cd /oe/oe core; . ./oe/init-build-env21:36
*** xperia64 <xperia64!> has joined #yocto21:36
kroonderRichard, you forgot the "." in your pastebin21:36
krooni mean the "./" as in ". ./oe-init-build-env"21:37
* derRichard hates dash even more21:38
kroondont think you can blame dash for that though21:39
kroonthats because "." is not in your PATH21:39
derRichardi blame ubuntu for using not bash as /bin/sh21:40
ant_homederRichard, we try to avoid bashism in OE FWIW21:41
derRichardyocto runs on linux, nothing else21:41
ant_homeyes, nut different linus distro hav edifferent shells21:43
RPderRichard: we do support running with /bin/sh pointing at dash21:43
RPderRichard: that is tested21:43
derRichardant_home: which yocto supported distro does *not* ship bash?21:43
ant_homeas default?21:44
RPderRichard: ubuntu defaults to /bin/sh as dash21:44
RPderRichard: and bash as the login shell21:44
derRichardbut it has bash installed21:44
RP/bin/sh is still dash21:44
derRichardanyway, i don't care much. i have bash installed and all is good. just want to let you know :)21:45
*** ferlzc <ferlzc!> has joined #yocto21:45
ant_homeRP: ideally we aim to purity :) moving towards musl libc to have POSIX complaince as well21:45
RPand we run bitbake's scripts under /bin/sh21:45
kroonI added some comments to #1177521:45
RPderRichard: I wish I didn't have to care ;-)21:45
* ant_home confeeses his install of OpenBSD21:45
derRichardRP: yocto depends on so many stuff, IMHO depending on bash does not hurt21:48
kroonJPEW, ^^^21:49
JPEWkroon: Hmm, interesting. I wasn't aware that sourcing it outside the directory it lives in was supported. I wonder if that is why the original bug was logged21:51
*** kaspter <kaspter!~Instantbi@> has quit IRC21:54
*** kaspter <kaspter!~Instantbi@> has joined #yocto21:55
kroonJPEW, yeah, well at least thats how I always do it (in bash, . openembedded-core/oe-init-build-env)21:55
*** andrey_utkin <andrey_utkin!~andrey_ut@gentoo/developer/andrey-utkin> has quit IRC21:56
*** marka <marka!~masselst@> has quit IRC21:57
RPderRichard: its not that simple sadly22:03
derRichardwhy? you depend even on python22:06
RPderRichard: we don't control many of the scripts we run which can call "/bin/sh". So either we start editing them to point at bash or we force people to change /bin/sh to point at bash, or we accept it can point at dash22:08
*** xperia64 <xperia64!> has quit IRC22:08
kergothcommon source of confusion. folks often think the limitations are in bitbake/oe itself when it's really the underlying buildsystems we call into. much like the system default 'python' being 'python3' thing, until we addressed that in hosttools22:09
derRichardok, makes sense22:10
*** feddischson <feddischson!> has quit IRC22:10
derRichardis scons broken on sumo?22:14
derRichard    PREFIX = os.path.normpath(sys.prefix).replace( os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )22:14
derRichardTypeError: expected a string or other character buffer object22:14
derRichardit expects BUILD_SYS and HOST_SYS set22:14
derRichardif i add a "export BUILD_SYS", "export HOST_SYS" to the scons recipe, it builds fine22:14
RPthere should be something setting those22:15
*** robbawebba <robbawebba!~rob@> has joined #yocto22:19
derRichardbitbake.conf does22:24
derRichardbut in scons os.getenv("HOST_SYS") seems to return "None"22:25
RPderRichard: I think scons assumes you include one of the classes which exports then into the environment22:29
kergothiirc one of the python bbclasses exports those22:29
derRichardRP: well the scons-native recipe itself fails to build...22:30
derRichard./poky/meta/recipes-devtools/python/ to be correct22:30
*** flihp <flihp!~flihp@> has joined #yocto22:31
RPderRichard: it just built for me with master...22:31
derRichardas i said, i'm on sumo22:32
derRichardon thud it also seems to build22:32
derRichardi did such a build yesterday22:32
RPderRichard: it could be a bug...22:32
derRichardyeah :)22:33
*** xperia64 <xperia64!> has joined #yocto22:37
*** WillMiles <WillMiles!> has quit IRC22:38
kroonkergoth, in a .bb file, are all variable assignments parsed and overrides applied, before the "inherit" lines are acted upon ?22:42
kergothdepends on the version. recent versions apply overrides at expansion time rather than at the end of the parse when they used to be22:42
kergothso now a variabler eference in an include/require/inherit line will be applied, but only the ones that exist at that point, not those set after that line22:43
kroonkergoth, so include/require/inherit will "inline" the contents of the file, sort of like the C preprocessor and the "include" directive, and the argument to include/require/inherit will be expanded right there and then ? is that somewhat accurate ?22:48
kergothessentially yes22:48
kergothour lazy-ish variable expansion was inspired by gnu make, which is why they both have := to force immediate expansion22:50
kroonkergoth, ok, thanks for clarifying22:50
kroonwas "-include" too ugly ? :-)22:51
*** robbawebba <robbawebba!~rob@> has quit IRC22:56
*** bzb <bzb!> has joined #yocto23:01
*** gaulishcoin <gaulishcoin!> has quit IRC23:04
*** xperia64 <xperia64!> has quit IRC23:06
*** sgw <sgw!~sgw@> has quit IRC23:22
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto23:28
*** kroon <kroon!> has quit IRC23:32
*** xperia64 <xperia64!> has joined #yocto23:33
*** bzb_ <bzb_!> has joined #yocto23:35
*** bzb <bzb!> has quit IRC23:39
*** awe00 <awe00!~awe00@unaffiliated/awe00> has quit IRC23:45
*** sgw <sgw!~sgw@> has joined #yocto23:54
*** sgw <sgw!~sgw@> has quit IRC23:59

Generated by 2.11.0 by Marius Gedminas - find it at!