Wednesday, 2020-11-04

*** mbulut <mbulut!> has quit IRC00:03
*** rsalveti <rsalveti!uid117878@gateway/web/> has quit IRC00:03
*** awafaa <awafaa!sid716@gateway/web/> has quit IRC00:03
*** awafaa <awafaa!sid716@gateway/web/> has joined #yocto00:04
*** dagmcr_ is now known as dagmcr00:04
*** mbulut <mbulut!> has joined #yocto00:05
*** rsalveti <rsalveti!uid117878@gateway/web/> has joined #yocto00:06
tastycactusThanks smurray, mccc00:07
*** tastycactus <tastycactus!> has quit IRC00:07
*** agust <agust!> has quit IRC00:08
*** vineela <vineela!vtummala@nat/intel/x-ipgkjveqooqpdvin> has quit IRC00:19
*** stbenz615515 <stbenz615515!> has quit IRC00:23
*** stbenz615515 <stbenz615515!> has joined #yocto00:26
*** Androo <Androo!> has quit IRC00:26
*** flery <flery!> has quit IRC00:31
*** mbulut <mbulut!> has quit IRC00:31
*** vineela <vineela!~vtummala@> has joined #yocto00:44
*** Batman_ <Batman_!~Batman@> has joined #yocto01:02
*** Batman_ <Batman_!~Batman@> has quit IRC01:07
*** vineela <vineela!~vtummala@> has quit IRC01:34
*** paulg <paulg!> has quit IRC01:36
*** NiksDev <NiksDev!~NiksDev@> has quit IRC01:39
*** wooosaiii <wooosaiii!> has joined #yocto01:41
*** wooosaiiii <wooosaiiii!> has quit IRC01:41
*** paulg <paulg!> has joined #yocto01:49
JaMawho have eaten bison? with latest oe-core I'm seeing binutils-cross-arm/2.35-r0/git/missing: bison: not found; and dtc-native failing with | make: bison: Command not found01:51
*** B0ned1ger <B0ned1ger!> has joined #yocto01:51
JaMait's that issue again: WARNING: binutils-cross-arm-2.35-r0 do_configure: Manifest sstate-control/manifest-x86_64-bison-native.populate_sysroot not found in x86_64 (variant '')?01:52
*** Batman_ <Batman_!~Batman@2601:647:4500:eb90:7093:192b:c33d:9d21> has joined #yocto01:53
*** B0ned1ger <B0ned1ger!> has quit IRC01:56
*** Batman_ <Batman_!~Batman@2601:647:4500:eb90:7093:192b:c33d:9d21> has quit IRC01:58
opellohi, trying to follow the "secondary toolchain" workflow and my trivial recipe with the trivial toolchain ends up failing because quilt-native is blacklisted for the gnu toolchain, i went with the "whitelist" (because i want to opt recipes in to the secondary toolchain) and i guess i'm wondering where i went wrong and if there's a better example or if i should show a complete example?02:11
opellomy goal is to have a newer gcc to use for some recipes that i can opt-in to it02:15
*** camus1 <camus1!~Instantbi@> has joined #yocto02:24
*** kaspter <kaspter!~Instantbi@> has quit IRC02:24
*** camus1 is now known as kaspter02:24
*** wooosaiii <wooosaiii!> has quit IRC02:28
*** wooosaiii <wooosaiii!> has joined #yocto02:28
*** kaspter <kaspter!~Instantbi@> has quit IRC02:39
*** kaspter <kaspter!~Instantbi@> has joined #yocto02:39
*** kaspter <kaspter!~Instantbi@> has quit IRC02:44
*** vineela <vineela!~vtummala@> has joined #yocto02:46
*** kaspter <kaspter!~Instantbi@> has joined #yocto02:46
*** kaspter <kaspter!~Instantbi@> has joined #yocto02:47
*** camus1 <camus1!~Instantbi@> has joined #yocto02:55
*** vineela <vineela!~vtummala@> has quit IRC02:55
*** kaspter <kaspter!~Instantbi@> has quit IRC02:56
*** camus1 is now known as kaspter02:56
*** kiwi_29_ <kiwi_29_!> has quit IRC02:57
*** ericch <ericch!> has quit IRC03:00
*** kaspter <kaspter!~Instantbi@> has quit IRC03:10
*** kaspter <kaspter!~Instantbi@> has joined #yocto03:12
*** sakoman <sakoman!> has quit IRC03:13
*** kiwi_29 <kiwi_29!> has joined #yocto03:22
*** ahadi <ahadi!~ahadi@> has quit IRC03:24
*** ahadi <ahadi!~ahadi@> has joined #yocto03:24
*** khem <khem!~khem@unaffiliated/khem> has quit IRC03:29
*** khem[m] <khem[m]!khemmatrix@gateway/shell/> has joined #yocto03:32
*** stephano <stephano!> has quit IRC03:33
*** onkelpit <onkelpit!> has quit IRC03:34
*** khem[m] is now known as khem03:34
*** khem is now known as Guest981603:35
*** onkelpit <onkelpit!> has joined #yocto03:36
*** Guest9816 <Guest9816!khemmatrix@gateway/shell/> has quit IRC03:38
*** Guest9816 <Guest9816!khemmatrix@unaffiliated/khem> has joined #yocto03:38
*** Guest9816 <Guest9816!khemmatrix@gateway/shell/> has joined #yocto03:38
*** B0ned1ger <B0ned1ger!> has joined #yocto03:52
*** B0ned1ger <B0ned1ger!> has quit IRC03:57
*** dreyna <dreyna!~dreyna@2601:646:4201:e280:6cf8:16d7:727d:3be6> has quit IRC03:58
*** kiwi_29 <kiwi_29!> has quit IRC04:01
*** rcw <rcw!~rcwoolley@> has quit IRC04:14
*** kpo_ <kpo_!> has quit IRC04:24
*** B0ned1ger <B0ned1ger!> has joined #yocto04:24
*** kpo_ <kpo_!> has joined #yocto04:24
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC04:26
*** B0ned1ger <B0ned1ger!> has quit IRC04:30
*** kiwi_29 <kiwi_29!> has joined #yocto04:36
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has quit IRC04:36
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has joined #yocto04:43
roussinmI was wondering if this is the style of code you are using inside bitbake python:  instead of `return fn in self.clean` ?04:57
*** B0ned1ger <B0ned1ger!> has joined #yocto05:05
*** B0ned1ger <B0ned1ger!> has quit IRC05:10
*** kaspter <kaspter!~Instantbi@> has quit IRC05:28
*** kaspter <kaspter!~Instantbi@> has joined #yocto05:28
*** oberstet <oberstet!~oberstet@> has joined #yocto05:37
*** derRichard <derRichard!> has quit IRC05:42
*** derRichard <derRichard!> has joined #yocto05:43
*** paulg <paulg!> has quit IRC05:45
*** paulg <paulg!> has joined #yocto05:45
*** B0ned1ger <B0ned1ger!> has joined #yocto05:45
*** B0ned1ger <B0ned1ger!> has quit IRC06:03
*** kaspter <kaspter!~Instantbi@> has quit IRC06:04
*** kaspter <kaspter!~Instantbi@> has joined #yocto06:04
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto06:07
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto06:09
*** kiwi_29 <kiwi_29!> has quit IRC06:15
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/> has quit IRC06:23
*** feddischson <feddischson!> has joined #yocto06:25
*** AndersD <AndersD!> has joined #yocto06:26
*** beneth` <beneth`!> has joined #yocto06:28
*** feddischson <feddischson!> has quit IRC06:29
*** mbulut <mbulut!> has joined #yocto06:34
*** hpsy <hpsy!~hpsy@> has joined #yocto06:39
*** pohly <pohly!> has joined #yocto06:46
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto06:48
*** RPI_IMX6 <RPI_IMX6!> has joined #yocto06:51
*** agust <agust!> has joined #yocto07:10
*** kiwi_29 <kiwi_29!> has joined #yocto07:17
*** kiwi_29 <kiwi_29!> has quit IRC07:22
*** frsc <frsc!> has joined #yocto07:35
*** RPI_IMX6 <RPI_IMX6!> has quit IRC07:51
mcfriskHey! yocto 3.2 gatesgarth is out, well done everyone!07:53
*** mckoan|away is now known as mckoan08:00
*** fl0v0 <fl0v0!~fvo@> has joined #yocto08:03
*** camus1 <camus1!~Instantbi@> has joined #yocto08:12
*** kaspter <kaspter!~Instantbi@> has quit IRC08:12
*** camus1 is now known as kaspter08:12
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has joined #yocto08:18
LetoThe2ndyo dudX08:20
*** carlsb3rg <carlsb3rg!~chrissc@> has joined #yocto08:23
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto08:32
*** ThomasD13 <ThomasD13!> has joined #yocto08:37
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:4058:61b0:c454:74b5> has joined #yocto08:37
*** hcg <hcg!51dddd33@> has joined #yocto08:38
*** micka_ <micka_!> has joined #yocto08:38
*** micka_ is now known as micka08:39
*** B0ned1ge_ <B0ned1ge_!> has joined #yocto08:40
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:42
*** B0ned1ger2 <B0ned1ger2!> has quit IRC08:43
*** B0ned1ge_ <B0ned1ge_!> has quit IRC08:45
*** PaowZ <PaowZ!~vince@2a01:e35:398b:6180:bd4b:69b5:830e:8d3d> has joined #yocto08:46
*** kpo_ <kpo_!> has quit IRC08:49
*** kpo_ <kpo_!> has joined #yocto08:50
*** goliath <goliath!> has joined #yocto08:54
*** tnovotny <tnovotny!> has joined #yocto09:00
*** dominick <dominick!> has joined #yocto09:01
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto09:01
*** dominick <dominick!> has quit IRC09:01
*** rsalveti <rsalveti!uid117878@gateway/web/> has quit IRC09:15
*** vdehors_ <vdehors_!> has joined #yocto09:19
*** vdehors <vdehors!> has quit IRC09:19
*** w00die <w00die!~w00die@> has quit IRC09:20
*** w00die <w00die!~w00die@> has joined #yocto09:22
ka6soxOnce the parse is done on a build Bitbake has already put everything in its cache and changing a recipe has no effect for that build?09:45
*** dleppich <dleppich!> has joined #yocto09:46
*** hcg <hcg!51dddd33@> has quit IRC09:52
*** kaspter <kaspter!~Instantbi@> has quit IRC09:52
*** camus1 <camus1!~Instantbi@> has joined #yocto09:52
*** problame_ <problame_!> has joined #yocto09:53
*** camus1 is now known as kaspter09:55
*** problame <problame!> has quit IRC09:56
*** tnovotny <tnovotny!> has quit IRC10:03
*** PaowZ <PaowZ!~vince@2a01:e35:398b:6180:bd4b:69b5:830e:8d3d> has quit IRC10:18
*** Ox861726f6c64 <Ox861726f6c64!~Ox861726f@gateway/tor-sasl/ox861726f6c64> has joined #yocto10:18
*** lxc <lxc!> has joined #yocto10:29
lxccan I augment a machine configuration? E.g. say I want to append some values to machine qemux86.conf without defining a new machine.10:29
LetoThe2ndlxc: new machine that pulls in the original file, and only "augments" :)10:35
LetoThe2ndlxc: technically you can inject stuff through local.conf for debugging/development, but ... well, its meant to go into a machine config.10:36
lxcyes, but then I would have to create a new machine type, say qemux86-extra.conf.10:36
lxcbut I want to keep the same machine name. recipes supports this with bbappend, but not conf files?10:37
LetoThe2ndlxc: nope, it doesn't work like that with conf files.10:38
lxccan I set PREFERRED_PROVIDER per machine type?10:40
lxce.g. PREFERRED_PROVIDER_qemux86_virtual/kernel ?10:40
LetoThe2ndof course, thats one of the primary usecases of a machine config10:47
LetoThe2ndah you mean, set somewhere OTHER than the machine confi? it depends. you can not in a recipe, affecting another recipe.10:47
*** florian_kc is now known as florian10:52
*** kpo_ <kpo_!> has quit IRC10:54
*** kpo_ <kpo_!> has joined #yocto10:54
*** tnovotny <tnovotny!> has joined #yocto11:18
*** kiwi_29 <kiwi_29!> has joined #yocto11:20
*** kiwi_29 <kiwi_29!> has quit IRC11:24
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto11:30
*** berton <berton!> has joined #yocto11:41
*** kpo_ <kpo_!> has quit IRC11:41
*** kpo_ <kpo_!> has joined #yocto11:41
*** kaspter <kaspter!~Instantbi@> has quit IRC11:43
*** kaspter <kaspter!~Instantbi@> has joined #yocto11:43
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto12:29
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:4058:61b0:c454:74b5> has quit IRC12:33
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:3999:903d:9c8d:1590> has joined #yocto12:33
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:3999:903d:9c8d:1590> has quit IRC12:38
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:c35:5be4:b4ac:11ba> has joined #yocto12:39
RobertBerger@LetoThe2nd: maybe @lxc means machine overrides?12:43
LetoThe2nd@RobertBerger maybe. but those do just affect the current recipe, hence as usual: it depends(TM)12:45
lxcRobertBerger LetoThe2nd I think I found a way, I created a new machine file and inside the file set MACHINE=12:45
lxcDoes that seems like a correct approach?12:45
LetoThe2ndhalfways. it will work probably, but confuse others that use the metadata, hence i did not mention that way. i would probably file it under "hack"12:46
*** mattia_ <mattia_!~mattia@> has joined #yocto12:59
mattia_Hi, I am using bitbake in a CI pipeline with a failing task, but bitbake does not seem to return a standard error output, any idea how I could make that happen?13:02
*** kaspter <kaspter!~Instantbi@> has quit IRC13:08
*** kaspter <kaspter!~Instantbi@> has joined #yocto13:09
*** tolszak <tolszak!~tolszak@> has quit IRC13:14
*** eduardas <eduardas!> has joined #yocto13:19
*** Ninic0c0 <Ninic0c0!> has joined #yocto13:23
Ninic0c0Hi guys! thanks to your help i'm now able to have useful CI workflow. Question regarding a shared SSTATE_CACHE shared between to Docker images running Yocto. If the 1st containers makes some changes on a package, the second one is able to detect changes ? Thx :)13:25
LetoThe2ndNinic0c0: please rephrase, i don't think the sentence makes sense as is.13:30
Ninic0c0Ok sorry my english is not really Goog. I have 2 Docker images sharing same SSTATE_CACHE. If the first one make some changes inside this package (means change recipe contains, SRCREV, add patch...) the second Docker image will be able to see differences ?13:33
Ninic0c0I hope to be clear ...13:33
rburtonassuming the second docker has the same recipe changes, it will find the sstate-cache files for those yes13:33
rburtonit won't magically use the files from sstate without the corresponding recipe changes13:34
*** Ox861726f6c64 <Ox861726f6c64!~Ox861726f@gateway/tor-sasl/ox861726f6c64> has quit IRC13:35
LetoThe2ndNinic0c0: i guess you're thinking backwards. its like this: if the build process in one container encounters a recipe, then it looks at the sstate if there is somethign that matches the exact state of the recipe. if it finds something, then it is used. if not, it is being (re)built13:41
Ninic0c0rburton and LetoThe2nd Thank you guys it's clear now13:41
LetoThe2ndNinic0c0: so if both (dockerized) builders share the same modified recipe sources, then the build will reuse the sstate. if their recipes are different, then not. it is always "build looks at sstate, then uses." never "sstate says 'hey ive' got something newer for you'"13:42
*** sakoman <sakoman!> has joined #yocto13:53
*** ak77 <ak77!> has joined #yocto13:55
ak77hello all!13:55
*** problame_ <problame_!> has quit IRC13:55
*** problame <problame!> has joined #yocto13:56
*** Sibert <Sibert!b98ee383@> has joined #yocto14:04
SibertSay that a distro is defined in layer A, is it possible to append to that distro from Layer B?14:04
Sibertsomething like confappend :P14:05
LetoThe2ndat least not in a somewhat clean way14:05
*** pbb <pbb!> has quit IRC14:10
*** pbb <pbb!> has joined #yocto14:11
SibertAnd some form of inclusion from a distro file from B in the A distro?14:18
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/> has joined #yocto14:21
LetoThe2ndyou can happily include other distros, and add/modify their content. look at poky-bleeding.conf for an example.14:21
*** kaspter <kaspter!~Instantbi@> has quit IRC14:26
*** kaspter <kaspter!~Instantbi@> has joined #yocto14:26
Sibertokay thanks14:26
nohithi using .bbappend file, how can i replace the images with my own ?
nohitor is the easiest way just to copy everything, make my own receipe and edit the Makefile and replace the images with my own ?14:31
*** Sibert <Sibert!b98ee383@> has quit IRC14:32
LetoThe2ndnohit: in the given example a stupid copy'n'patch does the trick probably.14:33
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC14:33
nohitLetoThe2nd: ok thanks14:35
nohiti found this but its for the poky psplash
nohiti was hoping for similar easy solution14:36
*** ericch <ericch!> has joined #yocto14:42
LetoThe2ndnohit: i can neither confirm nor deny that this works, never used that way.14:44
*** kaspter <kaspter!~Instantbi@> has quit IRC14:48
*** kaspter <kaspter!~Instantbi@> has joined #yocto14:49
*** ikke43 <ikke43!> has joined #yocto14:51
ikke43I'm lost...14:51
ikke43I have a Petalinux project.  Doesn't matter, it's yocto after all.14:51
ikke43I have a bbappend that add patches.14:51
ikke43And I can see them applied in the do.log_patch file.14:52
ikke43When I go to the linux-xlnx code checked out with devtool modify linux-xlnx, I can see the patches applied to the git repo.14:52
ikke43But I'm just behind the commits of these patches.14:53
*** dmoseley` <dmoseley`!~user@> has joined #yocto14:53
ikke43So: who is forcing me to say behind the applied patches?14:53
*** dmoseley` <dmoseley`!~user@> has quit IRC14:53
*** phlifish_ <phlifish_!~megabread@2a01:4b00:e031:2600:c35:5be4:b4ac:11ba> has joined #yocto14:53
ikke43First, it thought it was a do_patch[noexec] = "1'.14:53
ikke43But I can't find it.14:54
ikke43and unsetting it didn't help.14:54
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:c35:5be4:b4ac:11ba> has quit IRC14:54
*** armpit <armpit!~armpit@2601:202:4180:a5c0:5c1c:9520:3cc8:c75e> has quit IRC14:54
*** rcw <rcw!~rcwoolley@> has joined #yocto14:55
*** armpit <armpit!~armpit@2601:202:4180:a5c0:30:8e77:15b6:d55c> has joined #yocto14:56
*** ThomasD13 <ThomasD13!> has quit IRC15:00
*** megabread <megabread!~megabread@> has joined #yocto15:02
*** mbulut <mbulut!> has quit IRC15:03
*** phlifish_ <phlifish_!~megabread@2a01:4b00:e031:2600:c35:5be4:b4ac:11ba> has quit IRC15:04
*** PaowZ <PaowZ!~vince@> has joined #yocto15:08
*** ssajal <ssajal!> has joined #yocto15:11
*** xtron <xtron!~xtron@> has joined #yocto15:12
*** ikke43 <ikke43!> has quit IRC15:15
*** ikk3 <ikk3!> has joined #yocto15:17
*** fl0v0 <fl0v0!~fvo@> has quit IRC15:42
*** dleppich <dleppich!> has quit IRC15:44
*** dleppich <dleppich!> has joined #yocto15:46
*** dleppich <dleppich!> has quit IRC15:46
*** dleppich <dleppich!> has joined #yocto15:47
*** phlifish_ <phlifish_!~megabread@2a01:4b00:e031:2600:bd55:49fa:e7c3:6bde> has joined #yocto15:48
*** megabread <megabread!~megabread@> has quit IRC15:49
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/> has quit IRC15:49
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/> has joined #yocto15:51
*** dleppich <dleppich!> has quit IRC15:52
*** rcoote <rcoote!> has joined #yocto15:54
*** B0ned1ger2 <B0ned1ger2!> has quit IRC15:55
*** ikk3 <ikk3!> has quit IRC15:58
*** lxc <lxc!> has quit IRC16:01
*** AndersD <AndersD!> has quit IRC16:02
*** Batman_ <Batman_!~Batman@2601:640:10a:bc3d:5dd5:6db5:f865:c25d> has joined #yocto16:05
manuel1985Are the presentations from the Yocto Project Summit last week online somewhere?16:06
*** wattj <wattj!~wattj@2605:a601:ac3d:c100:e3e8:d9:3a56:e27d> has joined #yocto16:10
*** wattj <wattj!~wattj@2605:a601:ac3d:c100:e3e8:d9:3a56:e27d> has left #yocto16:10
*** Batman_ <Batman_!~Batman@2601:640:10a:bc3d:5dd5:6db5:f865:c25d> has quit IRC16:21
*** otavio__ is now known as otavio16:23
*** JPEW_ <JPEW_!~JPEW@2605:a601:ac3d:c100:e3e8:d9:3a56:e27d> has joined #yocto16:25
*** frsc <frsc!> has quit IRC16:26
*** JPEW_ <JPEW_!~JPEW@2605:a601:ac3d:c100:e3e8:d9:3a56:e27d> has quit IRC16:27
*** Ox861726f6c64 <Ox861726f6c64!~Ox861726f@gateway/tor-sasl/ox861726f6c64> has joined #yocto16:28
*** JPEW_ <JPEW_!~JPEW@2605:a601:ac3d:c100:e3e8:d9:3a56:e27d> has joined #yocto16:28
*** Ninic0c0 <Ninic0c0!> has quit IRC16:28
*** zbooth <zbooth!> has quit IRC16:31
*** JPEW <JPEW!~JPEW@2600:1f16:181:f300:d350:982:b6f5:216c> has quit IRC16:31
*** JPEW_ is now known as JPEW16:32
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto16:38
mckoanmanuel1985: AFAIK not yet16:40
smurraymanuel1985: the slides are available via the schedule if that helps:
*** kpo_ <kpo_!> has quit IRC16:45
*** kpo_ <kpo_!> has joined #yocto16:46
*** azzentys <azzentys!~azzentys@2601:281:8081:43e0:2870:989e:ac3:2d5d> has joined #yocto16:48
*** azzentys <azzentys!~azzentys@2601:281:8081:43e0:2870:989e:ac3:2d5d> has left #yocto16:50
mckoanmanuel1985: I though presentations=videos, sorry16:55
eduardassome videos are available here for those who might not be aware:
mckoaneduardas: ELCE!=YPSummit though16:58
eduardasmckoan: but as far as I understand there is quite a bit of overlap?16:59
eduardasfor example, Robert Bergers meta-virtualization video is listed on the elinux page17:03
*** abelal <abelal!~quassel@> has quit IRC17:03
*** abelal <abelal!~quassel@> has joined #yocto17:03
*** mckoan is now known as mckoan|away17:06
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto17:11
*** w00die <w00die!~w00die@> has quit IRC17:16
*** rabbit9911 <rabbit9911!> has joined #yocto17:16
opellohi, if i need to build a few packages with a newer version of gcc, how practical is that going to be?  i saw the "secondary toolchain" wiki page but the blacklist is tripping me up for quilt-native (which should presumably use the native tools and not be affected?)17:17
*** w00die <w00die!~w00die@> has joined #yocto17:18
rabbit9911Is there a way to have yocto build a toolchain for -native packages?17:23
rburtonhow would you build it? :)17:30
rabbit9911Build it with the hosttools gcc :)17:30
rburtonso if you trust the host gcc to build a compiler, why don't you trust it for the other -native packages?17:30
*** B0ned1ger <B0ned1ger!> has joined #yocto17:32
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC17:34
*** B0ned1ger2 <B0ned1ger2!> has quit IRC17:34
opelloif the hosttools gcc is old (as is my case) it might be nice :) but i can appreciate how that is an edge case17:36
*** vineela <vineela!~vtummala@> has joined #yocto17:37
kergothIf you can't trust your host, that's when it's time to do your builds in docker or another container17:44
kergothyou can do so almost entirely transparently, you don't have to move your dev tooling into the thing17:44
kergothi.e. pyrex17:45
rburtonopello: containers, or use the buildtools tarball which does in fact contain a native gcc built by yocto17:45
kergothgood point, buildtools-tarball is handy17:45
*** geheimnis` <geheimnis`!~geheimnis@> has quit IRC17:46
*** carlsb3rg <carlsb3rg!~chrissc@> has left #yocto17:47
opellois it practical to use buildtools-tarball and maybe even a future version esdk as a secondary toolchain for some subset of recipes?17:47
kergothwhy wouldn't you use it for everything?17:48
kergotha subset seems like just adding needless complexity17:48
*** hpsy <hpsy!~hpsy@> has quit IRC17:48
*** geheimnis` <geheimnis`!~geheimnis@> has joined #yocto17:50
opelloto avoid rebuilding libc and everything so that ongoing updates via the package feed don't reinstall the entire system17:50
opello(i'm trying to figure out just how practical of a goal that is to satisfy, if it's not practical, the solution is probably going to be reimage to a newer distribution, which is nicer for me anyway, but presents a more complex ongoing environment to support)17:53
*** rabbit9911 <rabbit9911!> has quit IRC17:53
*** hpsy <hpsy!~hpsy@> has joined #yocto17:54
*** vineela <vineela!~vtummala@> has quit IRC17:54
kergothi can't imagine sourcing the buildtools tarball would result in rebuilds of target packages. bitbake doesn't track the host's toolchain17:55
opellosorry, i thought you were addressing the 'future version esdk as a secondary toolchain for some subset of recipes'17:56
*** vineela <vineela!~vtummala@> has joined #yocto18:14
*** kiwi_29 <kiwi_29!> has joined #yocto18:24
*** xtron <xtron!~xtron@> has quit IRC18:25
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC18:28
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto18:30
*** eduardas <eduardas!> has quit IRC18:53
*** mbulut <mbulut!> has joined #yocto18:54
*** robbawebba <robbawebba!~rob@> has joined #yocto18:56
*** RPi_IMX6 <RPi_IMX6!> has joined #yocto19:06
robbawebbaHello, I have a question about PARALLEL_MAKE. I'm experiencing some strange "hanging" of bitbake tasks when building on a virtual server instance in the cloud (N1 on Google Cloud Platform, I blieve). The instance has 32 vCPUs, and bitbake automatically uses 32 for BB_NUMBER_THREADS and PARALLEL_MAKE. I noticed in the ref manual that the recommended setting for PARALLEL_MAKE on large systems with19:19
robbawebbamany CPUs is "-j 20". Why 20? I'm going to try this setting shortly, but I wanted to see if people knew the reason behind this. Thanks in advance!19:19
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC19:20
*** kpo_ <kpo_!> has quit IRC19:20
*** kpo_ <kpo_!> has joined #yocto19:21
smurrayrobbawebba: AIUI the issue is you effectively can end up with BB_NUMBER_THREADS * PARALLEL_MAKE processes, as PARALLEL_MAKE currently isn't global across tasks19:22
smurrayrobbawebba: lowering one or the other some can keep load within what the machine can handle19:23
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/> has quit IRC19:38
*** rcoote <rcoote!> has quit IRC19:44
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC19:44
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto19:53
*** B0ned1ger <B0ned1ger!> has quit IRC19:55
*** B0ned1ger2 <B0ned1ger2!> has quit IRC19:58
Guest9816use containers is an option20:06
opelloas part of the build process of a single recipe?  or you mean for the over-all build?20:07
robbawebbasmurray: thanks! this makes sense. I'll try lowering one or both of these parameters.20:07
*** mbulut <mbulut!> has quit IRC20:10
marexhi, is the hello-world example from meta-xilinx-standalone known to be broken ? cortexr5fhf-vfpv3d16-xilinx-eabi/xilstandalone/v2020.1+gitAUTOINC+338150ab36-r0/git//scripts/': [Errno 2] No such file or directory20:18
marexits as if this script was just missing form the embeddedsw repo altogether20:18
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto20:30
*** kiwi_29 <kiwi_29!> has quit IRC20:32
*** kiwi_29 <kiwi_29!> has joined #yocto20:32
*** B0ned1ger2 <B0ned1ger2!> has quit IRC20:39
*** PaowZ <PaowZ!~vince@> has quit IRC20:50
*** kiwi_29 <kiwi_29!> has quit IRC20:55
*** dev1990 <dev1990!> has quit IRC20:56
*** dev1990 <dev1990!> has joined #yocto21:00
*** PaowZ <PaowZ!~vince@2a01:e0a:52a:1870:bd4b:69b5:830e:8d3d> has joined #yocto21:02
*** dev1990 <dev1990!> has quit IRC21:03
*** lexano <lexano!~lexano@> has quit IRC21:10
*** berton <berton!> has quit IRC21:13
*** kiwi_29 <kiwi_29!> has joined #yocto21:13
*** dev1990 <dev1990!> has joined #yocto21:14
smurraymarex: suspect you need to flag fray on that, see he's listed as one of the maintainers now21:15
* smurray refrains from making any meta-amd jokes21:16
*** phlifish_ <phlifish_!~megabread@2a01:4b00:e031:2600:bd55:49fa:e7c3:6bde> has quit IRC21:24
marexsmurray: fray == mark ?21:27
smurraymarex: yep21:28
marexah, thanks21:28
marexsmurray: it fails to build on native hardware too btw21:28
*** georgem_ <georgem_!~georgem@> has quit IRC21:30
*** georgem_ <georgem_!~georgem@> has joined #yocto21:31
*** robbawebba <robbawebba!~rob@> has quit IRC21:37
*** Ox861726f6c64 <Ox861726f6c64!~Ox861726f@gateway/tor-sasl/ox861726f6c64> has quit IRC21:39
*** aidanh <aidanh!~aidanh@unaffiliated/aidanh> has quit IRC21:39
*** robbawebba <robbawebba!> has joined #yocto21:39
*** aidanh <aidanh!~aidanh@unaffiliated/aidanh> has joined #yocto21:40
*** georgem_ <georgem_!~georgem@> has quit IRC21:44
*** georgem_ <georgem_!~georgem@> has joined #yocto21:44
*** georgem_ <georgem_!~georgem@> has quit IRC21:46
*** georgem__ <georgem__!~georgem@> has joined #yocto21:46
marexfray: hi, what's the state of meta-xilinx-standalone ? (see above)21:54
* zeddii pops some popcorn21:55
*** lexano <lexano!~lexano@> has joined #yocto22:01
*** lexano <lexano!~lexano@> has quit IRC22:06
*** pohly <pohly!> has quit IRC22:18
*** lexano <lexano!> has joined #yocto22:18
*** tnovotny <tnovotny!> has quit IRC22:18
*** Androo <Androo!> has joined #yocto22:21
*** Scoutboy <Scoutboy!~quassel@> has quit IRC22:23
*** guido_ <guido_!~quassel@> has joined #yocto22:23
AndrooAnyone familiar with compiling golang directly on a Yocto target?  I have it working up until I include a MySQL driver, at which point it tries to use cgo and fails with this error:   Clearly the sysroot directory is wrong here, but I'm unsure what to do about it.22:25
*** oberstet <oberstet!~oberstet@> has quit IRC22:30
marexzeddii: did I miss something ?22:30
marexzeddii: seems like here is a good place to discuss downstream vendor layer problems, no ?22:31
*** beneth` <beneth`!> has left #yocto22:31
robbawebbaAndroo: one suggestion I'd recommend is to re-assign the CC env variable to remove the --sysroot flag. My assumption is that all of the libraries/headers/dependencies should be on the target, and the sysroot flag would no longer be needed.22:32
*** lexano <lexano!> has quit IRC22:37
Androorobbawebba: whoa, "env CC=arm-poky-linux-gnueabi-gcc go run .." mayyy have worked!22:37
Androothis is what I get for not really knowing C22:38
robbawebbahaha don't worry I'm in the same boat. I22:39
robbawebbaI'm still learning all of this one day at a time22:39
rburtonAndroo: can you file a bug please.  the sysroot shouldn't be used on target obviously.22:41
Androorobbawebba: I was thrown headfirst into Yocto by my employer and finding I need some serious cross-compilation skills at times.22:41
rburtonAndroo:, build system - oe-core -> devtools22:41
Androorburton: will do.  This is something related to the packaging of go?22:43
robbawebbahaha we'll you're in for a wild ride! I started using yocto about 2 years ago for the same reason, and I've learned a lot since then. There's still a lot I don't know about Yocto and embedded development, but we just have to take it one day / one problem at a time. Your debugging skills will definitely increase if you stick with development! Yocto luckily makes most of it very easy :)22:44
Guest9816are you compiling go itself on target ?22:45
AndrooGuest9816: Yes.  Sort of helpful to do my development straight on my target, as there's hardware there I can't replicate elsewhere.22:46
Guest9816Androo:  or using the go compiler on target to compile other go app which has cgo pieces22:46
Guest9816do you have CC set in your shell ?22:46
AndrooGuest9816: do now22:47
Guest9816so the sysroot is being added by go compiler itself ?22:48
AndrooGuest9816: yes22:48
Guest9816I guess it will be good to run strings program on go compiler and search for sysroot perhaps its being added during cross building of go compiler22:49
Guest9816since we use cross-compiler to build the go compiler for target, its not a normal setup for bootstrapping go22:49
*** lexano <lexano!~lexano@> has joined #yocto22:50
*** ssajal <ssajal!> has quit IRC22:52
AndrooGuest9816: cross compiling works fine, but I need to be able to work on my target as my application ties together custom hardware (an RF serial modem), buttons, LEDs, a cell modem, etc ... not sure how I would work effectively otherwise.22:53
robbawebbaI'm pretty sure the go toolchain respects the CC and CXX env variables from the shell I doubt that CC was set within the go toolchain itself. Would CC be set in some other environment location on the target?22:53
Androorobbawebba: no CC environment variable was set when this error occurred, so I'll have to dig to find the source22:54
*** camus1 <camus1!~Instantbi@> has joined #yocto22:58
Guest9816Androo: its ok, I understand your dev env is fine, I would do same especially if I am writing things in go or rust22:59
*** kaspter <kaspter!~Instantbi@> has quit IRC22:59
*** camus1 is now known as kaspter22:59
Guest9816yeah cgo is a bridge to bring all C/C++ devs over to go :)23:00
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has quit IRC23:06
robbawebbaAndroo: gotcha. Well best of luck! It sounds like it'll be sorted out with the bug report on bugzilla23:19
robbawebbaI use a mix of Go and C apps on the product I work on, and I've been spending quite a lot of time on C apps lately. I miss Go!23:20
*** ssajal <ssajal!> has joined #yocto23:33
*** kiwi_29 <kiwi_29!> has quit IRC23:35
*** kiwi_29 <kiwi_29!> has joined #yocto23:36
*** kiwi_29 <kiwi_29!> has joined #yocto23:37
AndrooGuest9816: looks like sysroot is compiles straight into Go somehow, getting binary matches in /usr/lib/go/bin/go and /usr/lib/go/pkg/tool/linux_arm/cgo23:38
AndrooGuest9816: I'm wondering if it's related to
*** kpo_ <kpo_!> has quit IRC23:41
*** kpo_ <kpo_!> has joined #yocto23:42
Guest9816yes see `C{C,XX}_FOR_TARGET23:46
Guest9816are embedded during the make.bash process because they have to provided by23:46
Guest9816the user.`23:46
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC23:46
Guest9816so naturally it is going to embed the cross compiler since that is what is setting these vars during build of go compiler for target23:46
*** leon-anavi <leon-anavi!~Leon@> has quit IRC23:55
*** agust <agust!> has quit IRC23:59

Generated by 2.17.2 by Marius Gedminas - find it at!