Thursday, 2020-04-30

*** robert_yang <robert_yang!~robert@> has quit IRC00:03
*** robert_yang <robert_yang!~robert@> has joined #yocto00:03
*** kpo <kpo!> has quit IRC00:04
*** robert_yang <robert_yang!~robert@> has quit IRC00:12
*** robert_yang <robert_yang!~robert@> has joined #yocto00:12
*** vineela <vineela!~vtummala@> has joined #yocto00:17
*** paulg <paulg!> has quit IRC00:19
*** vineela1 <vineela1!vtummala@nat/intel/x-yztujwyzybxuagoz> has quit IRC00:20
*** robert_yang <robert_yang!~robert@> has quit IRC00:22
*** robert_yang <robert_yang!~robert@> has joined #yocto00:22
*** paulg <paulg!> has joined #yocto00:33
*** Moh3N <Moh3N!057ee5da@> has joined #yocto00:53
Moh3Nhi , Im new in yocto , I have on question that maybe related to linux(not Only yocto). I build an Image and my board(PowerPC arch) boots up successfully , after booting I can see this output of "df -h" command :00:56
Moh3N"/dev/root"      45M      /00:58
Moh3Ndevtmpfs     169M      /dev00:58
Moh3Ntmpfs    208M     /var/volatile00:59
Moh3Ntmpfs      208M      /run00:59
Moh3NI have a code that when I run It it needs more than 45M storage because of its database and Log files, and root partition become full very soon01:01
*** stephano <stephano!> has quit IRC01:02
Moh3Nhow I can increase this partition??????  I can decrese tmpfs partitions in fstab file! but I want to have more space in root , because my code use /myDir for example01:02
Moh3Nis there any one who explain my mistake or misunderstanding ??01:03
*** attieg_ <attieg_!> has joined #yocto01:07
Moh3Nwhen I define size of /dev/root in  fstab, it doesnt any thing!!!!!01:08
*** attieg <attieg!> has quit IRC01:08
*** Sandrita <Sandrita!18ca2637@gateway/web/cgi-irc/> has quit IRC01:16
*** vineela <vineela!~vtummala@> has quit IRC01:25
*** Moh3N <Moh3N!057ee5da@> has quit IRC01:41
*** edgar444 <edgar444!uid214381@gateway/web/> has joined #yocto02:10
*** nameclash <nameclash!> has joined #yocto02:45
*** sakoman <sakoman!> has quit IRC02:59
*** invalidopcode_ <invalidopcode_!> has joined #yocto03:00
*** invalidopcode <invalidopcode!> has quit IRC03:03
*** gtristan <gtristan!~tristanva@> has quit IRC03:04
*** dqx <dqx!~dqx@unaffiliated/dqx> has quit IRC03:05
*** dqx <dqx!~dqx@unaffiliated/dqx> has joined #yocto03:06
*** meow` <meow`!~sbourdeli@> has quit IRC03:17
*** meow` <meow`!~sbourdeli@> has joined #yocto03:20
*** chandana731 <chandana731!~ckalluri@> has quit IRC04:05
*** chandana73 <chandana73!~ckalluri@> has joined #yocto04:09
*** marquiz <marquiz!~marquiz@> has joined #yocto04:15
*** marquiz_ <marquiz_!~marquiz@> has quit IRC04:16
*** RobertBerger <RobertBerger!> has quit IRC04:16
*** RobertBerger <RobertBerger!> has joined #yocto04:17
*** pacopedraza <pacopedraza!> has joined #yocto04:24
*** chandana73 <chandana73!~ckalluri@> has quit IRC04:28
*** chandana73 <chandana73!~ckalluri@> has joined #yocto04:29
*** pacopedraza <pacopedraza!> has quit IRC04:30
*** sgw <sgw!~sgw@> has quit IRC04:36
*** andycooper_home <andycooper_home!uid246432@gateway/web/> has quit IRC04:49
*** KindOne <KindOne!root@freenode/father-christmas/kindone> has quit IRC04:49
*** ssajal <ssajal!> has quit IRC04:55
*** KindOne <KindOne!shark@freenode/father-christmas/kindone> has joined #yocto04:57
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC05:09
*** ibinderwolf <ibinderwolf!> has joined #yocto05:10
*** feddischson <feddischson!> has joined #yocto05:15
*** agust <agust!> has joined #yocto05:17
*** jbeagle <jbeagle!~jkridner@pdpc/supporter/active/jkridner> has quit IRC05:23
*** invalidopcode <invalidopcode!> has joined #yocto05:24
*** AndersD <AndersD!> has joined #yocto05:26
*** invalidopcode_ <invalidopcode_!> has quit IRC05:27
*** jbeagle <jbeagle!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto05:29
*** pohly <pohly!> has joined #yocto05:44
*** smartin_ <smartin_!> has quit IRC05:52
*** gtristan <gtristan!~tristanva@> has joined #yocto05:53
*** vineela <vineela!~vtummala@> has joined #yocto06:12
*** vineela <vineela!~vtummala@> has quit IRC06:18
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto06:18
*** frsc <frsc!> has joined #yocto06:30
*** guerinoni <guerinoni!> has joined #yocto06:35
*** kroon <kroon!~kroon@> has joined #yocto06:38
*** dmoseley <dmoseley!~dmoseley@> has quit IRC06:44
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto06:45
*** pharaon2502 <pharaon2502!> has joined #yocto06:47
*** fl0v0 <fl0v0!~fvo@2a01:c23:601a:2f00:40b6:9542:8968:c5e0> has joined #yocto06:47
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@> has joined #yocto06:52
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto06:52
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto06:56
*** locutus_ <locutus_!~LocutusOf@> has joined #yocto06:57
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC06:59
*** hpsy <hpsy!~hpsy@> has joined #yocto07:04
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:5d17:dfd5:86c9:227> has joined #yocto07:11
yoctiNew news from stackoverflow: Yocto SDK with cmake toolchain file <>07:16
*** mckoan|away is now known as mckoan07:17
*** woutervh <woutervh!~woutervh@> has joined #yocto07:19
*** hpsy <hpsy!~hpsy@> has quit IRC07:20
*** hpsy <hpsy!~hpsy@> has joined #yocto07:20
*** kroon <kroon!~kroon@> has quit IRC07:24
*** kroon <kroon!~kroon@> has joined #yocto07:29
*** invalidopcode <invalidopcode!> has quit IRC07:33
*** jbeagle <jbeagle!~jkridner@pdpc/supporter/active/jkridner> has quit IRC07:36
*** jbeagle <jbeagle!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto07:39
*** lucaceresoli <lucaceresoli!~lucaceres@> has joined #yocto07:51
*** yann|work <yann|work!> has joined #yocto07:52
*** kroon <kroon!~kroon@> has quit IRC08:28
*** kroon <kroon!~kroon@> has joined #yocto08:31
*** jbeagle <jbeagle!~jkridner@pdpc/supporter/active/jkridner> has quit IRC08:38
*** dev1990 <dev1990!> has joined #yocto08:48
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:116a:e4c5:723c:5ca8> has quit IRC08:50
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto08:51
*** Bunio_FH <Bunio_FH!> has quit IRC08:54
*** bfederau[m] <bfederau[m]!bfederauma@gateway/shell/> has quit IRC08:56
*** hmw1 <hmw1!hmwmatrixo@gateway/shell/> has quit IRC08:56
*** guillaume <guillaume!gscigalama@gateway/shell/> has quit IRC08:56
*** bachp <bachp!bachpmatri@gateway/shell/> has quit IRC08:56
*** silviof <silviof!silv-iomat@gateway/shell/> has quit IRC08:56
*** wak-work <wak-work!wak-workma@gateway/shell/> has quit IRC08:56
*** yangm <yangm!yanyetanot@gateway/shell/> has quit IRC08:56
*** edrex <edrex!edrexmatri@gateway/shell/> has quit IRC08:56
*** henriknj <henriknj!hnjematrix@gateway/shell/> has quit IRC08:56
*** clementp[m] <clementp[m]!cperonmatr@gateway/shell/> has quit IRC08:56
*** sstiller <sstiller!> has joined #yocto08:58
*** locutus__ <locutus__!~LocutusOf@> has joined #yocto08:58
*** locutus_ <locutus_!~LocutusOf@> has quit IRC09:00
*** Bunio_FH <Bunio_FH!> has joined #yocto09:01
*** kpo <kpo!> has joined #yocto09:05
*** guillaume <guillaume!gscigalama@gateway/shell/> has joined #yocto09:09
*** hpsy <hpsy!~hpsy@> has quit IRC09:21
*** hpsy <hpsy!~hpsy@> has joined #yocto09:21
*** yann|work is now known as yann09:22
*** silviof <silviof!silv-iomat@gateway/shell/> has joined #yocto09:30
*** yangm <yangm!yanyetanot@gateway/shell/> has joined #yocto09:30
*** bachp <bachp!bachpmatri@gateway/shell/> has joined #yocto09:30
*** edrex <edrex!edrexmatri@gateway/shell/> has joined #yocto09:30
*** bfederau[m] <bfederau[m]!bfederauma@gateway/shell/> has joined #yocto09:30
*** hmw1 <hmw1!hmwmatrixo@gateway/shell/> has joined #yocto09:30
*** wak-work <wak-work!wak-workma@gateway/shell/> has joined #yocto09:30
*** henriknj <henriknj!hnjematrix@gateway/shell/> has joined #yocto09:30
*** berton[m] <berton[m]!fabioberto@gateway/shell/> has joined #yocto09:30
*** clementp[m] <clementp[m]!cperonmatr@gateway/shell/> has joined #yocto09:30
*** vdehors_ <vdehors_!> has joined #yocto09:35
*** vdehors <vdehors!> has quit IRC09:35
*** gtristan <gtristan!~tristanva@> has quit IRC09:42
*** goliath <goliath!> has joined #yocto09:42
*** rburton <rburton!~rburton@> has joined #yocto09:54
*** JaMa <JaMa!~martin@> has joined #yocto10:10
RPrburton, kanavin_home: Any ideas why master-next would be triggering SIGILL in various places? :/10:12
RP(trying to run native binaries)10:13
*** nameclash <nameclash!> has quit IRC10:13
* RP can't spot the pattern10:14
kanavin_homeRP: no :(10:16
RPlast two master-next builds have issues and I don't know what happened :(10:19
*** lucaceresoli <lucaceresoli!~lucaceres@> has quit IRC10:21
kroonI like the top answer10:26
*** hpsy <hpsy!~hpsy@> has quit IRC10:30
*** hpsy <hpsy!~hpsy@> has joined #yocto10:30
*** nacknick <nacknick!8de24efa@> has joined #yocto10:33
nacknickHey. Anyway to disable OSTree in Yocto?10:33
RPnacknick: its not used by default? :)10:34
nacknickFor some reason it's not RP10:34
RPnacknick: I'm pretty sure (as the maintainer) that it isn't in OE-Core or the default Yocto layers. That means its being brought in by something you're adding/enabling on top of the base system10:36
nacknickRP And there is a way to disable it?10:41
RPnacknick: I have no idea how you've added it. Find how it was added and don't do that? Maybe remove the layer for example?10:42
nacknickAnother question please: I know that `INHIBIT_PACKAGE_STRIP_pn-<PN>` makes a *package*, Is there a way to make a *single* executable file inside the package to not-stripped? And not all its binaries??10:44
nacknickmakes a package not strip their binaries**10:45
*** sstiller <sstiller!> has quit IRC10:53
qschulznacknick: wild guess: what about INHIBIT_PACKAGE_STRIP = "1" in the recipe?10:53
RPkanavin_home: - can you have a look at the step2d, error: /etc/rpm/macros.perl: line 34: Macro %global is a built-in (%define)10:59
*** kaspter <kaspter!~Instantbi@> has quit IRC10:59
*** ibinderwolf <ibinderwolf!> has quit IRC11:00
RPkanavin_home: doesn't appears to break anything but is new I think11:01
*** guerinoni <guerinoni!> has quit IRC11:11
kanavin_homeRP: I think it should be largely harmless - the test doesn't do enough to avoid rpm reading /etc/rpm/ from the host, but it shouldn't affect the outcome (which about how rpm compares versions)11:14
kanavin_homeRP: the places where native rpm is used to package or create rootfs are much more careful about that I think11:15
RPkanavin_home: log files with lines starting "error" just never look very good ;-)11:16
RPit also means those tests aren't deterministic :(11:16
RPkanavin_home: I guess we open a bug just to track it11:16
kanavin_homeRP: sure11:16
kanavin_homeRP: it's probably a matter of checking to see how rpm is instructed to look in build/.../etc/rpm that we create, and copy that bit into the test11:18
RPkanavin_home: right, makes sense11:20
RPkanavin_home: I'm going to struggle to get to your next patchset until i figure out this sigill issue :/11:21
*** ibinderwolf <ibinderwolf!> has joined #yocto11:21
*** FrazerClews <FrazerClews!> has quit IRC11:21
kanavin_homeRP: yeah, unfortunate timing :(11:23
kanavin_homelet me know if I can do anything11:23
RPkanavin_home: I just don't know how I'm going to find this, the pattern is too weird to pin down easily :(11:24
kanavin_homeRP: does master build cleanly?11:25
RPkanavin_home: seemingly11:26
RPkanavin_home: actually, no11:29
RPkanavin_home: dnf returning -4 on master11:29
*** berton <berton!~berton@> has joined #yocto11:34
rburtonRP: sigill? something native being built using -march=native on a newer machine and then same binaries being reused on a machine without those instructions?11:35
RPboth master failures on centos7-ty-211:35
RPrburton: possible if something is patching that in somewhere11:36
kanavin_homeRP: but what is receiving sigill specifically?11:38
*** FrazerClews <FrazerClews!> has joined #yocto11:38
*** guerinoni <guerinoni!> has joined #yocto11:41
rburtoni'd compare cpu generation of those workers to a rebuild of the same revision on another worker that presumably works11:42
RPkanavin_home: dnf, update-mime-db, xsltproc, wayland-scanner, swig11:43
RPrburton: the cpu flags are quite different on the various workers11:43
rburtonnew in master?11:44
RPrburton: I think this is something in recent master, yes11:44
RPrburton: cpu flag differences, abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti tsc_adjust bmi1 hle avx2 smep bmi2 invpcid rtm cqm rdt_a rdseed adx intel_pt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local cpuid sdbg fma movbe11:54
RPavx2 and movbe :/11:54
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto11:56
rburtoncan you replicate on demand? and get the error logs from dmesg?11:58
RPrburton: it probably can be replicated. I do have dmesg11:59
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto12:04
*** locutus__ <locutus__!~LocutusOf@> has quit IRC12:07
*** ebail <ebail!> has joined #yocto12:11
ebailHi guys. I just sent a patch on meta-dpdk and use as mentionned in README12:12
ebailit looks like you moved to meta-intel@lists.yoctoproject.org12:12
RPrburton: shrx instruction12:13
ebailis redirected ? On I don't see my patch so far.12:13
RPebail: you should use meta-intel@lists.yoctoproject.org12:14
ebailit looks like I finally see my message. I will add an other patch to modify the README then :). Thanks RP12:15
RPebail: sounds good, thanks. I guess the redirected mail is just slow12:17
nacknickqschulz: I just missed what you wrote. Anyway, it has the same affect12:19
nacknickI still want to not strip a specific binary file inside the package and not all the binaries12:19
RPrburton: and its in update-mine-info itself, not any library12:21
*** NiksDev <NiksDev!~NiksDev@> has quit IRC12:25
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto12:25
*** kroon <kroon!~kroon@> has quit IRC12:26
ebailRP: patch on README sent. Thanks12:27
rburtonRP: haswell+ then12:28
rburtonRP: i'd look at the compile log for the native recipe, see if its doing anything weird.12:33
rburtonalternatively did we add any new builders? or maybe a new rolling distro has decided to pass march=native implicityl?12:33
JaMaI have question about uninative, we have some kernel recipe which deploys native tool to DEPLOY_DIR_IMAGE, looking at uninative.bbclass in thud I see that uninative_changeinterp is applied only for native/cross/crosssdk recipes, does anyone have cases like this where uninative_changeinterp needs to be forced for some files from target recipe as well?12:34
JaMaor maybe I'm missing some part of this puzzle, because the binary shows uninative loader path, but pointing to directory as it was on the builder which created the binary, but the loader doesn't exist in that path on builder where sstate do_deploy is being reused12:36
JaMaah it's BUILD_LDFLAGS which set the uninative loader even when the recipe isn't native12:38
qschulznacknick: misunderstood sorry, INHIBIT_PACKAGE_STRIP_FILES maybe?12:41
rburtonnacknick: why do you not want to strip one specific binary? what does that achieve?12:48
RPrburton: over lunch I was also thinking about rolling builders doing something different12:49
*** lucaceresoli <lucaceresoli!~lucaceres@> has joined #yocto12:51
JaMaas temporary work around I'll explicitly use host's loader again13:02
nacknickqschulz: thanks I will check that13:02
*** Sandrita <Sandrita!18ca2637@gateway/web/cgi-irc/> has joined #yocto13:02
RPJaMa: the assumption is that target recipes don't generate native binaries13:03
nacknickrburton: I said *I want* to not-strip one file inside a package, and not to do so for all binaries of the same package13:03
JaMaRP: yes, in ideal world they shouldn't :)13:04
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:238d:84be:b349:9184> has quit IRC13:04
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:238d:84be:b349:9184> has joined #yocto13:05
*** lfa_ <lfa_!> has quit IRC13:05
*** andycooper_home <andycooper_home!uid246432@gateway/web/> has joined #yocto13:07
RPrburton: I've put a sentinel into master-next to try and find where this is coming from. My guess of opensuse doesn't appear right13:10
*** Sandrita43 <Sandrita43!18ca2637@gateway/web/cgi-irc/> has joined #yocto13:12
*** Sandrita <Sandrita!18ca2637@gateway/web/cgi-irc/> has quit IRC13:12
*** kergoth <kergoth!~kergoth@> has joined #yocto13:17
*** jbeagle <jbeagle!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto13:19
RPI think we need markers in sstate objects so we can know the origin13:21
*** ericch <ericch!> has joined #yocto13:21
*** maudat <maudat!> has joined #yocto13:22
*** stephano <stephano!> has joined #yocto13:31
*** pharaon2502 <pharaon2502!> has quit IRC13:32
*** ssajal <ssajal!> has joined #yocto13:38
*** UVV <UVV!2578cdb4@> has joined #yocto13:46
UVVHi everyone. I have a patch for meta layer, which I've sent to . I'm wondering now if it was a correct mailing list for this...13:48
*** BoJonas <BoJonas!> has joined #yocto13:52
qschulzUVV: meta in poky is openembedded-core if I'm not mistaken13:53
UVVAlright, thank, I'll resend it there13:56
UVVAlright, thanks, I'll resend it there13:56
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC13:57
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has joined #yocto13:57
*** caiortp <caiortp!d57f6fca@gateway/web/cgi-irc/> has joined #yocto13:58
*** UVV <UVV!2578cdb4@> has quit IRC13:59
BoJonasHi all, what is the "best way (TM)" to handle a yocto project for different architectures?14:00
BoJonasOur project is, in it's simplst form, a common layer (let's call it meta-commen) and two architecture/device specific layers (let's call them meta-x86 and meta-arm64).14:00
BoJonasWhat I'm doing right now, is having two different build directories, one for each machine, with separate bblayers.conf files, including the common layer and the device specific layer.14:00
qschulzBoJonas: layers shouldn't be destructive. they should be able to live together just well14:01
qschulzif not, you need to fix the layers14:01
*** sgw <sgw!~sgw@> has joined #yocto14:02
BoJonasBut if I have the same recipe in meta-x86 and in meta-arm64, how can bitbake tell which one to use?14:03
qschulzBoJonas: what is the recipe you're talking about?14:03
BoJonasIt could be any recipe. A recipe for setting the hostname for instance14:03
qschulzBoJonas: FYI, you can use VAR_<machine> or VAR_<architecture> or do_<task>_<machine/arch>14:04
qschulzBoJonas: in some cases, you can merge both recipes and have only a few variables or tasks machine/arch specific (don't forget to set PACKAGE_ARCH to MACHINE_ARCH in that case)14:04
BoJonasOk.. But then I need to make all variables in the recipes "machine specific" right?14:04
*** sakoman <sakoman!> has joined #yocto14:05
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC14:05
RobertBerger@BoJonas: What is done differently to read the hostname for x86 and arm?14:05
qschulzBoJonas: in some others, if the recipes are completely different but have the same "meaning", then virtual recipes/packages are what you're looking for. You can use COMPATIBLE_MACHINE to be sure to never pick the wrong one, and you can pick the provider with PREFERRED_PROVIDER and/or PREFERRED_VERSION14:06
BoJonasOne target is named "my-cool-arm-host" and the other is named "this-is-a-x86-host" for instance14:06
RobertBerger@BoJonas: OK I see you want to give it different host names depending on what they are build for.14:07
qschulzBoJonas: you could use a variable available from Yocto and put it in the hostname, or use a variable you would set in your machine.conf file14:07
*** locutus_ <locutus_!~LocutusOf@> has joined #yocto14:08
RobertBerger@BoJonas: as qschulz points out I would look at machine.conf. Certainly you will need 2 different BSP layers and 2 different machines to build for. By default the "BSP" name ends up being the hard coded hostname.14:08
BoJonas@RobertBerger yes, the two different targets are two completely different products, but are "kind-of" running the same application (with very different configs). Thats why we currently have these machine specific layers, and only include the one we need14:09
qschulzbut you should be able to build with both layers in bblayers.conf14:09
BoJonasOk, I'll have a look at machine.conf14:10
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC14:10
BoJonasCan I make a layer machine-specific?14:10
RobertBerger@BoJonas: That's what is called BSP layer14:10
BoJonasDoh!! Now I understand! Of course14:11
qschulzBoJonas: a BSP layer is a layer for all recipes required to boot the device. kernel, u-boot, machine configuration file. Maybe a few **very** specific recipes but it should be very small IMO14:11
*** locutus_ <locutus_!~LocutusOf@> has quit IRC14:12
qschulzthen, if your recipe has a different configuration depending on the machine, that is something you could set directly from within the recipe by using <machine> overrides14:13
BoJonasOk, i see14:13
RobertBerger@BoJonas: here is a machine.conf file
*** pharaon2502 <pharaon2502!> has joined #yocto14:14
RobertBergerthis is one for various boards ;)14:14
RobertBergerarmv7 based boards14:14
BoJonasYes ok, I see that I need to move more of my configuration out of the recipes and into machine.conf instead14:14
RobertBergeryou need to understand the concepts of distro, machine and image14:16
qschulzBoJonas: indeed and make use of machine/architecture overrides in some cases where it's not possible to put it into the machine.conf14:16
RobertBergerThe same image can be built for different machines. e.g. core-image-minimal for your arm and x86 boards14:17
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has joined #yocto14:17
BoJonas@RobertBerger, I think you are right.. What we do now is that we have our "" in the meta-common layer and then have "main-image.bbappend" in the device-specific layers14:17
qschulzBoJonas: as suggested by RobertBerger.. you can have a look at
qschulzBoJonas: yup, that seems wrong :)14:17
BoJonas@qschulz thanks i'll give it a look14:17
RobertBerger@BoJonas: But don't you fear: You would not be the first one who made such mistakes :) I saw this many times.14:19
qschulzEveryone makes mistake, everyone learns... for ever and ever :)14:20
BoJonasI have been using Yocto in different companies since beginning of 2015, and everyone seems to have misunderstood the basic concepts, and try to "invent" their own way of doing things like this.14:20
BoJonasThat's why I want to try to do it the right way this time14:21
RobertBerger@BoJonas:  Well unfortunately there are many degrees of freedom with OE/YP.14:23
*** fray <fray!> has joined #yocto14:23
*** nucatus <nucatus!> has joined #yocto14:23
*** AndersD <AndersD!> has quit IRC14:23
BoJonas@RobertBerger, yes i agree .. it's both good and bad14:24
BoJonasBut I still think that Yocto is fantastic14:24
BoJonasAnother thing .. can I build for multiple targets in a single bitbake command?14:27
BoJonasSorry, not targets, machines14:27
BoJonasI mainly need this for fetching all the sources for our different devices. Right now, we run a bitbake --runall=fetch for every target, but if I have all my layers included in my bblayers.conf, i guess that it will fetch for all machines, right?14:29
BoJonas... Hmm, thinking about it, no I guess it would only fetch for the machine specified14:30
*** ibinderwolf <ibinderwolf!> has quit IRC14:36
*** hpsy <hpsy!~hpsy@> has quit IRC14:36
*** hpsy <hpsy!~hpsy@> has joined #yocto14:37
smurrayBoJonas: the multiconfig feature is the only way to do that14:45
*** jbeagle <jbeagle!~jkridner@pdpc/supporter/active/jkridner> has quit IRC14:45
khemRP: I am seeing error: 'FALSE' undeclared in following two recipes before I delve into them has something change in oe-core/master-next14:46
*** jbeagle <jbeagle!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto14:46
*** lucaceresoli <lucaceresoli!~lucaceres@> has quit IRC15:00
*** pharaon2502 <pharaon2502!> has quit IRC15:01
*** nameclash <nameclash!> has joined #yocto15:02
RobertBerger@BoJonas: Look at multiconfig15:02
*** pharaon2502 <pharaon2502!> has joined #yocto15:03
qschulzRobertBerger: that's a bit overkill for only fetching packages :D15:03
RobertBerger@qschulz - yes of course just for fetching it's overkill15:04
RobertBerger@BoJonas I would unify as much as possible and, as you said, it's just different configurations with the same app design it like this.15:05
RobertBerger@BoJonas: like this you have the same sources and you could use a download cache for all of them15:05
*** lucaceresoli <lucaceresoli!~lucaceres@> has joined #yocto15:06
*** nucatus <nucatus!> has quit IRC15:07
*** nameclash <nameclash!> has quit IRC15:18
*** goliath <goliath!> has quit IRC15:24
*** gtristan <gtristan!~tristanva@> has joined #yocto15:24
*** goliath <goliath!> has joined #yocto15:29
RPkhem: not that I know of. We are seeing corrupt sstate with SIGILL being triggered from native binaries all over though15:33
*** goliath <goliath!> has quit IRC15:34
JaMaany meta-rust users/devs here? Have anyone tried to pass something like ${@oe.utils.parallel_make_argument(d, '-Ccodegen-units=%d', limit=64)} to rust-native bootstrap? It takes really long as shown by so I'm trying to make it more parallel15:36
*** frsc <frsc!> has quit IRC15:37
RPJPEW: hashequiv is totally undermining my attempts to debug this SIGILL issue :)15:40
*** dreyna <dreyna!> has joined #yocto15:43
yoctiNew news from stackoverflow: why does autostart with systemd doesn't work <>15:48
*** stacktrust <stacktrust!> has quit IRC15:52
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has quit IRC15:56
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has joined #yocto16:00
JPEWRP: Ya, I would expect it would16:01
khemJaMa: its building full llvm underneath so long times are expectd16:06
JaMakhem: isn't that in rust-llvm-native? I see most time spent in single threadded "rustc-1.37.0-src/build/x86_64-unknown-linux-gnu/stage0-tools-bin/fabricate generate"16:07
*** jae1 <jae1!> has joined #yocto16:11
JaMait's rust-native.do_compile which takes 20 minutes, even more than chromium-x11.do_compile in some cases16:11
*** nacknick <nacknick!8de24efa@> has quit IRC16:12
khemyeah fabricate it trouble to run in parallel16:15
yoctiNew news from stackoverflow: Why does autostart with systemd not work? <>16:18
*** goliath <goliath!> has joined #yocto16:22
*** jae1 <jae1!> has quit IRC16:30
*** caiortp <caiortp!d57f6fca@gateway/web/cgi-irc/> has quit IRC16:34
RobertBergerAm I the only one who sees NOTE: Retrying server connection (#8)...16:40
RobertBergerERROR: Unable to connect to bitbake server, or start one (server startup failures would be in bitbake-cookerdaemon.log) caused by "OSError: [Errno 98] Address 'hashserve.sock' is already in use" with dufell?16:40
kergother I'm seeing the retrying connection thing all the time now16:45
kergothhaven't seen the hashserve message though16:46
kergothneed to try to bisect16:46
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:48
RobertBerger@kergoth - not good ;)16:48
RobertBerger@kergoth: I CTRL+C, bitbakes are not killed, I kill them manually and I get this problem - need to manually remove hashserve.sock to bitbake again16:50
*** pacopedraza <pacopedraza!> has joined #yocto16:50
RobertBerger@kergoth: currently running a test where I did CTRL+C and no kill to see if a new bitbake run will fix it16:51
RobertBerger@kergoth: the hashserve message is in a log file: bitbake-cookerdaemon.log16:52
RobertBerger@kergoth: bitbake does not fix it if I don't kill them either16:53
*** stephano <stephano!> has quit IRC16:53
RobertBerger@kergoth: I guess someone should clean up hashsrv.sock by default?16:54
dl9pfIirc it happens with bitbake in memres  mode16:57
*** stephano <stephano!> has joined #yocto16:57
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC17:01
RobertBerger@dl9pf not only. I don't use memres mode, at least I don't intend to ;)17:01
RobertBerger@dl9pf  is it on by default now?17:02
*** vineela <vineela!~vtummala@> has joined #yocto17:02
*** mckoan is now known as mckoan|away17:03
RPkanavin_home: tracked this down and it is buildtools-tarball that is breaking things17:04
*** guerinoni <guerinoni!> has quit IRC17:04
kanavin_homeRP: :( how come?17:07
RPkanavin_home: I think the gcc in buildtools-tarball-extended has some kind of --with-arch=native default17:08
kanavin_homeRP: oh, so it's not about gomp? phew :)17:08
RPkanavin_home: I just know if I have a clean setup and force a build of shared-mime-info-native, it only breaks when buildtools-tarball-extended is in play17:09
*** woutervh <woutervh!~woutervh@> has quit IRC17:09
RPkanavin_home: I'm not blaming gomp, this new toolchain does seem to have issues though17:09
RPwhether host cpu flags leaked into the buildtools, I don't know17:09
RPsome handle on where to look is progress I guess17:10
*** stephano <stephano!> has quit IRC17:11
yoctiNew news from stackoverflow: Remove ROS from Yocto Bitbake to Reduce Image Size <>17:18
*** alejandrohs <alejandrohs!~alejandro@> has joined #yocto17:28
*** feddischson <feddischson!> has quit IRC17:30
*** vmeson <vmeson!> has joined #yocto17:32
*** stephano <stephano!> has joined #yocto17:34
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC17:42
*** pharaon2502 <pharaon2502!> has quit IRC17:49
*** pharaon2502 <pharaon2502!> has joined #yocto17:51
*** lucaceresoli <lucaceresoli!~lucaceres@> has quit IRC17:59
RPsakoman: I'd hold off builds for now. I know what the issue is, just need time to fix it and upgrade buildtools on the AB18:03
*** guerinoni <guerinoni!> has joined #yocto18:12
*** guerinoni <guerinoni!> has quit IRC18:13
*** radsquirrel <radsquirrel!> has quit IRC18:17
*** radsquirrel <radsquirrel!> has joined #yocto18:18
*** ebail <ebail!> has quit IRC18:23
*** dreyna_ <dreyna_!~dreyna@2601:646:4201:b1a0:11a3:b093:3ebb:3130> has joined #yocto18:28
*** meow` <meow`!~sbourdeli@> has quit IRC18:29
denixhalstead: ping18:29
*** meow` <meow`!~sbourdeli@> has joined #yocto18:30
*** Sandrita43 <Sandrita43!18ca2637@gateway/web/cgi-irc/> has quit IRC18:30
*** dreyna <dreyna!> has quit IRC18:31
*** Sandrita <Sandrita!18ca2637@gateway/web/cgi-irc/> has joined #yocto18:31
denixhalstead: why did List-Id: change on on/around Apr 25?18:31
kergothgood question, it broke half my filters :)18:33
kergothguessing the conversion?18:33
halsteaddenix, kergoth April 25th is after migration. I'll check the product update history and see if I can find a reason.18:41
denixkergoth: yeah, same here, notably patchwork18:42
*** smartin <smartin!> has quit IRC18:55
*** jd89 <jd89!> has joined #yocto18:56
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto19:01
khemRP: I figured, its the json-c upgrade patch in oe-core which is causing this issue, please hold it off19:08
*** invalidopcode <invalidopcode!> has joined #yocto19:10
smurrayhalstead: my guess is the change correlates with ndec changing the reply behavior of the lists19:13
*** rburton <rburton!~rburton@> has quit IRC19:14
halsteadsmurray, I'll check if that is it. Lots of product changes went in on the 24th but none called out a list-id change.19:14
*** smartin <smartin!> has joined #yocto19:14
RPkhem: actually its a patch from this khem guy ;-)19:18
halsteadsmurray, It appears the change was global to the platform not a setting we altered.19:20
smurrayhalstead: ouch, that seems like a misfeature on the part of groups.io19:20
ndecAt least it wasn’t me ;)19:20
*** lucaceresoli <lucaceresoli!~lucaceres@> has joined #yocto19:21
denixndec: you are off the hook for now... :)19:21
RPkhem: we didn't realise gcc-target has implications for nativesdk-gcc19:21
* smurray hopes filtering on ^Mailing-List is going to prove stable19:21
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto19:22
denixsmurray: how standard that field is?19:22
smurraydenix: I'm unsure, tbh.  I went back and checked and it's not present in older messages, so it might not be19:24
*** goliath <goliath!> has quit IRC19:37
*** lucaceresoli <lucaceresoli!~lucaceres@> has quit IRC19:38
RPI thought List-ID was the stable one?20:03
RPkhem: I understand your comment btw and will hold off the json-c patch for now20:06
RPkhem: we were cross talking issues :)20:07
denixRP: it is, but our List-Ids got changed/renamed last weekend on (see above) :( many filters got broken. our internal patchworks now misses patches20:08
denixsmurray: maybe you can use ^Mailing-List for procmail or other filters, but our ancient Patchwork seems to rely solely on List-Id :(20:11
RPdenix: hmm, I wonder why mine still work20:11
denixRP: it is now like this - List-Id: <>20:11
denixRP: used to be List-Id: <>20:12
kergothi'm guessing exact match vs search, gmail's filters are often the latter, so it doesn't have to be exact20:12
RPdenix: I got lucky with where I put wildcards in my procmail files!20:13
smurrayRP: yeah, I toyed with adding some wildcards, if Mailing-List proves problematic, I'll switch to doing that20:13
khemRP: what issue did you run into with nativesdk ?20:15
RPI've pushed ABI bumps into master-next so its rebuilding everything with the new buildtools on the appropriate workers20:15
RPkhem: if you use buildtools-tarball-extended and build with arch=native, it means the binaries won't run on other workers using uninative but hit SIGILL20:16
*** goliath <goliath!> has joined #yocto20:16
RPkhem: I was busy trying to find which crazy distro had enabled arch=native then found it was our buildtools :)20:17
*** alejandr1 <alejandr1!~alejandro@> has joined #yocto20:18
*** KindOne <KindOne!shark@freenode/father-christmas/kindone> has quit IRC20:18
*** alejandr1 <alejandr1!~alejandro@> has quit IRC20:18
*** alejandrohs <alejandrohs!~alejandro@> has quit IRC20:19
*** KindOne <KindOne!kindone@freenode/father-christmas/kindone> has joined #yocto20:21
*** alejandrohs <alejandrohs!~alejandro@> has joined #yocto20:22
*** woutervh <woutervh!~woutervh@> has joined #yocto20:26
*** smrbz <smrbz!> has joined #yocto20:28
*** pacopedraza <pacopedraza!> has quit IRC20:30
smrbzHey guys, I've been working with yocto for a bit now and was wondering something. My goal is to use yocto to build images for product with a web server interface (node/react). What would be the recommended procedure getting that project code on the system and up and running?20:31
smrbzperhaps just a recipe with an empty do_compile() stage?20:33
RPsmrbz: that would work, there are other recipes which do this for config files and similar20:34
halsteaddenix, smurray, The list-id change has been rolled back. It was added in attempt to assist with several e-mail providers spam policies. After testing the change wasn't needed.20:36
smrbz@RP great, that was my thinking given that there's nothing really to compile and the software recipe would give me a more formal means of putting code in the right location20:37
*** smrbz <smrbz!> has quit IRC20:37
smurrayhalstead: thanks for the heads up!20:37
halsteaddenix, If you changed your filters you will need to adjust back.20:37
denixhalstead: great, thanks!20:38
khemRP: extended tools tarball will use gcc target runtime  right I guess this change was prior to extended tools tarball was a reality20:50
*** khem <khem!~khem@unaffiliated/khem> has quit IRC20:52
*** rperier <rperier!~quassel@unaffiliated/bambee> has quit IRC20:53
*** iokill <iokill!> has quit IRC20:53
*** Lihis <Lihis!> has quit IRC20:53
*** Chaser <Chaser!> has quit IRC20:53
*** erbo <erbo!> has quit IRC20:53
*** icee <icee!mlyle@dRonin/dev/icee> has quit IRC20:53
*** Marex <Marex!~Marex@> has quit IRC20:53
*** gourve_l <gourve_l!> has quit IRC20:53
*** rperier_ <rperier_!> has joined #yocto20:53
*** erbo <erbo!> has joined #yocto20:53
*** icee <icee!> has joined #yocto20:53
*** iokill <iokill!> has joined #yocto20:53
*** Marex <Marex!~Marex@> has joined #yocto20:53
*** gourve_l <gourve_l!> has joined #yocto20:53
*** khem <khem!~khem@2601:646:9200:4e0::e11c> has joined #yocto20:54
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto20:54
*** g0hl1n <g0hl1n!> has quit IRC20:55
*** Chaser <Chaser!> has joined #yocto20:56
*** Lihis <Lihis!> has joined #yocto20:57
*** juvenal <juvenal!> has quit IRC20:59
khemRP: do we have a writeup on extended toolchain tarball generation ? I am interested in creating one to build morty20:59
khemlooking for building morty on ubuntu 18.0420:59
*** hpsy <hpsy!~hpsy@> has quit IRC21:00
*** hpsy <hpsy!~hpsy@> has joined #yocto21:00
*** g0hl1n <g0hl1n!> has joined #yocto21:02
kanavin_homekhem: I think the use case for the tarball is supporting modern yocto on ancient distros (by providing modern native toolchain), not the other way around21:03
kanavin_homekhem: if you need to build ancient yocto on a modern distro, your best bet is a ubuntu 14.04 docker container which is very easy to install21:03
*** Sandrita <Sandrita!18ca2637@gateway/web/cgi-irc/> has quit IRC21:03
khemI know that but it works both ways21:09
RPkhem: "bitbake buildtools-extended-tarball" :)21:09
khemRP has done builds for sumo21:09
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC21:09
RPkanavin_home: it does work both ways21:09
khemRP: heh21:09
RPkhem: was my test of backporting to build an older tarball21:10
RPkhem: its obviously out of date now21:10
*** berton <berton!~berton@> has quit IRC21:14
*** NiksDev <NiksDev!~NiksDev@> has quit IRC21:16
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto21:16
*** dkl__ <dkl__!> has quit IRC21:28
*** m1ster_r0b0t <m1ster_r0b0t!> has joined #yocto21:32
*** vineela1 <vineela1!~vtummala@> has joined #yocto21:34
*** vineela <vineela!~vtummala@> has quit IRC21:34
*** paulg <paulg!> has quit IRC21:38
*** edgar444 <edgar444!uid214381@gateway/web/> has quit IRC21:38
*** pohly <pohly!> has quit IRC21:39
RPHmm, tests failed in deployment :(21:39
*** khem <khem!~khem@unaffiliated/khem> has quit IRC21:40
*** JaMa <JaMa!~martin@> has quit IRC21:42
*** hpsy <hpsy!~hpsy@> has quit IRC21:49
*** woutervh <woutervh!~woutervh@> has quit IRC21:49
*** hpsy <hpsy!~hpsy@> has joined #yocto21:49
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC22:08
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto22:14
*** goliath <goliath!> has quit IRC22:21
RP"As new processors are deployed in the marketplace, the behavior of this option will change."22:40
*** vineela1 <vineela1!~vtummala@> has quit IRC22:41
*** paulg <paulg!> has joined #yocto22:50
denixRP: a case of extreme CYA?22:51
RPdenix: no, the behaviour of gcc is now depending on the system you run it on :/22:52
*** vineela <vineela!~vtummala@> has joined #yocto22:53
*** fl0v0 <fl0v0!~fvo@2a01:c23:601a:2f00:40b6:9542:8968:c5e0> has quit IRC22:56
*** agust <agust!> has quit IRC23:03
* RP gives up and will have to look at this more tomorrow23:12
*** vineela1 <vineela1!~vtummala@> has joined #yocto23:13
*** vineela <vineela!~vtummala@> has quit IRC23:13
*** dev1990 <dev1990!> has quit IRC23:15
yoctiNew news from stackoverflow: bitbake rpi-test-image with MACHINE=raspberrypi3-64 failing to build on the zeus release of yocto <>23:19
*** vineela <vineela!~vtummala@> has joined #yocto23:28
*** vineela1 <vineela1!~vtummala@> has quit IRC23:28
*** leon-anavi <leon-anavi!~Leon@> has quit IRC23:44

Generated by 2.17.2 by Marius Gedminas - find it at!