Wednesday, 2017-05-24

*** jairglez <jairglez!~jairdeje@> has quit IRC00:02
*** msvb-lab <msvb-lab!> has quit IRC00:05
*** majuk <majuk!> has quit IRC00:09
*** dorileo <dorileo!dorileo@nat/intel/x-tjngswbjesqihcis> has quit IRC00:24
*** majuk <majuk!> has joined #yocto00:26
*** majuk <majuk!> has quit IRC00:30
*** nighty-- <nighty--!> has joined #yocto00:31
*** seebs <seebs!> has quit IRC00:31
*** dvhart <dvhart!> has joined #yocto00:32
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC00:34
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto00:36
*** seebs <seebs!> has joined #yocto00:41
Crofton|workclearly we need meta-hurd00:47
paulgCrofton|work, don't be pinning that crime on me.  :)00:49
Crofton|workmeta-buildroot exists00:50
paulgyou mean meta-brainrot ?00:50
*** fitzsim <fitzsim!> has quit IRC00:57
*** rburton <rburton!> has joined #yocto01:01
*** majuk <majuk!> has joined #yocto01:02
*** majuk <majuk!> has quit IRC01:07
*** peacememories <peacememories!> has joined #yocto01:08
*** peacememories <peacememories!> has quit IRC01:15
*** dvhart <dvhart!> has quit IRC01:26
*** kanavin <kanavin!~ak@> has quit IRC01:30
*** kanavin <kanavin!~ak@> has joined #yocto01:31
*** dvhart <dvhart!> has joined #yocto01:33
*** dvhart <dvhart!> has quit IRC01:33
*** Guest93352 <Guest93352!> has quit IRC01:39
*** majuk <majuk!> has joined #yocto01:39
*** majuk <majuk!> has quit IRC01:43
*** aehs29 <aehs29!~aehernan@> has quit IRC01:56
*** majuk <majuk!> has joined #yocto01:57
*** paulg <paulg!> has quit IRC01:59
*** majuk <majuk!> has quit IRC02:01
*** majuk <majuk!> has joined #yocto02:11
berndhsso after bitbake is done building, where does it put the resulting image?02:13
*** kanavin <kanavin!~ak@> has quit IRC02:14
*** majuk <majuk!> has quit IRC02:15
*** kanavin <kanavin!~ak@> has joined #yocto02:19
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has quit IRC02:19
*** sgw_ <sgw_!~sgw_@2601:1c0:6000:fe8::8b5f> has joined #yocto02:19
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has joined #yocto02:25
*** t0mmy <t0mmy!> has quit IRC02:28
*** majuk <majuk!> has joined #yocto02:31
*** kanavin <kanavin!~ak@> has quit IRC02:31
*** kanavin <kanavin!~ak@> has joined #yocto02:31
*** majuk <majuk!> has quit IRC02:35
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto02:36
*** dolapevich <dolapevich!~seba@> has joined #yocto02:47
Crofton|workberndhs, tmp-glibc/deploy/image....02:47
dolapevichGood Morning, afternoon, night, I am getting 14 kb while clonning yocto kernel02:48
dolapevichis it expected?02:48
dolapevichlinux-yocto-4.8.12+gitAUTOINC+c19322afb1_021b4aef55-r0 do_fetch (pid 25171)  10% |##                     | 16.3K/s02:48
berndhsCrofton|work: yes, i found it, thank you02:49
*** majuk <majuk!> has joined #yocto02:50
*** majuk <majuk!> has quit IRC02:55
*** dolapevich <dolapevich!~seba@> has quit IRC03:08
*** majuk <majuk!> has joined #yocto03:09
*** majuk <majuk!> has quit IRC03:14
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC03:18
*** seebs <seebs!> has quit IRC03:24
*** dolapevich <dolapevich!~seba@> has joined #yocto03:27
*** seebs <seebs!> has joined #yocto03:27
*** majuk <majuk!> has joined #yocto03:29
*** majuk <majuk!> has quit IRC03:33
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto03:34
*** berndhs <berndhs!> has left #yocto03:37
*** majuk <majuk!> has joined #yocto03:49
*** majuk <majuk!> has quit IRC03:53
*** majuk <majuk!> has joined #yocto04:09
*** majuk <majuk!> has quit IRC04:13
*** jmcruzal <jmcruzal!~jmcruzal@> has left #yocto04:26
*** jmcruzal <jmcruzal!~jmcruzal@> has joined #yocto04:27
*** majuk <majuk!> has joined #yocto04:27
*** majuk <majuk!> has quit IRC04:31
*** majuk <majuk!> has joined #yocto04:45
*** morphis <morphis!> has joined #yocto04:47
*** dolapevich <dolapevich!~seba@> has quit IRC04:50
*** majuk <majuk!> has quit IRC04:52
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC04:54
*** warthog9 <warthog9!> has quit IRC05:01
*** warthog9 <warthog9!> has joined #yocto05:05
*** jmcruzal <jmcruzal!~jmcruzal@> has quit IRC05:11
*** agust <agust!> has joined #yocto05:22
*** majuk <majuk!> has joined #yocto05:23
*** cornel <cornel!~cornel@> has quit IRC05:28
*** majuk <majuk!> has quit IRC05:28
*** rob_w <rob_w!~bob@> has joined #yocto05:38
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto05:38
*** majuk <majuk!> has joined #yocto05:42
*** majuk <majuk!> has quit IRC05:46
*** JaMa <JaMa!~martin@> has quit IRC05:46
*** gtristan <gtristan!~tristanva@> has quit IRC05:48
*** ilial <ilial!~ilial@> has joined #yocto05:53
*** pohly <pohly!> has joined #yocto05:54
*** CostinC <CostinC!> has joined #yocto05:54
CostinCmorning all05:54
*** majuk <majuk!> has joined #yocto06:00
*** majuk <majuk!> has quit IRC06:06
*** AndersD <AndersD!~anders@> has joined #yocto06:15
*** gtristan <gtristan!~tristanva@> has joined #yocto06:16
*** majuk <majuk!> has joined #yocto06:20
*** Bunio_FH <Bunio_FH!> has joined #yocto06:21
*** rj_ <rj_!58d39085@gateway/web/freenode/ip.> has joined #yocto06:26
*** majuk <majuk!> has quit IRC06:26
*** adca <adca!~adca@> has joined #yocto06:32
*** hamis <hamis!~irfan@> has joined #yocto06:36
rj_Morning. Is it possible to execute commands like "mysql -u root -p password < create_tables.sql" in a post build script or something like that?06:37
*** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.> has joined #yocto06:39
*** warthog9 <warthog9!> has quit IRC06:39
*** warthog9 <warthog9!> has joined #yocto06:40
*** csanchezdll <csanchezdll!> has joined #yocto06:41
*** majuk <majuk!> has joined #yocto06:42
*** majuk <majuk!> has quit IRC06:46
*** ant_work <ant_work!> has joined #yocto06:47
*** fl0v0 <fl0v0!> has joined #yocto06:49
*** t0mmy <t0mmy!> has joined #yocto06:55
ChrysDGood morning !06:57
*** majuk <majuk!> has joined #yocto07:00
top21Hello! How can I make my own custom module to load automatically at boot ? I've add it in KERNEL_MODULE_AUTOLOAD, but it's not working. Thanks for the help!07:00
*** ed2 <ed2!~Adium@> has joined #yocto07:01
*** frsc <frsc!> has joined #yocto07:04
*** majuk <majuk!> has quit IRC07:05
*** AndersD <AndersD!~anders@> has quit IRC07:09
*** Smitty_ <Smitty_!86bfdc4a@gateway/web/freenode/ip.> has joined #yocto07:15
*** rajm <rajm!~robertmar@> has joined #yocto07:17
*** majuk <majuk!> has joined #yocto07:18
*** yohboy <yohboy!> has joined #yocto07:19
*** blitz00 <blitz00!~stefan@unaffiliated/blitz00> has joined #yocto07:20
*** dreyna <dreyna!> has quit IRC07:22
*** majuk <majuk!> has quit IRC07:24
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto07:24
*** AndersD <AndersD!> has joined #yocto07:30
*** toscalix <toscalix!~toscalix@> has joined #yocto07:31
*** t0mmy <t0mmy!> has quit IRC07:36
Smitty_Starting with this:, I have added this line <CORE_IMAGE_EXTRA_INSTALL = "example"> to meta-custom/recipes-example/images/  So, why doesn't it show up in the full distro image ?07:38
*** majuk <majuk!> has joined #yocto07:38
*** Hunk <Hunk!ce7a6654@gateway/web/freenode/ip.> has joined #yocto07:41
HunkHello, I want to add a step in my recipe before configure07:41
Hunkthe command was do_configure_before(){ .... } or? And where i can find the documentation for the recipes?07:42
*** majuk <majuk!> has quit IRC07:43
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:44
Smitty_Never mind.  The application is being built as "helloworld" not "example"07:44
*** tasslehoff <tasslehoff!~Tasslehof@> has joined #yocto07:45
*** Snert <Snert!> has quit IRC07:45
tasslehoffWhat package do I need to install rpms on target?07:45
*** avalluri <avalluri!avalluri@nat/intel/x-gswhyphcyktdmmob> has quit IRC07:46
*** Snert <Snert!> has joined #yocto07:46
*** avalluri <avalluri!~avalluri@> has joined #yocto07:47
ChrysDSmitty_ : Don't you get an error?07:48
Smitty_I didn't see any error07:49
ChrysDSmitty_ : Like "example" couldn't be parsed or whatever07:49
ChrysDSmitty_ : Ok have you tried with IMAGE_INSTALL_append =07:50
*** Kakounet <Kakounet!> has joined #yocto07:50
Smitty_Well, it's installing the binary with the name helloworld.  I was expecting to find a binary named example.  It turns out I didn't need to add the EXTRA_IMAGE_INSTALL.  When I remove it, the binary is installed anyway07:51
*** yann <yann!> has quit IRC07:52
PinkSnake@Smitty --> install -m 0755 helloworld ${D}${bindir}07:52
Smitty_I don't see anyting which indicates that the helloworld app *should* be installed.  I guess it's automagic07:53
*** MarcWe <MarcWe!> has joined #yocto07:53
PinkSnake@Smitty take a look to the recipe in install function07:53
Smitty_Still *extremely* fussy over which file is used for which type of information.  Seems like random info scattered across at least 4 files just for my trivial example07:54
Smitty_So, that file says: if this particular binary target is supposed to be installed, install it like this.   BUT, that doesn't control whether the binary target gets installed07:56
*** majuk <majuk!> has joined #yocto07:56
Smitty_So, how do I control whether -  *not* how07:56
ChrysDSmitty_ : Look to the recipe07:59
ChrysDSmitty_ : And see where it is installed07:59
PinkSnake@Smitty nothing is supposed, you have a just a look to the recipe07:59
Smitty_I am supposed to be able to control *if* as well as *how* the target binary gets installed.  Where do I do that ?08:00
PinkSnake@Smitty in install function08:00
*** majuk <majuk!> has quit IRC08:01
PinkSnake@Smitty i don't understand what are you looking for,
PinkSnake@Smitty you a compile function to build the binary and an install function to deploy it in the system08:01
Smitty_The binary target recipe describes *how* to build the binary target, *how* to install it, *how* to do things.  But, the other aspect of the problem is *whether* the target binary *should* be installed or not08:02
ChrysDSmitty_ :  install -m 0755 helloworld ${D}${bindir}08:02
ChrysDSmitty_ : Have you checked there?08:02
Smitty_That describes *how* not *if*08:03
*** t0mmy <t0mmy!~tprrt@> has joined #yocto08:04
ChrysDSmitty_ : ?08:04
ChrysDSmitty_ : Have you checked in /usr/bin/08:04
Smitty_Yes, and the helloworld binary is present08:04
ChrysDSmitty_ : So no problem08:04
Smitty_Now, what if I don't want it to be there08:04
ChrysDSmitty_ : You change the recipe08:04
ChrysDSmitty_ : The best way is to do a .bbappend08:05
Smitty_Defintiely not, I would possibly not include the recipe in the layer, or maybe not include the layer in the distro, but the recipe is totally correct08:05
ChrysDSmitty_ : So if the recipe is totally correct you let in /usr/bin08:05
ChrysDSmitty_ : because the recipe is " i would like to compile a code and put in /usr/bin "08:05
ChrysDSmitty_ : If you are okay with that, so nothing to change08:06
ChrysDSmitty_ : If you're not happyt with /usr/bin08:06
ChrysDSmitty_ : You have to change the recipe, but not directly.08:06
Smitty_I want to control whether or not that particular binary target (a sub-component of the layer) gets installed. Example, instead of being a executable "hello world" it's actually a static library which some other component in my layer depends upon.  So, it has to be built, but not installed, or maybe it only gets installed in the SDK and the the OS08:08
Smitty_not the OS08:08
ChrysDSmitty_ : Ok so your unhappy with the recipe.08:08
ChrysDSmitty_ : You can suspect changes.08:08
Smitty_The recipe contains all the instructions for *HOW* to build, install, whatever, but it does not control *IF*08:09
ChrysDSmitty_ : If you parse the recipe, it will install08:09
Smitty_This is absolutely fundamental to how Yocto is designed08:09
ChrysDSmitty_ : Because the recipe is : " I would like to compile it, and install into the target in /usr/bin "08:10
ChrysDSmitty_ : the ${D} means the target directory if i remember08:10
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has joined #yocto08:12
Smitty_but each of those "actions" compile, install, whatever are essentially optional.  Just including a layer that includes a recipe to build a binary target does not necessarily mean I want that binary target installed in the OS, the SDK, whatever.  Something is controlling the circumstances under which that binary targets' do_install gets called08:12
ChrysDSmitty_ : right08:13
Smitty_And that someting is what ?08:13
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has quit IRC08:14
Smitty_How would I say, for example, build the binary target, but only install it in the SDK, not in the OS08:14
*** avalluri <avalluri!~avalluri@> has quit IRC08:14
ChrysDSmitty_ : the SDK guide maybe08:15
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has joined #yocto08:15
*** avalluri <avalluri!~avalluri@> has joined #yocto08:15
*** TobSnyder <TobSnyder!> has joined #yocto08:16
ChrysDSmitty_ : You would like to add files in the native sysroots for example08:18
Smitty_or, maybe, for whatever reason, suppress one file from the SDK but let that file show up in the OS image, or vice-versa08:19
ChrysDSmitty_ : I'm not at ease with it, as i'm new in yocto, you should consider looking to BBCLASSEXTEND08:19
ChrysDSmitty_ :
ChrysDSmitty_ : 7.77.08:21
ChrysDSmitty_ : Look to 7.78 also08:21
*** lucaceresoli <lucaceresoli!> has quit IRC08:22
*** Guest93352 <Guest93352!> has joined #yocto08:22
ChrysDIf you consider changing your job, let me know. I could be happy to be hired. Ahahah08:24
HunkHow i can add a custom job before do_configure08:25
Hunki know the function do_configure_append08:25
Hunkit is possible to write do_configure_before08:25
*** grma <grma!~gruberm@> has joined #yocto08:26
Smitty_I'm not at ease with it at all - becuase looking at all the different places for configuration, whether it be a single recipe for a hello world app which very strangely also includes a directory "images" which contains which does nothing but inherit from core-image, the layer configuration including a "distro" folder which doesn't appear to do anythgin at all, etc, etc, there's just too many places to look at to unders08:26
ChrysDSmitty_ : ok.08:27
ChrysDHunk : In a bbappend file, you can tell that you would like to do another task08:29
ChrysDHunk : like addtask  your_task  after the_task_you_want before the_task_you_want08:30
ChrysDHunk : 3.5.1. Promoting a Function to a Task
*** grma <grma!~gruberm@> has quit IRC08:32
Smitty_I'll ask again:  is there some guidance as to which configuration items are placed in which .conf files ?    Right now, I'm not seeing a pattern08:32
ChrysDSmitty_ : The best is to check the guides08:33
ChrysDSmitty_ : there is one guide very nice that tell you what everything does08:33
*** qt-x <qt-x!~Thunderbi@> has joined #yocto08:33
*** majuk <majuk!> has joined #yocto08:33
Smitty_yep, that's exactly my question - where in the "guide" is there "guidance" for this issue ?   Because I've searched, and can't find it08:34
ChrysDSmitty_ : Ok i will cherch for you08:34
ChrysDSmitty_ : In that guide :
ChrysDSmitty_ : you have 5 - Common Tasks08:36
ChrysDSmitty_ : it will help you of doing simple tasks08:36
ChrysDSmitty_ : In chapter 408:37
ChrysDSmitty_ : You have the development models08:37
Hunkok thank you08:38
*** t0mmy <t0mmy!~tprrt@> has quit IRC08:38
Hunki want to write some output message as log files08:38
Hunkas output08:38
Hunkbb.plain isn't working08:38
Hunkwhat is the best way for do this08:38
ChrysDHunk : you mean in the host?08:38
*** yann <yann!> has joined #yocto08:39
ChrysDHunk : What did you expect as output message as log files?08:39
*** majuk <majuk!> has quit IRC08:39
*** t0mmy <t0mmy!~tprrt@> has joined #yocto08:40
ChrysDHunk : I don't really know what you want but maybe you shuold consider doing some python functions witch print some messages. I'm not familiar if there is a "pre-buuilt" way of doing some log files.08:40
Hunki did08:42
Hunk() {08:42
Hunkand i wanted to add there a print that i can see it inside the build process08:42
*** avalluri <avalluri!~avalluri@> has quit IRC08:43
ChrysDHunk : and bb.plain doesn't work right?08:44
ChrysDHunk : I've checked that you can log with python. My bad i didn't understand initially when you say bb.plain08:44
Hunkit doesn't work08:44
Hunksry i didn't write my problem well08:46
ChrysDHunk : No it's because i'm not familiar with that08:46
ChrysDHunk : can you pastebin your recipe?08:47
ChrysDHunk : and .bbappend08:47
rj_Heya. Is it possible to execute commands like "mysql -u root -p password < create_tables.sql" in a post build script or something like that?08:47
ChrysDHunk : you can even try the bash way08:50
*** lucaceresoli <lucaceresoli!> has joined #yocto08:50
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC09:04
PinkSnake@rj_ ROOTFS_POSTPROCESS_COMMAND += " *shell_command*;" at the end of an image recipe.09:04
*** geoffrey_l <geoffrey_l!> has joined #yocto09:07
HunkI found it09:08
rj_PinkSnake: So in my example that would be "ROOTFS_POSTPROCESS_COMMAND += " mysql -u root -p < create_tables.sql;" ?09:08
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto09:08
Hunkbb.note not plain09:09
*** majuk <majuk!> has joined #yocto09:12
PinkSnakerj_ i think you have to write a shell function, i will past an example ;)09:12
rj_PinkSnake: That would be  nice ^^09:13
ChrysDHunk : yeah here :
*** majuk <majuk!> has quit IRC09:16
PinkSnakerj_ it's an example paste in to set root as sshusers09:16
ChrysDHunk : it tried it,it works09:17
ChrysDHunk : have put a bb.plain09:17
*** msvb-lab <msvb-lab!> has joined #yocto09:17
rj_PinkSnake: I see, alright thanks! I'll try it out for my case ^^09:17
ChrysDHunk : I have a append on a .bbappend09:18
ChrysDHunk : i put as a first line bb.plain09:18
PinkSnakerj_ with pleasure ;)09:18
ChrysDHunk : python do_env_append_mx6() {  bb.plain("test")  }09:19
*** majuk <majuk!> has joined #yocto09:30
*** majuk <majuk!> has quit IRC09:36
rj_Is there a way to make yocto keep the configured kernel source?09:43
PinkSnakerj_ yep09:44
PinkSnakerj_ i going to paste ;)09:44
PinkSnakerj_ it's maybe not a proper solution but it works ->
rj_PinkSnake: For what i need it for thats all it has to do, work ^^09:46
*** JaMa <JaMa!~martin@> has joined #yocto09:47
rj_PinkSnake: Will that make the kernel source available when i use the image?09:47
PinkSnakerj_ what ? what ? i didn't understand09:48
rj_PinkSnake: Because from what i see, the kernel source should be somewhere in /lib/modules/(uname -r)/kernel right?09:48
PinkSnakerj_ ha ok you want to sav all your sources ?09:48
PinkSnakerj_ and not .config file, sry my mistake09:49
PinkSnake@rj_ why don't save only the .config file ?09:49
rj_PinkSnake: Yea, i need them to compile a package after installing the image in my virtual machine09:49
*** majuk <majuk!> has joined #yocto09:50
PinkSnakerj_ you mean a kernel module ?09:50
*** zeenix <zeenix!~zeenix@> has joined #yocto09:51
rj_PinkSnake: I'm not sure tbh, all it says is: "configure: error: Failed to find Linux sources. Use --with-linux-dir!"09:51
ChrysDrj_ : have you the recipe?09:51
rj_ChrysD: It's not really a recipe this time, im compiling it after building, when i install the image in a virtual machine09:52
rj_ChrysD: But it seems the Linux sources are not installed in the image09:52
ChrysDrj_ : But did you realize it "once" you have added something in your project or have you all the time get that problem?09:53
Smitty_Why is bitbake build so many new components when I build the SDK image for my config.  I have already build the OS image.  Why would it need to do anything other than package up what it already built when it did that ?09:53
PinkSnake@rj_ you can also build kernel modules
rj_ChrysD: What do you mean by that exactly?09:54
ChrysDrj_ : I mean, did you get that message all the time?09:54
rj_ChrysD: yep09:54
PinkSnake@Smitty i think yocot needs to build several package to create the toolchain09:54
*** Bunio_FH <Bunio_FH!> has quit IRC09:54
rj_ChrysD: Everytime i run the configure script it gives this error09:55
Smitty_The toolchain is built before the rest of the components in my OS IMage, otherwise it couldn't build them09:55
nrossiSmitty_: SDK has a canadian cross compiler09:55
ChrysDrj_ : which?09:55
*** majuk <majuk!> has quit IRC09:56
rj_ChrysD: the configure script provided by the package09:57
Smitty_By default ?   How many people need that ?09:57
PinkSnake@rj_ could you share the package ?09:58
rj_ChrysD: The script looks for /lib/modules/$(version)/build09:58
rj_PinkSnake: should be this one:
nrossiSmitty_: depends, there are lots of cases where the SDK platform is very different from the build host. e.g. 64bit/32bit09:59
Smitty_What's the target for that cross compiler ?  The target OS ?09:59
PinkSnake@rj i mean the recipe :)10:00
PinkSnake@rj_ i mean the recipe :)10:00
rj_PinkSnake: As stated before, i'm not using a recipe10:00
nrossiSmitty_: well it will build a HOST->SDK compiler and a SDK->TARGET compiler which is shipped in the SDK10:00
PinkSnake@rj_ ok i will take look, but after lunch :D10:00
ChrysDrj_ : Me too ahah10:00
rj_PinkSnake: I build a yocto image, installed that in my virtualbox, and im installing it by hand10:00
rj_PinkSnake: Because i can't seem to get that package working with a recipe in any way10:01
nrossiSmitty_: sorry, for clarity in my previous message the HOST->SDK compiler is not shipped10:01
ChrysDrj_ : have you checked for example in the sysroots of your target that you have everything?10:01
PinkSnake@rj_ ok but you can also create the recipe to download the package, build it and depoy no ?10:01
rj_PinkSnake: If only it would be that easy ;-;10:01
rj_PinkSnake: I've been trying to get that package to work for the last 3 months10:02
ChrysDrj_ : it could be so nice to see which package is requesting the missing file.10:02
ChrysDrj_ : and also "which" missing file10:02
rj_ChrysD: i know what files are missing tho, they are located in "/home/viro/poky/build/tmp/work-shared/genericx86-64/kernel-build-artifacts"10:03
ChrysDrj_ : i mean, in the sysroots10:03
ChrysDrj_ : not in the workdir10:03
ChrysDrj_ : I have to go sorry10:03
rj_ChrysD: Np ^^10:04
*** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.> has quit IRC10:04
*** Bunio_FH <Bunio_FH!> has joined #yocto10:04
*** rburton <rburton!> has joined #yocto10:04
Smitty_When I build my target OS (without SDK) bitbake will first (probably always?) construct a HOST->TARGET toolchain.  Now, when I want an SDK, I might want a HOST->TARGET  and/or a TARGET->TARGET (or potentially a TARGET->OTHER_TARGET).  The Target->Target is the Canadian Cross ??  How do I suppress that being built ?10:05
rj_PinkSnake: Yea i tried installing it by recipe, with this:
PinkSnake@rj_ do you have an error log ?10:07
rj_PinkSnake: But it keeps giving errors, either libtool cant find some folder calle ".libs" or the header "stdlib.h" can't be found10:07
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto10:08
*** Hunk <Hunk!ce7a6654@gateway/web/freenode/ip.> has quit IRC10:08
*** mdnneo <mdnneo!~umaucher@> has joined #yocto10:09
nrossiSmitty_: you are probably not after the SDK, you should first determine if that is what you need (see
rj_PinkSnake: This is the latest log:
*** majuk <majuk!> has joined #yocto10:10
nrossiSmitty_: regards the compilers for the SDK, the canadian cross is the HOST building a compiler that runs on SDK which compiles for the TARGET. TARGET->TARGET is different again10:11
Smitty_I already know I want to build an SDK, but I don't think I will need or want a TARGET->ANYTHING toolchain for any value of ANYTHING.10:12
nrossiSmitty_: thats not what the SDK builds though10:13
*** berndhs <berndhs!> has joined #yocto10:13
Smitty_What ?  doesn't bitbake have to construct the HOST->TARGET toolchain before it does anything else related to constructing the target OS ?10:14
*** majuk <majuk!> has quit IRC10:14
nrossiSmitty_: now your just confusing yourself. You said you didn't want a TARGET->* compiler... that is not the same as a HOST->TARGET compiler...10:15
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto10:15
*** rburton <rburton!> has joined #yocto10:15
Smitty_I want to ship a toolchian which allows other developers to construct applications which can run on TARGET.  And, that toolchain will only run on HOST (which happens to be the machine I am build on)10:16
Smitty_That's the SDK - isn't it ?10:16
rburtonbitbake myimage -c populate_sdk, will generate the SDK for whatever is in myimage10:16
Smitty_So, why would building the SDK, also construct a Canadian Cross wwhich would then allow TARGET->SOMETHING ?10:17
rburtonmost likely because building gcc is "fun" and "interesting"10:17
rburtonand always involves more steps than you'd like10:18
Smitty_How do I suppress that TARGET->ANYTHING toolchain ?  I don't want that shipping out anywhere10:18
nrossiSmitty_: you didn't read my original message... it builds a compiler that runs on the "SDK" system which is essentially the same as your build host by default. It does not make a compiler that runs on your target10:18
rburtonSmitty_: the image wont contain a compiler unless you put it in, and the sdk will only contain a cross for your target10:23
*** JoiF <JoiF!~jofr@> has quit IRC10:23
*** JoiF <JoiF!~jofr@> has joined #yocto10:24
*** nighty-- <nighty--!> has quit IRC10:24
rj_rburton: Is there any way to get "/lib/modules/(uname -r)/build" linux sources installed on a yocto build?10:25
rburtonrj_: iirc, the package is kernel-sources.10:26
rj_rburton: Should i add that to my Cause nothing seems to provide that package10:28
rburtona five second grep tells me that kernel-devsrc contains the kernel sources, if that's what you want10:31
*** majuk <majuk!> has joined #yocto10:46
*** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.> has joined #yocto10:48
ChrysDrj_ : Something new?10:49
*** majuk <majuk!> has quit IRC10:50
PinkSnake../x86_64-pc-linux-gnu-libtool: line 7549: cd: .libs: No such file or directory10:52
PinkSnake@rj_ maybe you can try to bluid sdk and compile inside no ?10:53
*** Ramose <Ramose!c05e2222@gateway/web/freenode/ip.> has quit IRC11:02
rj_rburton: I found the same thing yea, build is just done11:03
rj_PinkSnake: The thing is, that .libs directory exists...11:03
*** qt-x <qt-x!~Thunderbi@> has quit IRC11:05
*** fl0v01 <fl0v01!> has joined #yocto11:07
PinkSnake@rj_ arf :S maybe you can try with -c devshell option to take a look insid...11:07
*** fl0v0 <fl0v0!> has quit IRC11:09
*** mappy <mappy!b9691ff9@gateway/web/freenode/ip.> has joined #yocto11:19
PinkSnake@rj_ in my opinion you should maybe to try --> inherit autotools + remove do_compile() & do_install() in .bb11:19
*** yohboy <yohboy!> has quit IRC11:20
*** majuk <majuk!> has joined #yocto11:22
*** majuk <majuk!> has quit IRC11:27
*** berton <berton!~berton@> has joined #yocto11:38
*** majuk <majuk!> has joined #yocto11:40
rj_PinkSnake: Tried that, doesn't work sadly :(11:42
*** majuk <majuk!> has quit IRC11:45
Smitty_Back from lunch - continuing the conversation about SDK11:55
*** majuk <majuk!> has joined #yocto11:59
Smitty_So, my question is:  I have already built the OS image.  Doing so requires building of a HOST->TARGET toolchain and also ends up retrieving and building what could be considered the sysroots (let's call the toolchain and sysroots combination SDK).  Now, since the OS iimage required build the SDK, why would then issuing "bitbake -c populate_SDK customimage" have to do any more than just packaging of the already bult components that ma11:59
*** Snert_ <Snert_!~snert_@> has quit IRC11:59
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC12:02
*** JordonWu <JordonWu!~quassel@> has quit IRC12:03
*** majuk <majuk!> has quit IRC12:03
nrossiSmitty_: because it builds another cross toolchain that runs on the SDK machine, see SDKMACHINE -> And the dependency for that is set here:
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC12:06
Smitty_But, by default the SDKMACHINE is the build host that produced the OS Image12:06
Smitty_or, is it not ?12:07
nrossiSmitty_: SDKMACHINE may be the same architecture but it is not the same as the build host. This is for a number of reasons most due to the need for a portable toolchain12:07
*** rj_ <rj_!58d39085@gateway/web/freenode/ip.> has quit IRC12:08
*** gtristan <gtristan!~tristanva@> has left #yocto12:08
Smitty_not following how that works.  How would the SDKMACHINE be the same arch. of the host, but not be the same as the build host ?12:08
*** gtristan <gtristan!~tristanva@> has joined #yocto12:08
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:c8a6:17d:5ad6:1157> has joined #yocto12:10
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto12:10
*** nighty-- <nighty--!> has joined #yocto12:10
nrossiSmitty_: think host dependencies, also consider that SDKMACHINE can be set to targets other than the host e.g. windows12:10
neverpanicSmitty_: Your host could be x86_64, your SDKMACHINE could be i386, your target could be ARM12:10
lpapphi, what is the best approach to remove a package if a new one is installed?12:10
lpappRREPLACE or something like that instead of manual rms in a postinst function?12:11
neverpanicThat's less common now that everybody has x86_64 development machines, but it used to be a thing.12:11
neverpaniclpapp: RREPLACE and RCONFLICTS maybe? Or, having the same name.12:12
lpappneverpanic: yep, the mega manual says so as well after reading RREPLACE12:12
lpapphopefully, the new package will install fine even if the "old" is no longer installed12:13
lpappi.e. opkg will not warn me about a replace/conflict if it is not there, but it removes it if it is there.12:13
neverpanicThat's the only sane way of implementing this, so I would assume that's the case.12:13
lpappI wonder whether I also need rprovides... probably not as the new one is not replacing any files from the old one?12:15
PinkSnake@rj_ save issue ? .libs ?12:15
Smitty_So, the default behavior is to build a toolchain that is different (actual different binary components) than what was used to build the components of the OS image ?12:16
*** majuk <majuk!> has joined #yocto12:17
*** majuk <majuk!> has quit IRC12:22
* kanavin has parallelized rpm generation - glibc-locale rpm making goes down to 25 seconds from over 20012:26
ChrysDkanavin : time to get a ride in italy ahahah12:27
ant_workkanavin, now the other package managers...12:27
ChrysDant_work : ahah, i guess he is so happy to have done that, and now instead of letting him happy of achieving that, you tell him that it was only the beggining ahahah12:28
ant_workfair, isn't? :)12:28
berndhshi folks, why would bitbake hang on an idle system? stuck at 99% after trying "bitbake rpi-test-image"12:29
kanavinant_work: RP is doing those :)12:29
ant_worksurely many have hopes for opkg12:30
neverpanicSmitty_: Yes, because your host toolchain may just not work in your SDK12:34
Smitty_How can that be ?12:34
*** majuk <majuk!> has joined #yocto12:35
*** gtristan <gtristan!~tristanva@> has quit IRC12:36
neverpanicSmitty_: Again, your build machine may be x86_64, the target architecture of your SDK may be i68612:36
neverpanicSo of course, your x86_64 -> arm toolchain will not work on an i686 machine12:36
ChrysDneverpanic : is that what we call canadian cross compilation?12:37
Smitty_Let's be clear.  The first step to build an OS Image is to build a toolchain.  Let's call that toolchainA.  Now toolchainA is used to build the rest of what makes up the OS Image.  When I instruct bitbake to create an SDK, it had better (by default) bundle up toolchainA and headers and libd (sysroots) for the OS Image I just built, or the default doesn't make sense12:37
neverpanicSmitty_: No, it doesn't. That assumes that your build machine architecture is the same as the architecture you want to run your SDK on12:38
neverpanicChrysD: Yes12:38
Smitty_By Default -12:38
Smitty_Why would I expect the SDK to run on somehting different ?12:38
neverpanicAnd btw, even if your host architecture equals the SDK architecture, libraries might be built with different feature sets for build machine and SDK12:39
Smitty_Right, that's the toolchain and sysroots used for building the OS Image12:39
neverpanicE.g., your SDK might contain an svn binary that supports storing passwords in system keychains, while your host svn binary used by bitbake doesn't12:39
*** majuk <majuk!> has quit IRC12:40
*** tasslehoff <tasslehoff!~Tasslehof@> has quit IRC12:42
rburtonant_work: rpm was the last one left, RP did opkg/dpkg already12:52
rburtonkanavin: *awesome* improvement12:52
ant_workgreat, thanks12:53
*** majuk <majuk!> has joined #yocto12:53
*** egavin <egavin!> has joined #yocto12:54
kanavinrburton: thanks, but I have bad(ish) news, it's racy over shared data, so that needs to be sorted12:54
rburtonSmitty_: a SDK is packaged and configured differently to the cross tooling used directly.  details, dont worry about it.12:54
kanavinrburton: glibc-locale works perfectly each time, but gettext crashes (or not)12:55
*** yann <yann!> has quit IRC12:58
*** majuk <majuk!> has quit IRC12:59
*** Snert <Snert!> has quit IRC13:05
*** Snert <Snert!> has joined #yocto13:12
*** majuk <majuk!> has joined #yocto13:15
*** sgw_ <sgw_!~sgw_@2601:1c0:6000:fe8::8b5f> has quit IRC13:17
*** majuk <majuk!> has quit IRC13:19
*** CostinC <CostinC!> has quit IRC13:20
Smitty_That's not a simple detail to ignore.  But, OK.  I'm learning to ignore almost everything13:20
*** nos__ <nos__!> has joined #yocto13:21
nos__I am working with repo manifest and I'd like to include some repos or others depending on an external variable, would that be possible to do in the manifest xml?13:22
*** madisox <madisox!> has joined #yocto13:22
nos__I do not think xml allows conditionals13:22
nos__or do you have better way to do that?13:22
*** yann <yann!> has joined #yocto13:22
neverpanicSmitty_: You're getting a toolchain that will work with your target system if you create an SDK.13:23
ChrysDnos__ : XSLT ?13:23
neverpanicI think you *can* actually ignore that it's not the exact same toolchain your host used.13:23
nos__ChrysD: sorry I am not too fond on documentation parsers, I'll look into that, thanks13:24
Smitty_I thought I was getting a toolchain that could produce binaries for my target system, but ran on the same machine that I build the target system on.13:24
ChrysDnos__ :  Have done that to school, i even don't know if it could help you but I know that i could do some kind of conditionals13:25
rburtonSmitty_: feel free to compare cross.bbclass with nativesdk.bbclass, and the relocation logic, and the various gcc/binutils recipes.  or just admit that you want to keep your sanity :)13:25
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC13:26
*** gtristan <gtristan!~tristanva@> has joined #yocto13:26
Smitty_I guess I'm not used to having to consider such things.  I've cross compiled before, of course, and built up a toolchian (like in Linux From Scratch).  But, to put together a build environment that gives such incredible versatility that it can build a OS that can run a toolchain targeting another OS is mental !13:28
ChrysDSmitty_ : and needed in certain case13:30
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto13:31
*** majuk <majuk!> has joined #yocto13:33
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto13:36
*** peacememories <peacememories!> has joined #yocto13:37
*** majuk <majuk!> has quit IRC13:37
nrossirburton: looks like the libgcrypt vs pkgconfig debacle rears its head again :(13:38
rburtoni do want to change binconfig-disabled so it destroys the scripts in the sysroot but writes the proper scripts to the packages for on-target use13:39
rburtonjust wish upstream wouldnt be so annoying about pkgconfig13:39
berndhswhat is bigbuckbunny-480p and why does bitbake tell me I need it?13:40
*** JPEWhacker <JPEWhacker!cc4da337@gateway/web/freenode/ip.> has joined #yocto13:40
rburtonberndhs: its a video file for testing and you only need it if you tried to build a recipe that ships it13:41
ChrysDberndhs : a video13:41
nrossirburton: could always just replace the scripts with scripts that just run pkgconfig under the hood... no one will notice im sure ;)13:41
rburtonthere's a recipe in meta-multimedia i believe13:41
rburtonnrossi: yeah almost done that before13:41
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto13:41
ChrysDberndhs i have it on : /meta-openembedded/meta-multimedia/recipes-multimedia/sample-content$13:42
berndhshmm so I don't really really need it, its just to verify that other stuff is working, it seems13:42
*** rcw <rcw!~rwoolley@> has joined #yocto13:46
*** MarcWe <MarcWe!> has quit IRC13:47
ChrysDberndhs : maybe with bitbake -e you could check which package RDEPENDS on it.13:48
*** nos__ <nos__!> has quit IRC13:49
*** majuk <majuk!> has joined #yocto13:51
*** majuk <majuk!> has quit IRC13:56
*** ant_work <ant_work!> has quit IRC13:57
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC13:58
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC14:01
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto14:02
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC14:04
*** majuk <majuk!> has joined #yocto14:07
lamegokhem: you around?14:08
*** Aethenelle <Aethenelle!> has joined #yocto14:08
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto14:10
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:c8a6:17d:5ad6:1157> has quit IRC14:13
*** mappy_ <mappy_!b9691ff9@gateway/web/freenode/ip.> has joined #yocto14:18
*** mappy <mappy!b9691ff9@gateway/web/freenode/ip.> has quit IRC14:18
*** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.> has quit IRC14:20
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC14:21
*** stephano <stephano!~stephano@> has quit IRC14:22
*** RP1 <RP1!> has joined #yocto14:23
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto14:25
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:addb:268a:bf70:e778> has joined #yocto14:26
*** stephano <stephano!stephano@nat/intel/x-kckfopodtkvmabhk> has joined #yocto14:26
*** AndersD <AndersD!> has quit IRC14:30
*** Bunio_FH <Bunio_FH!> has quit IRC14:30
*** peacememories <peacememories!> has quit IRC14:34
*** maxin <maxin!~maxin@> has quit IRC14:38
*** yann <yann!> has quit IRC14:39
*** Aethenelle <Aethenelle!> has quit IRC14:41
*** paulg <paulg!> has joined #yocto14:41
khemlamego: yes14:46
*** frsc <frsc!> has quit IRC14:47
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC14:48
*** aratiu <aratiu!~adi@> has quit IRC14:49
*** dreyna <dreyna!> has joined #yocto14:51
*** JPEWhacker <JPEWhacker!cc4da337@gateway/web/freenode/ip.> has quit IRC14:51
*** aratiu <aratiu!~adi@> has joined #yocto14:51
*** TobSnyder <TobSnyder!> has quit IRC14:52
*** yann <yann!> has joined #yocto14:52
*** vm_ <vm_!> has joined #yocto14:52
*** mivond <mivond!18acd356@gateway/web/freenode/ip.> has joined #yocto14:53
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC14:53
lamegokhem:  Hi. I prepared a patch for bug 8673, dealing with distutils3 packages being installed through an .egg file. As I understand, --single-version-externally-managed does handle this, but was removed some time ago. Do you know what was the reason for this?14:53
yoctiBug enhancement, Medium+, 2.4 M1, jose.a.lamego, IN PROGRESS IMPLEMENTATION , distutils3 packages installed via an egg file cannot be imported by the python3 interpreter14:53
*** aV_V <aV_V!~aV_V@> has joined #yocto14:53
lamegokhem: * removed from setuptools14:54
mivondI'm building a yocto sdk. It worked fine before, I made a bbappend to one recipe, then it wouldn't install anymore. I reverted to stock, same error.14:54
mivondSetting it cannot access '/opt/poky/2.2.1/environment-setup-*': No such file or directory14:54
*** zeddii_home <zeddii_home!> has quit IRC14:54
mivondit writes the files fine, but doesn't seem to write the env setup script14:55
mivondgoogle doesn't have many answers for this14:55
vm_hi, i cloned git:// , then i changed into poky dir and cloned git://  , then i did "source oe-init-build-env", changed into /build, set MACHINE=raspberrypi in conf/local.conf , then run "bitbake rpi-hwup-image", now it returns alot of errors? what do i wrong14:56
mivondvm_ did you edit bblayers.conf to include meta-raspberrypi?14:57
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC14:57
vm_yes, i did,  bitbake-layers add-layer ../meta-raspberrypi14:58
mivondImpossible to guess without logs14:59
vm_where is the rpi-hwup-image recipe14:59
*** zeddii_home <zeddii_home!> has joined #yocto15:00
vm_found it15:00
*** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-gpqqurojqrsjbeqg> has joined #yocto15:01
mivondanyone know about my issue installing the sdk?15:01
*** WillMiles <WillMiles!> has joined #yocto15:01
mivond Setting it cannot access '/opt/poky/2.2.1/environment-setup-*': No such file or directory15:02
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto15:02
*** gtristan <gtristan!~tristanva@> has quit IRC15:04
*** mdnneo <mdnneo!~umaucher@> has quit IRC15:04
vm_do i need to setup all vars in conf/local.conf by myself?  KERNEL_IMAGETYPE, IMAGE_FSTYPES  and so on?15:06
vm_or is there anywhere a pre-configured raspberry local.conf?15:07
mivondrpi-hwup-image should have all the preconfigured stuff to run15:07
vm_the only uses git://
vm_sorry ,wrong copy/paste15:09
vm_but it only includes core-image-minimal.bb15:09
*** jairglez <jairglez!~jairdeje@> has joined #yocto15:09
*** mappy_ <mappy_!b9691ff9@gateway/web/freenode/ip.> has quit IRC15:12
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto15:13 is the error output15:14
vm_it seemed to miss var values15:14
mivondis meta-raspberrypi on morty branch?15:16
vm_thats it, thanks alot15:18
mivondyou're welcome15:18
*** blitz00 <blitz00!~stefan@unaffiliated/blitz00> has quit IRC15:18
*** JPEWhacker <JPEWhacker!cc4da337@gateway/web/freenode/ip.> has joined #yocto15:18
*** gtristan <gtristan!~tristanva@> has joined #yocto15:19
*** hamis <hamis!~irfan@> has quit IRC15:20
*** sjolley <sjolley!~sjolley@> has quit IRC15:23
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC15:23
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto15:24
*** aV_V <aV_V!~aV_V@> has quit IRC15:25
*** JoiF <JoiF!~jofr@> has quit IRC15:25
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC15:27
*** Smitty_ <Smitty_!86bfdc4a@gateway/web/freenode/ip.> has quit IRC15:27
*** JoiF <JoiF!~jofr@> has joined #yocto15:28
*** Guest93352 <Guest93352!> has quit IRC15:32
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has quit IRC15:34
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC15:38
*** psnsilva <psnsilva!> has quit IRC15:38
*** JPEWhacker <JPEWhacker!cc4da337@gateway/web/freenode/ip.> has quit IRC15:38
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto15:39
*** psnsilva <psnsilva!> has joined #yocto15:40
*** ed2 <ed2!~Adium@> has quit IRC15:45
vm_i can look at the filenames in meta-raspberrypi/conf/machines to get a value for MACHINE , and in meta-raspberrypi/recipes-core/images/ i can see a value for bitbake  to build a image, but is there a command to get these values?  i have seen other bsp layers where these files are stored anywhere else15:46
*** Guest93352 <Guest93352!> has joined #yocto15:46
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC15:48
kergothvm_: they're two completely different things. recipes can be listed with bitbake -s, and images are just recipes like any other. or just use the layer index15:49
vm_they are different, but the two most values someone needs for building15:50
mivondkergoth: have you seen this issue with the sdk installation? For some reason it is having trouble with the env file15:50
mivond Setting it cannot access '/opt/poky/2.2.1/environment-setup-*': No such file or directory15:51
kergothvm_: what machines you have available completely depends on what layers you have enabled. same with the recipes. bitbake can't list machines, as a machine is just a config file, it has no special awareness of it. machine is a variable and a config file that bitbake.conf happens to parse, that's all from its perspective15:51
*** tavish <tavish!~tavish@unaffiliated/tavish> has joined #yocto15:51
nrossiCrofton|work: getting mailer daemons on meta-xilinx list for "", you can help sort that out maybe? :)15:54
mivondI can't install the yocto generated SDK :(15:57
*** sjolley <sjolley!~sjolley@> has joined #yocto15:57
mivondno matter what directory I use15:57
*** zeenix <zeenix!~zeenix@> has quit IRC15:57
*** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-gpqqurojqrsjbeqg> has quit IRC15:58
*** tlwoerner <tlwoerner!~Trevor@> has joined #yocto15:59
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto15:59
berndhsi need to make knee joints with available materials15:59
berndhsso the knee will carry maybe 3 kg of weight, better 516:00
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC16:00
*** Snert_ <Snert_!~snert_@> has joined #yocto16:01
*** tlwoerner <tlwoerner!~Trevor@> has joined #yocto16:01
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto16:01
*** SoniaLeon <SoniaLeon!~sleonbau@> has joined #yocto16:02
*** csanchezdll <csanchezdll!> has left #yocto16:05
*** geoffrey_l <geoffrey_l!> has quit IRC16:06
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has joined #yocto16:07
*** SoniaLeon <SoniaLeon!~sleonbau@> has quit IRC16:07
*** pohly <pohly!> has quit IRC16:11
*** zeenix <zeenix!~zeenix@> has joined #yocto16:12
*** pohly <pohly!> has joined #yocto16:12
*** michaelw1 <michaelw1!~michael@> has quit IRC16:17
*** michaelw_ <michaelw_!~michael@> has joined #yocto16:18
*** diego_r <diego_r!> has quit IRC16:18
*** t0mmy <t0mmy!~tprrt@> has quit IRC16:22
*** lexano <lexano!> has quit IRC16:24
*** peacememories <peacememories!> has joined #yocto16:26
*** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-ztzgsmowreojbjoj> has joined #yocto16:27
*** peacememories <peacememories!> has quit IRC16:28
*** toscalix <toscalix!~toscalix@> has quit IRC16:29
*** ed2 <ed2!> has joined #yocto16:33
*** lexano <lexano!> has joined #yocto16:35
*** JoiF <JoiF!~jofr@> has quit IRC16:38
*** ed2 <ed2!> has quit IRC16:39
*** fl0v01 <fl0v01!> has quit IRC16:45
lamegokhem: Any thoughts on my previous question?16:46
*** peacememories <peacememories!> has joined #yocto16:47
*** Hunk <Hunk!ce7a6654@gateway/web/freenode/ip.> has joined #yocto16:48
HunkI have a problem with my quilt-native16:48
Hunki get an error16:48
Hunk /build/tmp/sysroots/x86_64-linux/etc/ | The specified directory does not exist.16:49
Hunkbut the dir is existing16:49
*** WillMiles <WillMiles!> has quit IRC16:54
*** peacememories <peacememories!> has quit IRC16:56
*** peacemem_ <peacemem_!> has joined #yocto16:56
*** egavin <egavin!> has quit IRC17:00
Crofton|worknrossi, I'll look17:01
*** stephano <stephano!stephano@nat/intel/x-kckfopodtkvmabhk> has quit IRC17:03
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has quit IRC17:14
*** rburton <rburton!> has quit IRC17:15
*** aehs29 <aehs29!~aehernan@> has joined #yocto17:16
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has joined #yocto17:17
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has quit IRC17:31
*** manuel__ <manuel__!~manuel@> has joined #yocto17:31
*** manuel__ <manuel__!~manuel@> has joined #yocto17:32
*** zeenix <zeenix!~zeenix@> has quit IRC17:32
vm_got it, its also in the manual, ls meta*/recip*/images/*.bb  shows all available images you need to setup when running bitbake17:39
*** aehs29 <aehs29!~aehernan@> has quit IRC17:43
JaMaexit off17:47
*** JaMa <JaMa!~martin@> has quit IRC17:47
*** ketemphor <ketemphor!> has joined #yocto17:49
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:addb:268a:bf70:e778> has quit IRC17:51
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:c8a6:17d:5ad6:1157> has joined #yocto17:52
*** JPEWhacker <JPEWhacker!cc4da337@gateway/web/freenode/ip.> has joined #yocto17:57
*** martinkelly <martinkelly!> has quit IRC18:14
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC18:14
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has joined #yocto18:16
*** martinkelly <martinkelly!> has joined #yocto18:17
*** aragua__ <aragua__!> has quit IRC18:19
*** aragua__ <aragua__!> has joined #yocto18:19
*** twall <twall!~tom@> has joined #yocto18:20
*** caiortp <caiortp!~caiortp@> has joined #yocto18:21
*** manuel__ <manuel__!~manuel@> has quit IRC18:21
*** martinkelly <martinkelly!> has quit IRC18:22
*** martinkelly <martinkelly!> has joined #yocto18:23
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto18:24
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has quit IRC18:26
ketemphorhave a vendor meta example tree that I've successfully built.  I changed a single bbconfig file to add some features to a package and it broke it.  I modified again and reran bitbake iot2000-example-image and it starts back at 63% done.  Did it not do those before? My impression watching the build was that it hit 100% with 1 broken package (error popped up then a lot more building happened after before final report: attempted 369118:26
ketemphortasks of which 1647 didn't need to be rerun and 1 failed). Is there a way to test build just the modified package? (poky/meta/recipes-devtools/tcf-agent, btw)18:26
twallyou can run bitbake on single packages18:26
ketemphorthat would be recipes-devtools? or recipes-devtools/tcf-agent? or just tcf-agent?18:27
twalltcf-agent I'd say18:27
twallhello, I'm having some issues running a bitbake image, where I know that there's a recipe for gtk+ in one of my layers, however it isn't built with the image.  To enable that package, what should I modify?18:30
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC18:30
JPEWhackertwall: Did you add the package to IMAGE_INSTALL?18:35
twallI've been trying to find where that is, should that just be a line in bblayers.conf or local.conf?18:36
JPEWhackertwall: You should be able to do IMAGE_INSTALL += "<package>" in local.conf18:36
JPEWhackertwall: Oh, sorry, use IMAGE_INSTALL_append18:37
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto18:38
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has joined #yocto18:39
twallJPEWhacker: I'll give that a shot, thank you18:39
khemlamego: you add it to DISTUTILS_INSTALL_ARGS18:59
khemI removed it back then since we were moving to distutils from setuptools and distutils did not support it19:03
*** majuk <majuk!> has quit IRC19:05
*** ChrysD <ChrysD!500c2a5c@gateway/web/freenode/ip.> has joined #yocto19:12
ketemphorpkay, so build give me a .rootfs.wic, a .hddimg, a .iso, and a rootfs.ext4, all ~1GB.  I'm only using the .wic file, where do I suppress building of others?19:12
lamegokhem: got it. This helps. Thanks!19:13
ChrysDketemphor : You should change the local.conf19:14
ChrysDketemphor : You have a variable which named IMAGE_FSTYPES19:14
ketemphorcrap, didn't see it in there, maybe in referenced file?19:15
ChrysDketemphor : In your build/conf/local.conf?19:16
ketemphortemplateconf.cfg -> meta-poky/conf19:16
ketemphoryeah, not there19:16
ChrysDketemphor : did you get the software from a company?19:17
*** stephano <stephano!~stephano@> has joined #yocto19:17
ChrysDketemphor : when you said " didn't see it in there " you mean the file or the variable?19:19
ChrysDketemphor : Why not trying bitbake -e and looking for the IMAGE_FSTYPES19:20
*** manuel__ <manuel__!~manuel@> has joined #yocto19:21
*** ChrysD_ <ChrysD_!500c29c7@gateway/web/freenode/ip.> has joined #yocto19:23
ketemphordefinitely in there - need to go digging for where, 1MB text file doing bitbake -e imagename > file - set to " live wic"19:24
*** dvhart <dvhart!> has joined #yocto19:24
ketemphoroh, then live looks like it expands to iso, hddimg19:24
*** ChrysD <ChrysD!500c2a5c@gateway/web/freenode/ip.> has quit IRC19:25
*** rburton <rburton!> has joined #yocto19:25
ChrysD_ if base_contains("IMAGE_FSTYPES", "live", "live", "0", d) == "0": # live is not set but hob might set iso or hddimg > > -        d.setVar('NOISO', base_contains('IMAGE_FSTYPES', "iso", "0", "1", d)) > > -        d.setVar('NOHDD', base_contains('IMAGE_FSTYPES', "hddimg", "0", "1", d))19:26
ChrysD_ketemphor : So yeah i guess19:26
ChrysD_ketemphor : take off live and the work is done19:27
*** ChrysD_ <ChrysD_!500c29c7@gateway/web/freenode/ip.> has left #yocto19:28
*** ChrysD_ <ChrysD_!500c29c7@gateway/web/freenode/ip.> has joined #yocto19:28
ChrysD_ketemphor : Can you confirm after you tried?19:28
ketemphortrying to figure out where that's sourced from19:29
ketemphorthe -e just shows a bunch of config info, haven't been able to trace back source of those lines yet19:29
ChrysD_try with grep19:31
ChrysD_like grep --include=*.conf -rnw  -e 'IMAGE_FSTYPES'19:32
ketemphorthat's how I found them in the output, not seeing any clues as to where those configuration lines being displayed by -e are read from file19:32
*** ed2 <ed2!Adium@nat/intel/x-ppuxgplbywhcwvyl> has joined #yocto19:32
ChrysD_You go to your source directory and try what I said19:33
ChrysD_It will check for only .conf file and I suspect it being in a ".conf" but as i'm a newbine in Yocto, you will need to wait more for expert helps19:34
*** dvhart <dvhart!> has quit IRC19:34
ChrysD_pastebin after it the result19:34
*** tavish <tavish!~tavish@unaffiliated/tavish> has quit IRC19:35
ketemphorlike recursively?  haven't used grep without a pipe before...  use in source tree, not build tree19:35
ChrysD_no pipe19:35
ChrysD_just only what i said19:35
ChrysD_no need19:35
ChrysD_directly into your source directory19:35
ChrysD_grep --include=*.conf -rnw  -e 'IMAGE_FSTYPES'19:35
ChrysD_and you should also try into your build dir as it used to be19:36
ChrysD_yeah the best is to be on the top of both source and build dir :p19:36
ketemphordamn, that was fast ... alright, let me figure out pastebin real quick19:36
*** ed2 <ed2!Adium@nat/intel/x-ppuxgplbywhcwvyl> has quit IRC19:37
ketemphorbuild is going to be slow, that directory tree is huge19:38
ChrysD_yeah we should add --exclude-dir to excluse some of them like the wrk directory ahahah19:39
*** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-ztzgsmowreojbjoj> has quit IRC19:40
ketemphornothing in build19:41
ketemphor52GB build directory - never had a clue what it took to build a 1GB distro19:41
ketemphorI restarted it with --exclude-dir=tmp/work19:42
twalli've had a build directory that's exceeded 100GB before19:43
ChrysD_ketemphor : I don't know if it work but maybe considering 'IMAGE_FSTYPES*"19:43
ketemphorsame thing, it found the ones in the source directory alright, none of those look like likely candidates?19:44
ketemphornone of those say live ...19:45
*** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-dmtttgmfnrkzcvzf> has joined #yocto19:45
ketemphorah well, more of an annoyance than anything, especiall when they're duplicated in the tmp/deploy and tmp/work19:46
*** twall <twall!~tom@> has quit IRC19:46
ketemphordamn, need to run.  thanks for your help ChrysD19:47
*** ketemphor <ketemphor!> has quit IRC19:47
*** ant_home <ant_home!> has joined #yocto19:47
*** ChrysD <ChrysD!894a6839@gateway/web/freenode/ip.> has joined #yocto19:47
ChrysDtwall : Do you remove the bitbakes oytu have done before?19:47
*** ChrysD_ <ChrysD_!500c29c7@gateway/web/freenode/ip.> has quit IRC19:48
*** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-dmtttgmfnrkzcvzf> has quit IRC19:53
*** majuk <majuk!> has joined #yocto19:54
JPEWhackerDoes any one know if it would be bad form to have DISTRO_FEATURES be based on MACHINE_FEATURES? (e.g. DISTRO_FEATURES = "${@bb.utils.contians("MACHINE_FEATURES", "screen", "wayland", "", d)}"19:55
ChrysDJPEWhacker : If there is two words, it seems that somethings is conceptually different.19:56
ChrysDJPEWhacker : Stupid answer i guess19:56
ChrysDJPEWhacker : Maybe in the guide there is an explanation of the philosophy on what should be distro and machine19:57
rburtonJPEWhacker: yeah you wouldn't do that really19:57
rburtonJPEWhacker: recipes can check both machine and distro features if required19:57
JPEWhackerrbuton: Ok, thanks.19:58
ChrysDJPEWhacker : I would say that the MACHINE_FEATURES should be " machine specific "19:58
ChrysDJPEWhacker : such as package/drivers for the wifi19:58
*** vm_ <vm_!> has quit IRC19:58
ChrysDJPEWhacker : also some kind of packages for touchscreen and so on19:58
JPEWhackerYa, I guess my thinking was "if the machine has a screen ("screen" in MACHINE_FEATURES), this distro wants to use Wayland ("wayland" DISTRO_FEATURE)19:59
JPEWhackerBut if the machine doesn't have a screen, don't bother19:59
rburtonbut then you're breaking the axiom that distro features doesnt' change in a distro19:59
JPEWhackerrburton: Makes sense20:00
khemrburton: whats holding up gcc7 ?20:00
rburtonkhem: nothing now the 4.1 fix has been resubmitted20:00
rburtonkhem: got a clean branch i can throw at the ab now?20:00
*** nrossi <nrossi!uid193926@gateway/web/> has quit IRC20:03
*** manuel__ <manuel__!~manuel@> has quit IRC20:03
khemrburton: you can cherry-pick
khemits a single patch20:05
khembtw. I switched to using gcc7 on my archlinux-testing20:06
khemand it seems uninative will have issues20:06
khemit will need to consider the c++11 ABI for libstdc++ with gcc720:06
khemfor now easy fix was to stop using uninative20:07
khemI wonder if we should just cut the crap and build own gcc20:07
khemand gcc-runtime for build host20:07
rburtona gcc to build gcc?20:07
rburtoni mean, build gcc-native first20:07
khemso we can have gcc-native gcc-nativesdk gcc-cross-initial gcc-cross and gcc-crosssdk and gcc20:08
khemjust gccfy your life20:08
*** manuel__ <manuel__!~manuel@> has joined #yocto20:10
*** caiortp <caiortp!~caiortp@> has quit IRC20:11
*** RP1 <RP1!> has quit IRC20:18
rburtonhm doing a stop all builds on the new AB makes it hang (halstead, I think i broke
rburtonoh there it goes, back again20:19
halsteadrburton, It hasn't in the past. Anything special about this time?20:19
rburtonall http connections just hung for about 30 seconds20:19
rburtonworking fine now20:20
halsteadrburton, I have seen the web interface stall when stopping lots of builds.20:20
halsteadI'm not sure what the bottleneck is.20:21
halsteadIt's not load on the controller.20:21
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:c8a6:17d:5ad6:1157> has quit IRC20:23
khemrburton: ok cool20:23
*** sjolley <sjolley!~sjolley@> has quit IRC20:23
*** RP1 <RP1!> has joined #yocto20:24
*** bluelightning <bluelightning!~paul@> has joined #yocto20:24
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:24
*** sjolley <sjolley!~sjolley@> has joined #yocto20:25
*** SoniaLeon <SoniaLeon!~sleonbau@> has joined #yocto20:26
*** sjolley <sjolley!~sjolley@> has quit IRC20:30
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:5aac:892e:cbe9:f7fc> has joined #yocto20:41
*** gtristan <gtristan!~tristanva@> has quit IRC20:44
*** hbruce <hbruce!hbruce@nat/intel/x-mmvebdrlnoruzudu> has joined #yocto20:46
*** ChrysD <ChrysD!894a6839@gateway/web/freenode/ip.> has quit IRC20:46
*** rcw <rcw!~rwoolley@> has quit IRC20:46
*** rburton <rburton!> has quit IRC20:48
*** rburton <rburton!> has joined #yocto20:48
*** hbruce <hbruce!hbruce@nat/intel/x-mmvebdrlnoruzudu> has quit IRC20:50
*** hbruce <hbruce!~hbruce@> has joined #yocto20:52
*** RP1 <RP1!> has quit IRC20:55
*** JPEWhacker <JPEWhacker!cc4da337@gateway/web/freenode/ip.> has quit IRC20:58
*** sjolley <sjolley!~sjolley@> has joined #yocto21:02
*** hbruce <hbruce!~hbruce@> has quit IRC21:02
-YoctoAutoBuilder- build #1134 of nightly-non-gpl3 is complete: Failure [failed BuildImages] Build details are at
*** hbruce <hbruce!hbruce@nat/intel/x-rpiepodggcgtjzdl> has joined #yocto21:16
*** berton <berton!~berton@> has quit IRC21:17
*** morphis <morphis!> has quit IRC21:19
*** twall <twall!~tom@> has joined #yocto21:20
*** sjolley <sjolley!~sjolley@> has quit IRC21:20
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:5aac:892e:cbe9:f7fc> has quit IRC21:21
twallhello, I've been running into an issue building gtk+3 from the oe-core layer, where mesa-gl is "trying to install files into a shared area where theose files already exist."  The error messages advise clearing out build/tmp and the sstate cache, then rebuilding.  This still fails.  So is it a configuration issue in the .bb file, or maybe my machine?  The error mentions DISTRO_FEATURES could be the culprit if21:25
twallI changed that variable recently, but I've never touched it21:25
bluelightningtwall: the message is a little vague because it can't automatically determine what the cause is21:28
bluelightningtwall: which files is it complaining about?21:29
bluelightning(use pastebin if it's more than a few)21:29
*** paulg <paulg!> has quit IRC21:31
twallbluelightning: it's not super helpful, but here's the log21:32
twallit looks like it's dying while trying to install libgbm after installing libgbm-dev21:34
bluelightningwell, it kind of looks like there is a recipe called am57xx-evm-libgbm (presumably from TI) which provides libgbm and that's what it's clashing with21:34
*** King_InuYasha <King_InuYasha!~kvirc@fedora/ngompa> has quit IRC21:37
bluelightningperhaps mesa is being built incorrectly? i.e. maybe it's not supposed to be producing this library21:37
bluelightningdenix: any ideas?21:37
twallin one of the ti layers (meta-processor-sdk) there is a libgbm recipe21:39
twall*append recipe21:39
denixbluelightning: yes, we discussed it with rburton before. there's a need to decouple libgbm from mesa21:40
*** aehs29 <aehs29!~aehernan@> has joined #yocto21:40
bluelightningdenix: ok, in the mean time is there a workaround that twall can use?21:40
twallthe append has a patch to add linkable libs for Qt, yeah21:40
denixtwall: libgbm is in meta-ti21:40
twalldenix: is there a way i can decouple it from mesa while still keeping the meta-ti layer?21:43
denixbluelightning: in the meantime we avoid pulling in mesa when using sgx blob. basically mesa is replaced by sgx+libgbm. and for recipes that pull mesa directly we have bbappends to modify that dependsncy21:43
bluelightningdenix: hmm, presumably twall is hitting something that still has such an explicit dependency which isn't covered21:44
denixtwall: if you actually need to pull mesa, then no. if it's pulled accidentally, then find what causes it and see if we have a solution in meta-ti/meta-arago21:45
*** sjolley <sjolley!sjolley@nat/intel/x-haihagdahbyrgtqq> has joined #yocto21:45
twallsounds good.  I don't think I have anything that requires mesa.  Where would be a good start to finding what pulls it in?21:46
bluelightningtwall: bitbake -g will produce some graph files (which you should search with less or your favourite editor rather than a graph viewer as they are too large for most viewers)21:49
denixtwall: ^^^ yes, -g helps21:49
bluelightninggraphs showing the dependency relationships, that is21:49
denixbluelightning: mesa and mesa-gl provide own libgbm unconditionally. previous discussion was about maybe making it a PACKAGECONFIG, but I'm not that familiar with Mesa and so far didn't have time to look into it21:51
bluelightningdenix: ah ok21:51
* bluelightning is not very familiar with mesa either21:51
twallthe package dependency chart is saying that libgbm is dependent on mesa from the oe-core layer21:52
twallthen a bunch of sgx packages in the meta-ti layer are made with it21:54
twallboth libgbm and libgbm-dev are made with mesa from the oe-core layer21:55
denixtwall: meta-ti provides separate libgbm. you need to see what depends and pulls entire mesa21:56
bluelightningright, it's what depends on mesa that needs to be tracked down21:56
twallsorry if this seems rather noobish, but what would i be looking for?21:59
*** SoniaLeon <SoniaLeon!~sleonbau@> has quit IRC22:00
bluelightning-> mesa or something similar I would think22:00
*** hbruce <hbruce!hbruce@nat/intel/x-rpiepodggcgtjzdl> has quit IRC22:01
twallbluelightning: I have "libgl-mesa" -> "mesa-megadriver" [style=dotted] and "mesa-gl-staticdev" -> "mesa-gl-dev" [style=dashed]22:02
bluelightningthe second one isn't significant22:03
bluelightningso what depends on libgl-mesa?22:03
twallnothing, it would seem22:04
bluelightningreally? I wouldn't expect it'd be in the graph if that's the case...22:04
bluelightningwell, actually that's not necessarily a requirement22:04
bluelightningtwall: I'd recommend looking at rather than the other files unless you are on pyro or master22:05
*** RP1 <RP1!> has joined #yocto22:06
twallI'm on krogoth, so i'll check the task-depends22:08
*** SoniaLeon <SoniaLeon!~sleonbau@> has joined #yocto22:09
*** lamego <lamego!jose@nat/intel/x-wwnaaekkmywudbsu> has quit IRC22:11
twallbluelightning: the mesa-gl.do_packagedata task is only required by another mesa-gl task, and gtk+3.do_package22:11
bluelightningso the only mention of mesa in the gtk+3 recipe in krogoth relates to wayland22:16
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:c8a6:17d:5ad6:1157> has joined #yocto22:16
bluelightningif you don't need wayland support perhaps you should disable that if it's enabled (which I think it may be by default)22:17
rburton(by removing wayland from DISTRO_FEATURES)22:18
rburtonand on that its bed time22:18
bluelightningindeed, thanks rburton22:18
rburtonbluelightning: CCd you on a bug mail regarding selftest and recipetool, your thoughts would be appreciated22:18
bluelightningrburton: right it's on my todo for today22:19
rburtonalso if anyone wants to make their first contribution to oe-core then would be trivial and satisfying22:19
yoctiBug 11575: normal, Undecided, 2.4 M1, ross.burton, ACCEPTED , ERROR: cryptodev-tests-1.8-r0 do_checkuri: Fetcher failure for URL: ''22:19
rburtonjust thought i'd mention that on the off chance :)22:19
-YoctoAutoBuilder- build #484 of nightly-no-x11 is complete: Success [build successful] Build details are at
rburtonbluelightning: thanks.  g'night :)22:19
*** rburton <rburton!> has quit IRC22:19
twallthat's unfortunate, since I'd like to have wayland.  Mainly because I'm going to be doing quite a lot of gstreamer stuff and the light weight of wayland is nice22:19
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC22:20
twallif i wanted to keep wayland, should I move to a newer branch?22:20
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has quit IRC22:21
*** mivond <mivond!18acd356@gateway/web/freenode/ip.> has quit IRC22:22
bluelightningthat's a good question22:22
bluelightningdenix any recommendations?22:22
bluelightning(I think there's an element of this that is BSP specific)22:22
twallmakes sense22:23
*** nighty-- <nighty--!> has quit IRC22:24
*** martinkelly <martinkelly!> has quit IRC22:29
*** martinkelly <martinkelly!> has joined #yocto22:29
*** stephano <stephano!~stephano@> has quit IRC22:33
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:c8a6:17d:5ad6:1157> has quit IRC22:49
*** aehs29 <aehs29!~aehernan@> has quit IRC22:50
*** RP1 <RP1!> has quit IRC22:51
*** dv_ <dv_!~quassel@> has quit IRC22:55
*** dv_ <dv_!> has joined #yocto22:55
*** ant_home <ant_home!> has quit IRC23:02
*** twall <twall!~tom@> has quit IRC23:03
*** Guest93352 <Guest93352!> has quit IRC23:08
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto23:12
*** fischerm <fischerm!> has quit IRC23:19
*** majuk <majuk!> has quit IRC23:21
*** Snert_ <Snert_!~snert_@> has quit IRC23:22
*** Snert_ <Snert_!~snert_@> has joined #yocto23:22
*** SoniaLeon <SoniaLeon!~sleonbau@> has quit IRC23:29
*** majuk <majuk!> has joined #yocto23:33
*** majuk <majuk!> has quit IRC23:39
*** RP1 <RP1!> has joined #yocto23:43
*** jairglez <jairglez!~jairdeje@> has quit IRC23:53
*** RP1 <RP1!> has quit IRC23:57
*** agust <agust!> has quit IRC23:59

Generated by 2.11.0 by Marius Gedminas - find it at!