Monday, 2017-05-22

*** garbados <garbados!~garbados@2601:1c2:303:6b0:2547:735:6b72:ee4f> has quit IRC00:01
*** dvhart <dvhart!> has quit IRC00:02
*** dvhart <dvhart!> has joined #yocto00:02
*** dvhart <dvhart!> has quit IRC00:08
*** fischerm <fischerm!> has quit IRC00:20
*** dvhart <dvhart!> has joined #yocto00:22
*** nighty-- <nighty--!> has joined #yocto00:24
*** majuk <majuk!> has joined #yocto00:24
*** dvhart <dvhart!> has quit IRC00:26
*** dvhart <dvhart!> has joined #yocto00:27
*** majuk <majuk!> has quit IRC00:31
*** yizhao <yizhao!~zhaoyi@> has joined #yocto00:33
*** msvb-lab <msvb-lab!> has quit IRC00:37
*** majuk <majuk!> has joined #yocto01:02
*** majuk <majuk!> has quit IRC01:08
*** Jackie <Jackie!~quassel@> has joined #yocto01:10
*** Jackie is now known as Guest144701:11
*** Crofton|work <Crofton|work!> has quit IRC01:20
*** majuk <majuk!> has joined #yocto01:23
*** JordonWu <JordonWu!~quassel@> has joined #yocto01:27
*** majuk <majuk!> has quit IRC01:28
*** Crofton <Crofton!> has joined #yocto01:28
*** dreyna <dreyna!> has quit IRC01:31
*** seebs <seebs!> has quit IRC01:34
*** Crofton <Crofton!> has quit IRC01:34
*** majuk <majuk!> has joined #yocto01:41
*** seebs <seebs!> has joined #yocto01:42
*** majuk <majuk!> has quit IRC01:47
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC01:56
*** dengke <dengke!~dengke@> has joined #yocto02:00
*** robert_yang <robert_yang!~lyang1@> has joined #yocto02:15
*** majuk <majuk!> has joined #yocto02:19
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has quit IRC02:19
*** catch22_ <catch22_!> has joined #yocto02:23
*** majuk <majuk!> has quit IRC02:25
*** ojdo <ojdo!> has joined #yocto02:26
*** Guest93352 <Guest93352!> has quit IRC02:40
*** majuk <majuk!> has joined #yocto02:41
*** majuk <majuk!> has quit IRC02:45
*** berndhs <berndhs!> has quit IRC02:54
*** redengin <redengin!~redengin@2601:600:987f:e616:75a9:6d21:d094:43a5> has quit IRC02:54
*** redengin <redengin!~redengin@2601:600:987f:e616:f41b:43c3:4a4b:dbed> has joined #yocto02:56
*** majuk <majuk!> has joined #yocto02:59
*** mkelly <mkelly!~martin@> has quit IRC03:02
*** majuk <majuk!> has quit IRC03:04
*** majuk <majuk!> has joined #yocto03:17
*** pohly <pohly!> has joined #yocto03:17
*** pohly1 <pohly1!> has quit IRC03:20
*** majuk <majuk!> has quit IRC03:23
*** gabrbedd <gabrbedd!> has quit IRC03:25
*** seebs <seebs!> has quit IRC04:06
*** gtristan <gtristan!~tristanva@> has quit IRC04:07
*** seebs <seebs!> has joined #yocto04:13
*** majuk <majuk!> has joined #yocto04:13
*** dreyna <dreyna!> has joined #yocto04:14
*** majuk <majuk!> has quit IRC04:19
*** gabrbedd <gabrbedd!> has joined #yocto04:33
*** majuk <majuk!> has joined #yocto04:52
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC04:55
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto04:56
*** majuk <majuk!> has quit IRC04:57
*** majuk <majuk!> has joined #yocto05:11
*** majuk <majuk!> has quit IRC05:16
*** majuk <majuk!> has joined #yocto05:31
*** majuk <majuk!> has quit IRC05:36
*** MarcWe <MarcWe!~hmw@> has joined #yocto05:38
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC05:39
*** agust <agust!> has joined #yocto05:43
*** majuk <majuk!> has joined #yocto05:49
*** qt-x <qt-x!~Thunderbi@> has joined #yocto05:50
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto05:54
*** majuk <majuk!> has quit IRC05:55
*** AndersD <AndersD!~anders@> has joined #yocto05:56
*** morphis <morphis!> has joined #yocto05:57
*** paulg <paulg!> has quit IRC06:03
*** majuk <majuk!> has joined #yocto06:11
*** majuk <majuk!> has quit IRC06:15
*** hamis <hamis!~irfan@> has joined #yocto06:24
*** arkver <arkver!~arkver@> has joined #yocto06:29
*** majuk <majuk!> has joined #yocto06:29
*** frsc <frsc!~frsc@> has joined #yocto06:31
*** arkver <arkver!~arkver@> has quit IRC06:35
*** rj_ <rj_!58d39085@gateway/web/freenode/ip.> has joined #yocto06:36
*** majuk <majuk!> has quit IRC06:36
*** tasslehoff <tasslehoff!~Tasslehof@> has joined #yocto06:36
*** mdnneo <mdnneo!~umaucher@> has joined #yocto06:37
*** eduardas_m <eduardas_m!~eduardas@> has joined #yocto06:39
*** mckoan|away is now known as mckoan06:50
mckoangood morning06:50
*** JaMa <JaMa!~martin@> has joined #yocto06:51
*** majuk <majuk!> has joined #yocto06:51
*** majuk <majuk!> has quit IRC06:55
*** AndersD <AndersD!~anders@> has quit IRC06:57
*** Bunio_FH <Bunio_FH!> has joined #yocto06:57
*** RP1 <RP1!> has joined #yocto06:59
*** Smitty_ <Smitty_!86bfdc49@gateway/web/freenode/ip.> has joined #yocto07:04
Smitty_I can hear the groans  !07:04
*** Bunio_FH <Bunio_FH!> has left #yocto07:05
*** yohboy <yohboy!> has joined #yocto07:08
*** ed2 <ed2!~Adium@> has joined #yocto07:08
*** jku <jku!~jku@> has joined #yocto07:08
*** majuk <majuk!> has joined #yocto07:09
*** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.> has joined #yocto07:10
*** majuk <majuk!> has quit IRC07:14
*** toscalix <toscalix!~toscalix@> has joined #yocto07:20
*** lucaceresoli <lucaceresoli!> has joined #yocto07:23
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:24
*** majuk <majuk!> has joined #yocto07:27
*** AndersD <AndersD!> has joined #yocto07:31
*** majuk <majuk!> has quit IRC07:32
Smitty_It seems like any file, whether it be a .conf, .bb, .bbclass, etc, can be used for just about anything.  The naming convention is a hint for how they are used.07:35
*** Bunio_FH <Bunio_FH!> has joined #yocto07:39
*** t0mmy <t0mmy!~tprrt@> has joined #yocto07:44
*** majuk <majuk!> has joined #yocto07:45
*** CostinC <CostinC!> has joined #yocto07:46
*** mappy <mappy!b9691ff9@gateway/web/freenode/ip.> has joined #yocto07:47
CostinCmorning all07:47
*** lemagoup <lemagoup!~lemagoup@> has joined #yocto07:48
*** yann <yann!> has quit IRC07:51
*** majuk <majuk!> has quit IRC07:52
Smitty_Reading through oe-buildenv-internal, I am a bit confused about the three python version checks:   Why 3, why not just a single check for version 3.4.0 or greater, since that's what bitbake apparently requires ?07:54
*** JoiF <JoiF!~jofr@> has joined #yocto07:54
nrossiSmitty_: oe needs both python 2.7.3 and python 3.4.0. And 'python' must be python 2, on some distros (e.g. Arch Linux) it is not.07:57
nrossiSmitty_: thus why the three checks need to be made07:57
Smitty_So, the requirement for python 2.7.3 is not from bitbake, rather from existing (python) scripts within oe-core (and dependent projects) ?  And those scripts don't behave correctly with python 3 ?07:59
*** gtristan <gtristan!~tristanva@> has joined #yocto08:01
jkupython and python3 might be related but they are different languages...08:02
Smitty_Another totally unrelated question.  I read that nfs mounted file systems can't be used for build directories.  Why would such a restriction exist ?  Why would a user app care what file system was in use ?08:03
*** deva <deva!~deva@> has joined #yocto08:05
jkuSmitty_: TMPDIR can't be on NFS I think (can't remember details but symlink behaviour differences maybe?)08:07
*** majuk <majuk!> has joined #yocto08:07
jkubut you also wouldn't want that: TMPDIR should be on the fastest disk you have08:08
jkubut SSTATE_DIR and DL_DIR should be fine (and those are the ones that might make sense to put on network disks IMO)08:10
*** gtristan <gtristan!~tristanva@> has quit IRC08:10
Smitty_symlinks apparently are problematic across mountpoints - I didn't realize that.  I thought that restriction was for hardlinks.08:11
*** blitz00 <blitz00!~stefan@unaffiliated/blitz00> has joined #yocto08:11
*** majuk <majuk!> has quit IRC08:12
ChrysDGood morning =D08:12
*** rajm <rajm!~robertmar@> has joined #yocto08:15
*** gtristan <gtristan!~tristanva@> has joined #yocto08:15
*** geoffrey_l <geoffrey_l!> has joined #yocto08:16
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC08:20
*** MarcWe <MarcWe!~hmw@> has quit IRC08:20
*** MarcWe <MarcWe!> has joined #yocto08:21
*** majuk <majuk!> has joined #yocto08:27
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has joined #yocto08:30
Smitty_The symlink issue makes sense.  Since a symlink can contain a path (absolute or relative ) to a location in the destination file system that doesn't exist in the clients "view" of that filesystem.  Never thought about why, I always simply said, "OK".08:32
*** majuk <majuk!> has quit IRC08:32
Smitty_So, back to oe-init-build-env.  It seems my initial understanding of the purpose of this (along with oe-buildenv-internal, and oe-setup-builddir) was wrong.  rburton - and others - told me that sourcing this file was essentially optional.  At first I didn't understand how that could be.  After all, every example uses it, and besides it processes bblayers.conf.sample, and creates build dir.08:35
*** zeenix <zeenix!~zeenix@> has joined #yocto08:40
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC08:40
Smitty_What really should happen is that the oe-init scripts be setting up the environment to point to a totally correct bblayers.conf located inside source dir  not move it into builddir.  bitbake should just use what it finds in source dir08:44
*** majuk <majuk!> has joined #yocto08:46
*** yann <yann!> has joined #yocto08:47
*** pagios is now known as PAGIO08:48
*** PAGIO <PAGIO!pagios@gateway/shell/panicbnc/x-ubbpjphvdksemaqh> has left #yocto08:48
jkuSmitty_: and what source dir should that "totally correct" bblayers.conf come from?08:49
jku E.g. my current build has the poky layers and meta-intel in BBLAYERS -- what source repo could have known I want those but not meta-oe which is also cloned.08:49
*** majuk <majuk!> has quit IRC08:50
Smitty_I guess what I am saying, is that since bblayers.conf really only sets BBPATH (which I find a bit strange), BBFILES and BBLAYERS.  The latter really control what is getting built.08:57
rj_Morning, Could someone help me out with MariaDB? I installed it from the yocto recipe(meta-oe layer) but when i want to run it it says it can't find mysqld_safe_helper. Besides that when i run 'mysql' it says it can't connect to the local MySQL server socket "/var/lib/mysql/mysql.sock"08:59
MarcWehi, Im having issus with building im getting: /usr/src/debug/gdb/7.10.1-r0/gdb-7.10.1/gdb/completer.c:1615: undefined reference to `_rl_completion_prefix_display_length'08:59
PinkSnake@all quick and dirty -> add to you setup-environment file to list all image recipes :
*** Guest93352 <Guest93352!> has joined #yocto09:00
*** aV_V <aV_V!~aV_V@> has joined #yocto09:02
Smitty_PinkSnake:  how does that differ from the output of bitbake-layers show-recipes "*-image-*"09:02
*** TuTizz <TuTizz!~TuTizz@> has joined #yocto09:03
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto09:03
jkuMarcWe: on an old poky?09:03
ChrysDSmitty_ : it differ that the script is made for developper engineer09:03
MarcWeyes krogoth09:03
ChrysDSmitty_ : For example you will launch this script, it will source the oe init build dir and also give to the client the list of images.09:04
MarcWejku: yes on krogoth09:04
*** majuk <majuk!> has joined #yocto09:04
ChrysDSmitty_ : For client OR developper engineer09:04
Smitty_That's what "bitbake-layers show-recipes "*-image-*"" does09:05
PinkSnake@Smitty @ChrysD +1 and script is faster than your cmd and doesn't use bitbake tools ;)09:06
Smitty_OK, so when you don't rely upon bitbake, how do you know the image is really available ?09:06
jkuMarcWe: I'm not familiar with this but see poky commit 07c4bc109d51 -- maybe you can remove "readline" from PACKAGECONFIG to make it work?09:06
ChrysDSmitty_ : it's not that09:06
ChrysDSmitty_ : You can't ask for your client or dev team to know bitbake09:07
Smitty_Becasue unless bitbake sees it as an image, it's not an image09:07
PinkSnake@Smitty and i don't care about poky and oe images09:07
ChrysDSmitty_ : In my case, i use a script which I simply launch, and give me the all command to launch so that I don't need to care of bitbake or yocto09:07
PinkSnake@Smitty it's my job to keep repos clean so i know exactly which images are really available :P09:08
ChrysDSmitty_ : So that for example, the marketing/commercial team can even do them itself.09:08
ChrysDSmitty_ : Sometimes we need to do some kinds of scripts to simplify tasks for people that are not platform engineer/developper09:10
*** majuk <majuk!> has quit IRC09:10
MarcWe jku: cant finde the commit.09:12
*** dreyna <dreyna!> has quit IRC09:14
pohlyed2: is it part of your plans for wic to get replace the wic-tools->grub-efi+syslinux dependency?09:15
pohlyNot all images built with wic need those, so a better place would be in the per-image dependencies.09:15
ed2pohly: The problem here is how to build images depending on syslinux manually with wic.09:16
ed2pohly: i still don't have good solution for this09:17
pohlyed2: perhaps "wic-tools" should be reserved for this "use wic manually" case and automatic building via bitbake should use something else ("wic-tools-light") or no wic-tools at all?09:17
pohlyThen "manual mode" uses wic as a generic tool that works for multiple images (at the expense of having to build things with might not be needed), while building through bitbake can be as efficient as possible for the desired images.09:19
ed2this makes sense. it would require to build wic-tools manually, but anyway it's better than building unneeded recipes.09:19
ed2pohly: I'll try to remove wic-tools from deps. having a bug for that would speed this up, btw :)09:21
pohlyed2: I wanted to check first whether you already have one ;-) I'll file one.09:22
ed2all: does anyone see this build error in master-next for beaglebone machine?
*** Bunio_FH <Bunio_FH!> has quit IRC09:24
*** Bunio_FH <Bunio_FH!> has joined #yocto09:24
ed2all: I've just seen it on qemux86-64 machine too. hmmm.09:26
*** _AndersD <_AndersD!> has joined #yocto09:35
MarcWejku: ty09:36
*** AndersD <AndersD!> has quit IRC09:36
*** majuk <majuk!> has joined #yocto09:42
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto09:44
*** nighty-- <nighty--!> has quit IRC09:44
*** pranay <pranay!736e4506@gateway/web/freenode/ip.> has joined #yocto09:44
Smitty_It seems my PATH is being manipulated to be incorrect - by the build, not by me:
binarymSmitty_: bitbake doesn't support to be called by relative path09:48
binarymyou must09:48
binarym1/ . oe-init-buildenv <--- this command gonna:09:48
binarym   a/ setup your PATH to point to bitbake binaries directory etc...09:48
*** majuk <majuk!> has quit IRC09:48
binarym   b/ move your shell to your build/ sub-directory09:48
binarym2/ launch your build by using bitbake <your image>09:49
*** berndhs <berndhs!> has joined #yocto09:49
binarymSmitty_: Yocto and bitbake are massively based on shell scripts09:49
binarymand, as you probably know, shell scripts isn't the more powerfull language09:50
binarymthat kind of "limitations" aren't SO unbelievable :)09:50
*** csanchezdll <csanchezdll!> has joined #yocto09:53
*** Bunio_FH <Bunio_FH!> has quit IRC09:55
*** toanju <toanju!~toanju@> has joined #yocto09:56
*** JordonWu <JordonWu!~quassel@> has quit IRC10:03
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto10:06
*** Bunio_FH <Bunio_FH!> has joined #yocto10:12
*** majuk <majuk!> has joined #yocto10:20
*** nighty-- <nighty--!> has joined #yocto10:20
*** majuk <majuk!> has quit IRC10:26
*** deva <deva!~deva@> has quit IRC10:27
*** Bunio_FH <Bunio_FH!> has quit IRC10:30
*** Bunio_FH <Bunio_FH!> has joined #yocto10:30
*** aV_V <aV_V!~aV_V@> has quit IRC10:40
*** catch22 <catch22!~catch22__@> has quit IRC10:43
*** msvb-lab <msvb-lab!> has joined #yocto10:54
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has quit IRC10:57
*** majuk <majuk!> has joined #yocto10:59
*** Saur <Saur!> has quit IRC10:59
*** Saur <Saur!> has joined #yocto11:00
*** majuk <majuk!> has quit IRC11:05
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC11:06
*** Crofton|work <Crofton|work!> has joined #yocto11:08
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto11:16
-YoctoAutoBuilder- build #483 of nightly-no-x11 is complete: Failure [failed Running Sanity Tests] Build details are at
Smitty_error: cannot run git-proxy: No such file or directory    I have git-proxy script in my PATH after sourcing oe-init   Why this error ?11:31
*** zeeblex <zeeblex!> has left #yocto11:35
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC11:35
*** zeenix <zeenix!~zeenix@> has quit IRC11:36
*** majuk <majuk!> has joined #yocto11:37
PinkSnake@Smitty  git:// to https:// ?11:38
*** yohboy <yohboy!> has quit IRC11:43
*** qt-x <qt-x!~Thunderbi@> has quit IRC11:44
*** majuk <majuk!> has quit IRC11:44
*** berton <berton!~berton@> has joined #yocto11:49
*** zeenix <zeenix!~zeenix@> has joined #yocto11:50
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto11:58
Smitty_I was able to get around the problem with git, by changing the SRC_URI to use https instead of git.  Now I get this instead:  ERROR: mobile-broadband-provider-info-1_20170310-r0 do_populate_lic: QA Issue: mobile-broadband-provider-info: LIC_FILES_CHKSUM points to an invalid file: /local/smitty/custom_distro/build/tmp-glibc/work/i586-oe-linux/mobile-broadband-provider-info/1_20170310-r0/git/COPYING [license-checksum]11:59
neverpanicWell, now the source code seems to have changed, so the change was either not transparent, or the recipe does not specify a specific git hash to use and the COPYING file was updated.12:01
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC12:03
*** top22 <top22!c34b4920@gateway/web/freenode/ip.> has quit IRC12:05
Smitty_Ah, so, if I do a "git pull" ,  then after some time the source changes, then I attempt a build, bitbake fetches the source, but, now the hash is different that what my meta-data says it is, so bitbake errors ??   Is that what's happening ?12:12
*** toanju <toanju!~toanju@> has quit IRC12:20
*** toanju <toanju!~toanju@> has joined #yocto12:20
*** pranay <pranay!736e4506@gateway/web/freenode/ip.> has quit IRC12:21
*** aratiu <aratiu!~adi@> has quit IRC12:25
*** rovanceo_ <rovanceo_!~rovanceo@> has quit IRC12:25
Smitty_So, performing a git pull within my top level project directory appears to have updated whatever the problem was.  BUT, now I get this:  DEBUG: Executing shell function do_compile NOTE: make -j 56 ERROR: oe_runmake failed make: *** No targets specified and no makefile found.  Stop12:25
Smitty_for that same project12:26
ChrysDSmitty_ : Have you checked that you have everything now in your git repo?12:29
ChrysDSmitty_ : look to your do_compile12:29
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto12:35
*** aratiu <aratiu!~adi@> has joined #yocto12:45
*** rovanceo <rovanceo!~rovanceo@> has joined #yocto12:45
*** aratiu <aratiu!~adi@> has quit IRC12:49
*** rovanceo <rovanceo!~rovanceo@> has quit IRC12:49
*** peacememories <peacememories!> has joined #yocto12:50
*** baldgeek <baldgeek!> has joined #yocto12:51
*** zeenix <zeenix!~zeenix@> has quit IRC12:53
Smitty_Thinking that the problem may be an out of date meta-data I cd'd into my project top level meta data directory, ran git reset --hard HEAD12:54
*** rovanceo <rovanceo!~rovanceo@> has joined #yocto12:54
Smitty_then ran git pull ----recurse-submodules=yes12:54
Smitty_then cd'd into my build directory12:55
Smitty_run bitbake, then get the original error:    ERROR: mobile-broadband-provider-info-1_20170310-r0 do_fetch: Fetcher failure for URL: 'git://'. Unable to fetch URL from any source.12:55
*** JPEWhacker <JPEWhacker!cc4da371@gateway/web/freenode/ip.> has joined #yocto12:56
*** majuk <majuk!> has joined #yocto12:56
*** Jetty <Jetty!b91c11ae@gateway/web/freenode/ip.> has joined #yocto12:56
*** tasslehoff <tasslehoff!~Tasslehof@> has quit IRC12:56
*** Jetty is now known as person_from_web12:57
Smitty_Since many, many other subcomponents (.bb files) also contain git:// in their fetch url, this must be an error in that particular module12:57
*** aratiu <aratiu!~adi@> has joined #yocto12:57
neverpanicSmitty_: I think your fetch was never successful, despite your sed -E 's#git://#https://#g'12:58
neverpanicSmitty_: At least that would explain the hash mismatch in COPYING (e.g. when the file isn't there at all), and your compile failure (no Makefile, no targets, make errors)12:59
Smitty_actually, it seems that within oe-core only two modules use git://   recipes-connectivity/mobile-broadband-provider-info recipes-graphics/cantarell-fonts13:00
*** majuk <majuk!> has quit IRC13:00
Smitty_OK, so how do I force a correct update ?13:00
Smitty_I mean of my meta13:00
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:03
neverpanicWhat do you want to do? Set the state of your working copy of the meta layer containing recipes to the upstream state, or re-run the fetch phase for the recipes that failed?13:05
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto13:07
Smitty_I guess I want to make sure that my meta is up to date, then re-run the build.  I hope that would update any referenced URLS13:07
*** zeenix <zeenix!~zeenix@> has joined #yocto13:09
Smitty_Not only "up to date" but pristine.  So, I just moved my originally checked-out met to a new directory, then ran git pull on the project then attempt to run "bitbake customdistro" and still the same issue13:09
Smitty_so, maybe I need to force bitbake to do a fresh pull on that module ?13:10
Smitty_how is that accomplished13:10
Smitty_I expect that to happen automagically13:10
person_from_webHi, looking for hint... I'm building SDK package for some 2.1 based yocto tree software set. Here I got some success. However I need to include the rootfs image (as archive file) into SDK...13:11
*** supermark is now known as sandsmark13:11
*** fl0v0 <fl0v0!> has joined #yocto13:11
Smitty_person_from_web:  I may be a beginner here, but what you're asking for sounds like a very strange request.  Why would you ship the rootfs image within the SDK image ?  Why can't they be two files, if needed in a super-archive13:12
person_from_web100% - aggree :)13:13
*** lamego <lamego!~jose@> has joined #yocto13:13
neverpanicSmitty_: git clone git:// works fine for me, so sounds like the problem is with your network?13:13
*** jku <jku!~jku@> has left #yocto13:13
*** majuk <majuk!> has joined #yocto13:14
Smitty_Ahh, yes, I didn't consider that, I'm actually back to the original issue of not having a correctly configured git proxy13:14
neverpanicSmitty_: Alternatively, you can change the SRC_URI to git://;protocol=https13:14
Smitty_I'd rather configure my git proxy to work correctly, to avoid further errors13:15
Smitty_of the same form13:15
person_from_webHowever, it is rather about "end-developers" control... You know, if you giving them more than one image, they immediately will mess up everything... And in my situation consistency of the image and sdk is quite important13:16
person_from_webSo I'm looking for a possible way, how to bundle the image togather with SDK.... The only thing comed to my mind is to use shell script for finding actual archive in particular directory :)13:18
ChrysDperson_from_web : When you say the rootfs image, you really speak about the "image file " or you would like having the complete tree as it shuold be in the board?13:18
person_from_webthe last one13:19
ChrysDperson_from_web : When you do bitbake -c populate_sdk <image>13:20
ChrysDperson_from_web : you shuold have a script that will install you the sysroot where you want and so that the SDK no?13:20
*** majuk <majuk!> has quit IRC13:20
person_from_webChrysD: I have the toolchain definition, which is resulting the SDK bundle...13:24
person_from_webAnd as far as I understand "-c populate_sdk <image>" should create another SDK image for me... right ?13:25
ChrysDIt shuold create the sysroots13:25
ChrysDAnd also the sdk for your computer13:25
ChrysD+ one file(a scriptà  for setting the environmental values needed in case13:26
person_from_webPinkSnake: tnx... reading...13:27
rj_Any chance someone would know why stdlib.h is not found?13:27
rj_This is the error i get:
Smitty_Oh My God !!!    changing my .gitconfig to set gitProxy from ~/bin/git-proxy to /home/smitty/bin/git-proxy solved the issue.     I haven't worked with such primitive tools since the 90s13:28
*** dfaught <dfaught!> has joined #yocto13:30
person_from_webOkay... so yeah, I see the point of the advices I got, and this is actually what I already did and I already have :)13:35
person_from_webI have a sysroots/crosscompilers etc, I can compile the software for target platfrom and it works perfectly fine13:35
*** majuk <majuk!> has joined #yocto13:36
person_from_webThe problem I'm trying to solve is the partial image delivery to the developer through the SDK13:36
ChrysDperson_from_web : what you mean?13:36
*** madisox <madisox!> has joined #yocto13:37
neverpanicrj_: Missing dependency, maybe? Do you have a link to the recipe?13:38
person_from_webso the developer will glue up "rootfs-image-from-sdk" and "his-own-file-system-image"(probably some ext4 partition) and flash it to the target device13:38
*** majuk <majuk!> has quit IRC13:41
PinkSnake@person_from_web "partial image delivery" what do you mean ?13:41
person_from_webI'll provide ext4 image, the developer will "mount it", will put some files on it and flash to target device13:42
ChrysDperson_from_web : He could flash directlry the target device13:42
ChrysDperson_from_web : and with scp, he can copy so that he can test13:43
person_from_webno... there is no such possibility13:43
person_from_webno connectivity at all13:43
ChrysDperson_from_web : How do you flash?13:43
ChrysDperson_from_web : sdcard slot?13:43
person_from_weblike that13:43
*** cryptix <cryptix!cryptixtel@gateway/shell/> has left #yocto13:44
*** gtristan <gtristan!~tristanva@> has quit IRC13:48
*** willdye <willdye!> has joined #yocto13:52
*** majuk <majuk!> has joined #yocto13:54
rj_neverpanic: It's a costum recipe,
*** peacememories <peacememories!> has quit IRC13:56
*** majuk_ <majuk_!> has joined #yocto13:57
*** majuk <majuk!> has quit IRC13:58
*** peacememories <peacememories!> has joined #yocto13:58
neverpanicrj_: Yeah, looks like a missing dependency. stdio.h is part of libc, but kernel modules don't depend on libc. IIRC there's some libc-initial-something or kernel-libc-headers package that provides these for use in kernel modules, but I don't have the details.14:02
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC14:02
rj_neverpanic: but this is about stdlib.h not stdio.h right..?14:03
*** majuk_ <majuk_!> has quit IRC14:04
neverpanicYes, sorry, typo.14:07
rj_neverpanic: Ah okay, well i just added "linux-libc-headers" to the image14:07
rj_neverpanic: so let's hope for the best14:07
neverpanicTo the image, or the recipe?14:07
*** gtristan <gtristan!~tristanva@> has joined #yocto14:10
person_from_webtry to search your /home/user/poky/build/tmp/sysroots/genericx86-64 for that header in standard locations like ./usr/include14:10
person_from_webProbably you really miss it :)14:10
rj_neverpanic: well, as dependency to the recipe14:18
*** joshuagl <joshuagl!~joshuagl@> has quit IRC14:23
*** CostinC <CostinC!> has quit IRC14:27
*** RP1 <RP1!> has quit IRC14:27
*** hamis <hamis!~irfan@> has quit IRC14:28
*** Artox <Artox!~Artox@2a01:8740:1:ff05::1> has quit IRC14:31
rj_neverpanic: It didn't work sadly14:32
*** maciejjo <maciejjo!> has quit IRC14:32
neverpanicDid you check whether your sysroot has the file?14:33
rj_neverpanic: yea, it does14:34
*** maciejjo <maciejjo!> has joined #yocto14:35
*** yann <yann!> has quit IRC14:37
*** peacememories <peacememories!> has quit IRC14:38
*** rj_ <rj_!58d39085@gateway/web/freenode/ip.> has quit IRC14:38
*** stephano <stephano!~stephano@> has quit IRC14:46
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC14:46
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto14:47
Smitty_Ruminating over the purpose of BB_ENV_EXTRAWHITE.  Is this variable somehow informing bitbake which environment variable it is allowed to look at ?14:47
*** ChrysD <ChrysD!d9804861@gateway/web/freenode/ip.> has quit IRC14:49
*** mappy <mappy!b9691ff9@gateway/web/freenode/ip.> has quit IRC14:49
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC14:51
*** yann <yann!> has joined #yocto14:55
lsandovSmitty_: list of env variables that you can use inside bitbake14:56
*** sgw_ <sgw_!~sgw_@> has quit IRC14:56
lsandovSmitty_: basically you can extract those values with d.getVar14:56
Smitty_COnfused about why/how a file named somehow automatically references a directory parallel to it named example-0.1   why the difference between underscore and hyphen  ?14:57
lsandovSmitty_: the underscore separates the package name and the package version14:58
Smitty_and the hyphen ?14:58
Smitty_Also does that14:58
*** sjolley <sjolley!~sjolley@> has quit IRC15:00
Smitty_What I am getting at is that somehow the build system looks at the name of the file, and magically knows that do_compile, SRC_URI (and probably others) are actually referring to files within a directory named "example-0.1"    So, why change from an underscore to a hyphen ?15:00
lsandovSmitty_: the hypen and part of the PN15:00
lsandovso example-0.1 is the package name15:00
lsandovexample_0.1, just example is the package name15:01
*** sjolley <sjolley!sjolley@nat/intel/x-ywcddviynbplduds> has joined #yocto15:01
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto15:01
lpapphi, any plans for openssl 1.1.0?15:01
*** sjolley <sjolley!sjolley@nat/intel/x-ywcddviynbplduds> has quit IRC15:02
*** _AndersD <_AndersD!> has quit IRC15:03
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto15:03
*** paulg <paulg!> has joined #yocto15:04
*** Bunio_FH <Bunio_FH!> has quit IRC15:04
lsandov Smitty_: pastebin your recipe15:05
lsandovSmitty_: so we can have more context15:05
lsandovSmitty_: oh. that is the hello world created with yocto-layer, right?15:06
Smitty_This is in a file named meta-custom/recipes-example/example/example-0.1/    EVen the path to the file is consistent, but the bb file name doesn't match15:06
*** ketemphor <ketemphor!> has joined #yocto15:07
lsandovSmitty_:  I see what you mean15:08
Smitty_Is that standard ?  to have such an inconsistency  for the bb file name15:09
*** jairglez <jairglez!~jairdeje@> has joined #yocto15:09
Smitty_I mean, is that intentional, or works by accident ?15:09
lsandovSmitty_: it is intentional and the standard15:10
*** aratiu <aratiu!~adi@> has quit IRC15:11
lsandovso you have a recipe name then you can place your patches or any file inside: foo or foo-X.Y or files15:11
Smitty_So, the build environment is looking for a file named ""   in a directory named "recipes-package", and also expect parallel source in a subdirectory named "package-version"  but for some reason the bb file contains an underscore in the naame, and no other element of this package does15:12
*** scottrif <scottrif!~scottrif@> has joined #yocto15:13
*** scottrif <scottrif!~scottrif@> has left #yocto15:13
*** frsc <frsc!~frsc@> has quit IRC15:13
lsandovSmitty_: recipes have standalone folders so no parallel recipes/sources is expected15:14
lsandovSmitty_: you can modify recipes in another layers, but this is not what you mean I believe15:15
*** RP1 <RP1!~richard@> has joined #yocto15:15
*** aratiu <aratiu!~adi@> has joined #yocto15:16
*** vm_ <vm_!> has joined #yocto15:18
vm_hi, when i build with toaster, where are the "Bitbake Variables" stored ?15:19
-YoctoAutoBuilder- build #1120 of nightly-qa-extras is complete: Failure [failed BuildImages_3] Build details are at (the pastebin)  SRC_URI variable and the do_compile() both reference helloworld.c without explicitly naming the directory example-0.1     That directory is parallel to  file.  So, there must be some weird implicit rule that allows bitbake to know to look there15:19
Smitty_And it's the strange inconsistency between underscore and hyphen that I find confusing15:20
*** eduardas_m <eduardas_m!~eduardas@> has quit IRC15:22
*** SoniaLeon <SoniaLeon!~sleonbau@> has joined #yocto15:23
lsandovSmitty_: there are some variables to understand all this15:24
lsandovcheck WORKDIR, S and B definitions15:24
lsandovWORKDIR is the parent folder of the recipe inside TMPDIR, S is where the source code is located and B the build folder15:25
lsandovSmitty_: you can use bitbake -e hello-world | grep ^<name of the variable> to check its value15:25
*** Guest93352 <Guest93352!> has quit IRC15:26
lsandovSmitty_: and yes, the hyphen/underscore is a bit confusing15:26
*** stephano <stephano!~stephano@> has joined #yocto15:28
*** toanju <toanju!~toanju@> has quit IRC15:31
*** psnsilva <psnsilva!> has joined #yocto15:32
*** sjolley <sjolley!~sjolley@> has joined #yocto15:34
*** zeenix <zeenix!~zeenix@> has quit IRC15:36
*** rajm <rajm!~robertmar@> has quit IRC15:39
*** ed2 <ed2!~Adium@> has quit IRC15:42
*** black_13 <black_13!48b62bb7@gateway/web/freenode/ip.> has joined #yocto15:45
*** fl0v0 <fl0v0!> has quit IRC15:46
*** Pharaoh_Atem <Pharaoh_Atem!~neal@fedora/ngompa> has quit IRC15:46
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC15:47
*** toscalix <toscalix!~toscalix@> has quit IRC15:47
*** mkelly <mkelly!> has joined #yocto15:47
black_13how do i set my permissions so that can yocto can run on a vagrant user15:47
black_13how do I set my permissions so that the yocto scripts can run with a vagrant user15:49
*** p0kerface|work <p0kerface|work!~bg14ina@kde/bgupta> has joined #yocto15:51
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto15:52
*** peacememories <peacememories!> has joined #yocto15:52
lsandovblack_13: what do you mean? you want to launch a VM and inside run yocto?15:53
black_13i figured it out15:53
black_13i had to dust off the linux/unix grey matter notes15:53
*** SoniaLeon <SoniaLeon!~sleonbau@> has quit IRC15:54
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has quit IRC15:54
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto15:55
*** ntl <ntl!> has quit IRC15:56
*** p0kerface|work <p0kerface|work!~bg14ina@kde/bgupta> has quit IRC15:57
ketemphorI have a prebaked image from device manufacturer and I'd like to modify one of the packages without figuring out the entire dev chain for baking my own image.  I need to modify tcf-agent with some different build flags.  It's available in vendor's opkg servers, but I don't know how to reconfigure it from that level. Is that feasible?15:58
*** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-usocmgqhfcryucmv> has joined #yocto16:00
kergothyou can't use an ipk feed to rebuild a package from source. it's not debian, no source packages are provided16:02
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto16:02
ketemphorI would try to rebuild from scratch using the git repo, but I'm stuck at the hardware layer.  Git repo has i686 and i386 in its machine subdirectory, but my hardware identifies as i586 (intel quark)16:03
ketemphorthanks kergoth, still trying to get my head around some of these concepts16:04
kergothno idea  what you're referring to there, but you can target any architecture16:04
*** mkelly <mkelly!> has quit IRC16:05
*** fischerm <fischerm!> has joined #yocto16:06
*** black_13 <black_13!48b62bb7@gateway/web/freenode/ip.> has quit IRC16:07
ketemphor I really should try it, sorry, I just read the makefile first and it tries to query the local uname -m and defines a variable that picks out particular include and .c files based on cpu architecture16:07
ketemphorjust my arch doesn't have a subdir so I assumed it wouldn't work16:08
*** Snert__ <Snert__!~snert_@> has joined #yocto16:10
*** lexano <lexano!> has joined #yocto16:11
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC16:12
*** t0mmy <t0mmy!~tprrt@> has quit IRC16:14
kergoththe recipe no doubt addresses all of that already16:15
*** Pharaoh_Atem <Pharaoh_Atem!~neal@fedora/ngompa> has joined #yocto16:15
kergothwhich is why oe exists, so its recipes can deal with the crosscompilation madness so you don't have to16:16
*** lucaceresoli <lucaceresoli!> has quit IRC16:17
ketemphoryeah, i have the recipe mod I think I need: , but I don't know if I have access to the original recipes that this vendor used to construct this image...  it's not buried in the image somewhere, is it?16:19
yoctiBug 5069: enhancement, Medium, Future, david.reyna, NEW , Eclipse TCF can support arm cpu debug now,but can't do it this time.16:19
*** geoffrey_l <geoffrey_l!> has quit IRC16:19
*** SomeDumbBumb <SomeDumbBumb!> has joined #yocto16:19
*** blitz00 <blitz00!~stefan@unaffiliated/blitz00> has quit IRC16:19
kergothno, oe metadata isn't deployed to the target. you'd have to check with the manufacturer16:21
ketemphorohh, think i might have found it:  ... so you think that's easier to figure out the bitbake application than try to rebuild a single app by hand?16:21
*** peacememories <peacememories!> has quit IRC16:22
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC16:22
kergothdo you already have the toolchain from the manufacturer? even if you *do* have the exact toolchain (and the glibc version will have to match your rootfs), you'd have to adjujst for any crosscompilation issues yourself, and also use the correct tuning arguments to ensure the resulting binaries rae even compatible with your rootfs libraries16:22
*** mkelly <mkelly!> has joined #yocto16:23
*** Guest93352 <Guest93352!> has joined #yocto16:23
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto16:23
kergothand that's assuming it even works without the patches we're applying to the upstream sources16:23
ketemphoryes, have sdk toolchain and can crosscompile from windows and direct compile on machine16:24
*** peacememories <peacememories!> has joined #yocto16:24
ketemphorIf bitbake is relatively straightforward given a preexisting configuration, I may go that route, it just looks intimidating from the outside16:24
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC16:24
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto16:25
kergoththat depends on what your device manufacturer has provided, really16:26
*** p0kerface|work <p0kerface|work!~bg14ina@kde/bgupta> has joined #yocto16:26
kergothbut as i just described, there'll be difficulty doing either direction, so pick your pain :)16:27
ketemphorwell, they claim that repo has all the files necessary to build the example image that I'm running on now16:27
*** mckoan is now known as mckoan|away16:28
ketemphorthanks, kergoth, you've saved me from a couple of dead-ends anyway ... :)16:30
*** peacememories <peacememories!> has quit IRC16:32
*** peacememories <peacememories!> has joined #yocto16:36
*** caiortp <caiortp!~inatel@> has quit IRC16:36
*** fischerm <fischerm!> has quit IRC16:37
*** JoiF <JoiF!~jofr@> has quit IRC16:40
*** ntl <ntl!> has joined #yocto16:40
*** diego_r <diego_r!> has quit IRC16:43
*** stephano <stephano!~stephano@> has quit IRC16:45
SomeDumbBumbI would not say that bitbake is straightforward.  It's unnecessarily complicated, in fact, I'd say it's a total mess.  It does work, somehow, though.16:49
*** csanchezdll <csanchezdll!> has left #yocto16:49
*** mdnneo <mdnneo!~umaucher@> has quit IRC16:50
*** majuk <majuk!> has joined #yocto16:50
*** t0mmy <t0mmy!> has joined #yocto16:53
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC16:56
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto17:01
kergothI wouldn't say it's unnecessarily complicated, given the problem being solved and the focus on flexibility. The file format is admittedly a bit of a mess, a hodgepodge of declarative and imperative content.17:02
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC17:06
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto17:10
*** paulg <paulg!> has quit IRC17:12
*** peacememories <peacememories!> has quit IRC17:13
*** dreyna <dreyna!> has joined #yocto17:17
*** aehs29 <aehs29!aehernan@nat/intel/x-yayybcpvodtwiouw> has joined #yocto17:17
SomeDumbBumbI agree to disagree.  BitBake's use of inference is incredibly confusing.  There are too many inferred behaviors, which are optionally over-ridden explicitly in a seemingly random architecture of conf/layer.conf, target.bbclass, etc, etc.  I compare it to equally complicated projects in other huge project build systems like buildroot, or even CMake that do the same thing in a manner which seems far better17:17
SomeDumbBumbdesigned and is much easier to understand.17:17
kergothbuildroot has much different goals, and cmake isn't even in the same ballgame. cmake is analagous to make, whereas bitbake and buildroot are a level above that, more along the lines of the buildsystems of debian, fedora, etc, but with crosscompilation capability17:19
SomeDumbBumbCMake handles cross compilation much easier than either bitbake or buildroot17:19
SomeDumbBumbIt also supports fetching source17:20
SomeDumbBumband packaging17:20
SomeDumbBumbInn short, I find CMake vastly superior, and can't believe anyone actually gets anything accomplished with bitbake.  But, then, I guess I am still learning17:21
*** berndhs <berndhs!> has quit IRC17:21
kergothcmake knows nothing about handling crosscompilation for other project buildsystems.17:25
kergothfor its own sources its compiling, sure17:25
kergothnowhere near enough to build a distribution17:25
kergothand buildroot is nowhere near capable enough either, it's weaknesses are largely why oe exists at all17:26
kergothit didn't scale well enough17:26
SomeDumbBumbSorry, do yo know about CMAKE_TOOLCHAIN_FILE ?17:27
SomeDumbBumbwhere you trivially set the compiler, linker, archiver, along with optional flags for all those tools, and sysroot location,17:29
*** peacememories <peacememories!> has joined #yocto17:30
vm_whats best way to reconfigure/rebuild u-boot? with meta-toolchain or bitbake -c u-boot17:31
SomeDumbBumbIt that ^^ type of question that should make people realise how confusing bitbake is to use.17:33
SomeDumbBumbThat shouldn't even be a valid question.  There should be one, standard way to do such a standard operation17:33
*** sgw_ <sgw_!~sgw_@> has joined #yocto17:33
khemSomeDumbBumb: good feedback, if you can comeup with some feature requrests against bitbake that will make it better for users it would be cool17:35
khemSomeDumbBumb: All tools suck in general and some may suck more,17:36
khemwe just want to keep the bar low17:36
*** paulg <paulg!> has joined #yocto17:37
*** dreyna <dreyna!> has quit IRC17:37
vm_how can i rebuild u-boot with meta-toolchain17:40
-YoctoAutoBuilder- build #896 of nightly-oe-selftest is complete: Failure [failed Running oe-selftest] Build details are at
*** peacememories <peacememories!> has quit IRC17:49
kergothSomeDumbBumb: unless CMAKE_TOOLCHAIN_FILE can magically fix all the problems with autoconf, you just proved my point. it can handle crosscompilation for *shit its compiling*, not the buildsystems of other projects it has to call into.17:52
*** peacememories <peacememories!> has joined #yocto17:54
*** stephano <stephano!~stephano@> has joined #yocto17:55
*** dreyna <dreyna!> has joined #yocto17:57
*** majuk <majuk!> has quit IRC17:58
*** itseris <itseris!~emikulin@> has quit IRC18:02
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC18:02
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto18:02
khemkergoth: there is a reason why we dont have a cmake based linux distro18:03
*** ftoth <ftoth!~quassel@> has joined #yocto18:06
*** itseris <itseris!~emikulin@> has joined #yocto18:13
*** jairglez <jairglez!~jairdeje@> has quit IRC18:13
*** peacememories <peacememories!> has quit IRC18:18
*** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-usocmgqhfcryucmv> has quit IRC18:25
-YoctoAutoBuilder- build #857 of nightly-world-lsb is complete: Failure [failed BuildImages] Build details are at
*** dv_ <dv_!> has joined #yocto18:31
*** peacememories <peacememories!> has joined #yocto18:33
jmesmonHey folks, I'm trying to track down why some of my recipes are rebuilding when I change the DISTRO_VERSION variable. I've manually looked at the recipes and their includes & couldn't find a direct usage of DISTRO_VERSION, I've looked at `bitbake -e linux-foo` (I'm trying to keep a custom linux from rebuilding) and not seen any DISTRO_VERSION reference in the tasks. `bitbake-whatchanged linux-foo` doesn't18:35
jmesmonappear useful, it prints out lots of items. bitbake-diffsigs -t linux-foo do_fetch (I'd noticed it running this task) shows some differences that don't really make sense: it has a change to DISTRO_FEATURES which shouldn't be happening (I'm not changing the DISTRO). It also looks like the output is mixed up with 2 things trying to print at the same time (I'm running morty, so this might be fixed in master). Any18:35
jmesmonideas for things to look at that I've missed?18:35
*** majuk <majuk!> has joined #yocto18:38
*** itseris <itseris!~emikulin@> has quit IRC18:41
*** peacememories <peacememories!> has quit IRC18:41
*** jairglez <jairglez!~jairdeje@> has joined #yocto18:44
*** sgw_ <sgw_!~sgw_@> has quit IRC18:48
*** AndersD <AndersD!~anders@> has joined #yocto18:49
JPEWhackerjmesmon: Are you building an SDK?18:50
SomeDumbBumbOK, you're saying CMake can't build a non-CMake project  - or can't make it build croos-platform, or what ?18:51
*** ketemphor <ketemphor!> has quit IRC18:52
jmesmonJPEWhacker: no, just building an image. Also, I've overridden SDKPATH for when I do build an sdk :)18:55
jmesmonOh, this is using poky as the base (so SDKPATH would normally include SDK_VERSION, which in turn uses DISTRO_VERSION).18:56
jmesmonThe bitbake-diffsigs output seems like it could be hinting at the issue, output almost looks like something isn't using the DISTRO config for do_fetch (at some time)18:58
*** peacememories <peacememories!> has joined #yocto18:58
jmesmonOr bitbake-diffsigs might just be wrong.18:58
jmesmonHere's what it says for the curious: (note that the mixing of output is what I see too)18:59
kergothI don't see any mixing of output19:09
kergothSRC_URI is multi-line19:09
kergothlooks exactly how it should afaict19:09
*** yann <yann!> has quit IRC19:11
*** peacememories <peacememories!> has quit IRC19:11
*** vm_ <vm_!> has quit IRC19:19
*** majuk <majuk!> has quit IRC19:21
*** dfaught <dfaught!> has quit IRC19:28
*** sgw_ <sgw_!~sgw_@> has joined #yocto19:29
*** dreyna <dreyna!> has quit IRC19:29
*** zeenix <zeenix!> has joined #yocto19:31
*** majuk <majuk!> has joined #yocto19:31
*** gtristan <gtristan!~tristanva@> has quit IRC19:32
*** zeenix <zeenix!> has quit IRC19:34
*** majuk <majuk!> has quit IRC19:36
*** AndersD <AndersD!~anders@> has quit IRC19:36
*** morphis <morphis!> has quit IRC19:36
*** jairglez <jairglez!~jairdeje@> has quit IRC19:37
*** msvb-lab <msvb-lab!> has quit IRC19:38
*** jairglez <jairglez!~jairdeje@> has joined #yocto19:39
*** msvb-lab <msvb-lab!> has joined #yocto19:42
*** majuk <majuk!> has joined #yocto19:50
*** JaMa <JaMa!~martin@> has quit IRC19:53
*** majuk <majuk!> has quit IRC19:54
*** silviof <silviof!~silviof@unaffiliated/silviof> has joined #yocto19:58
jmesmonkergoth: so the 'DISTRO_FEATURES{bluez5} = Unset' lines interspersed are expected? I'm pretty sure that that text isn't actually in SRC_URI20:02
*** majuk <majuk!> has joined #yocto20:02
jmesmonI mean, it's contents clearly depends on that info, so it it is useful to see it. But mixing it into the output of SRC_URI seems wrong20:02
jmesmonwith fewer 'it's: SRC_URI's contents clearly depends on the DISTRO_FEATURES noted, so it is useful to see the DISTRO_FEATURES values, but mixing the DISTRO_FEATURES values into the output of SRC_URI seems wrong.20:04
kergothjmesmon: that's how bitbake handles 'contains' type variables for the checksum20:05
kergothit's not part of the value for the variable in the metadata, but it *is* in the string that's checksummed for that variable, and bitbake-diffsigs is comparing those, not the original20:06
*** zeeblex <zeeblex!> has joined #yocto20:06
*** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-nonephusfwuzhiqw> has joined #yocto20:07
*** Smitty_ <Smitty_!86bfdc49@gateway/web/freenode/ip.> has quit IRC20:07
*** stephano <stephano!~stephano@> has quit IRC20:10
*** ant_home <ant_home!> has joined #yocto20:15
*** ferry <ferry!~quassel@> has joined #yocto20:18
*** _william_ <_william_!> has joined #yocto20:19
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC20:22
*** bluelightning <bluelightning!~paul@> has joined #yocto20:23
*** bluelightning <bluelightning!~paul@> has quit IRC20:23
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:23
*** dreyna <dreyna!> has joined #yocto20:24
*** sjolley <sjolley!~sjolley@> has quit IRC20:24
*** sameo <sameo!~samuel@> has joined #yocto20:25
*** SomeDumbBumb_ <SomeDumbBumb_!> has joined #yocto20:26
*** sameo <sameo!~samuel@> has quit IRC20:26
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto20:29
*** ferry <ferry!~quassel@> has quit IRC20:29
*** SomeDumbBumb <SomeDumbBumb!> has quit IRC20:30
*** Artox <Artox!~Artox@2a01:8740:1:ff05::1> has joined #yocto20:30
*** ferry <ferry!~quassel@> has joined #yocto20:33
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto20:33
*** majuk <majuk!> has quit IRC20:35
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC20:39
*** lexano <lexano!> has quit IRC20:40
jmesmongot it.20:46
*** majuk <majuk!> has joined #yocto20:50
*** stephano <stephano!stephano@nat/intel/x-hrozostnnvvruowv> has joined #yocto20:52
*** majuk <majuk!> has quit IRC20:57
*** pohly <pohly!> has quit IRC20:58
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has joined #yocto21:03
*** p0kerface|work <p0kerface|work!~bg14ina@kde/bgupta> has quit IRC21:04
*** itseris <itseris!~emikulin@> has joined #yocto21:08
*** MarcWe <MarcWe!> has quit IRC21:09
*** paulg <paulg!> has quit IRC21:11
*** berton <berton!~berton@> has quit IRC21:14
*** baldgeek <baldgeek!> has quit IRC21:15
*** yann <yann!> has joined #yocto21:25
*** majuk <majuk!> has joined #yocto21:29
*** majuk <majuk!> has quit IRC21:33
*** agust <agust!> has quit IRC21:38
*** ferry <ferry!~quassel@> has quit IRC21:44
*** majuk <majuk!> has joined #yocto21:47
*** paulg <paulg!> has joined #yocto21:48
*** majuk <majuk!> has quit IRC21:52
*** diego_r <diego_r!~diego@> has joined #yocto21:54
*** mkelly <mkelly!> has quit IRC21:55
*** lamego <lamego!~jose@> has quit IRC21:58
*** BaloneyGeek|work <BaloneyGeek|work!~bg14ina@kde/bgupta> has quit IRC21:59
*** JPEWhacker <JPEWhacker!cc4da371@gateway/web/freenode/ip.> has quit IRC22:01
*** garbados <garbados!~garbados@2601:1c2:303:6b0:8486:47a2:5f5c:8488> has joined #yocto22:01
*** dreyna <dreyna!> has quit IRC22:02
*** ftoth <ftoth!~quassel@> has joined #yocto22:02
*** gizero <gizero!> has quit IRC22:05
*** majuk <majuk!> has joined #yocto22:05
ftoth@paulg, @khem, thanks guys, I went with ROOTFS_POSTPROCESS_COMMAND and that worked. My initramfs boots and mmc partitions emerge. Now fixup the init script..22:06
*** majuk <majuk!> has quit IRC22:10
*** _william_ <_william_!> has quit IRC22:15
*** stephano <stephano!stephano@nat/intel/x-hrozostnnvvruowv> has quit IRC22:17
*** ftoth <ftoth!~quassel@> has quit IRC22:22
*** ftoth <ftoth!> has joined #yocto22:22
*** ntl <ntl!> has quit IRC22:23
*** majuk <majuk!> has joined #yocto22:24
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC22:26
*** SoniaLeon <SoniaLeon!sleonbau@nat/intel/x-nonephusfwuzhiqw> has quit IRC22:27
*** majuk <majuk!> has quit IRC22:30
*** jairglez <jairglez!~jairdeje@> has left #yocto22:32
*** ftoth <ftoth!> has quit IRC22:41
*** mkelly <mkelly!~martin@> has joined #yocto22:48
*** dv_ <dv_!> has quit IRC22:55
*** dv_ <dv_!~quassel@> has joined #yocto22:55
*** majuk <majuk!> has joined #yocto22:56
paulgglad it worked out for him.22:59
*** majuk <majuk!> has quit IRC23:01
*** nighty-- <nighty--!> has quit IRC23:09
*** msvb-lab <msvb-lab!> has quit IRC23:14
*** ant_home <ant_home!> has quit IRC23:16
*** khem <khem!~khem@unaffiliated/khem> has quit IRC23:22
*** diego_r <diego_r!~diego@> has quit IRC23:29
*** majuk <majuk!> has joined #yocto23:32
*** majuk <majuk!> has quit IRC23:37
*** gourve_l <gourve_l!> has quit IRC23:41
*** gourve_l <gourve_l!> has joined #yocto23:41
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto23:42
*** aehs29 <aehs29!aehernan@nat/intel/x-yayybcpvodtwiouw> has quit IRC23:42
*** aehs29 <aehs29!aehernan@nat/intel/x-uzslmwznguaybkyz> has joined #yocto23:43
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto23:46
*** fischerm <fischerm!> has joined #yocto23:46

Generated by 2.11.0 by Marius Gedminas - find it at!