**** BEGIN LOGGING AT Sun May 28 03:00:04 2017
May 28 08:43:19 <vm__> hi, i created a custom layer with conf/distro/mydistro.conf  inside, then set DISTRO="mydistro" in build/conf/local.conf  , and when i now run bitbake rpi-hwup-image  it tells me it uses nodistro.0     how can i change that , that it uses poky as before
May 28 08:50:34 <vm__> in put into meta-mydistro/conf/distro/mydistro.conf the line   require conf/distro/poky.conf    and now it shows after running bitbake rpi-hwup-image  DISTRO_VERSION="2.2.1"  . Which tells me that it now uses poky ?
May 28 10:31:59 <vm__> i want to use another u-boot git src,   so i created in my own layer the directories mydistrolayer/recipes-bsp/u-boot   do the file inside now must match any naming-criteria ?
May 28 10:52:44 <vm__> how do i tell bitbake now that it should use my own u-boot-mydistro.bb file
May 28 11:07:22 <fl0v01> vm__: you should be able to set your distro in local.conf or as environment variable DISTRO
May 28 11:07:29 <fl0v01> http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-DISTRO
May 28 11:08:45 <vm__> fl0v01, yes, i did that, but it still uses the u-boot from raspberrypi.bb
May 28 11:09:38 <fl0v01> vm__: ah you dont set your uboot in the distro but in the machine conf i think
May 28 11:11:57 <fl0v01> vm__: PREFERRED_PROVIDER_u-boot_<machine_name> = "<u-boot-recipe>"
May 28 11:12:47 <fl0v01> vm__: hm no you are right, shouldnt matter
May 28 11:13:57 <vm__> is PREFERED_PROV.. wrong line
May 28 11:14:49 <vm__> or should i use  PREFERED_PROVIDER_u-boot_raspberrypi = "u-boot-mydistro.bb"  in local.conf
May 28 11:16:41 <fl0v01> you could try
May 28 11:20:00 <vm__> it went through  bitbake mydistro-image  without errors or complains, but did nothing
May 28 11:20:29 <fl0v01> vm__: here is how variscite specified the u-boot, they did it in the machine conf:
May 28 11:20:29 <fl0v01> https://github.com/varigit/meta-variscite-imx/blob/Krogoth-imx-4.1.15-var01/conf/machine/var-som-mx6.conf#L53
May 28 11:29:23 <binarym> 12:52:45 < vm__> how do i tell bitbake now that it should use my own u-boot-mydistro.bb file
May 28 11:29:41 <binarym> have a look to machine definition, for example in meta-raspberry
May 28 11:31:27 <binarym> for example: https://github.com/akuster/meta-odroid/blob/master/conf/machine/odroid-c2.conf
May 28 11:31:36 <vm__> binarym, they use  UBOOT_MACHINE  but that seemed  to be the config-file-name for u-boot
May 28 11:31:57 <binarym> vm__: what "machine" are u using ?
May 28 11:32:05 <vm__> raspberrypi
May 28 11:32:12 <binarym> uboot settings are 100% machine related
May 28 11:33:21 <binarym> so if the build depends on uboot, you must have some config file somewhere that point to the version to use. Simply try override it using bbappend file
May 28 11:33:52 <vm__> i want to use another git src too
May 28 11:35:02 <vm__> i did  bitbake -c cleansstate virtual/bootloader   and bitbake -c deploy virtual/bootloader  but it rebuilds the old u-boot
May 28 11:35:32 <vm__> PREFERED_PROVIDER as i use it now does not work
May 28 11:36:51 <binarym> vm__: a build is : 1/ an image built following rules of 2/ a distro and for a given 3/ machine
May 28 11:36:58 <binarym> 1/ 2/ and 3/ have their config files
May 28 11:37:13 <binarym> so uboot version to use is defined somewhere there
May 28 11:37:37 <vm__> yes, and i created my own layer to override this
May 28 11:37:45 <vm__> i try to :)
May 28 11:38:02 <binarym> vm__: you probably missed some variable inherited from a include directive
May 28 11:44:58 <binarym> vm__: i just took a look to my yocto tree
May 28 11:44:59 <binarym> and
May 28 11:45:23 <binarym> uboot for raspberry pi looks to be installed by recipe bcm2835-bootfiles.bb
May 28 11:45:40 <binarym> that recipe inherit firmware.inc which is part of meta-raspberrypi too
May 28 11:45:57 <binarym> that firmware.inc point here: git://github.com/raspberrypi/firmware.git;protocol=git;branch=master
May 28 11:46:18 <binarym> and
May 28 11:46:27 <binarym> if you go with your favourite browser to that URL
May 28 11:46:42 <binarym> you'll see that it ships pre-compiled bootloader for raspberrypi
May 28 11:46:46 <binarym> so
May 28 11:47:08 <binarym> if you want to build your own uboot
May 28 11:47:26 <binarym> it probably will be more tricky since you'll have to change the whole way image is built
May 28 11:48:39 <binarym> or hack into this mechanism by overriding bcm2835-bootfiles recipe with a bbappend that 1/ DEPENDS="your uboot recipes" 2/ override the do_deploy task to add your uboot.bin
May 28 11:48:40 <vm__> raspi uses its own bootloader, because gpu is on before cpu is.  but you can then use u-boot to boot your linux kernel, just add "KERNEL_IMAGETYPE="uImage" into your conf/local.conf
May 28 11:48:42 <binarym> good lucj
May 28 11:49:02 <vm__> thx
May 28 11:52:29 <binarym> vm__: if you're new in yocto, will troubleshooting/investigatin that kind of problem, a good entry point is often the deploy dir
May 28 11:53:11 <binarym> i figured out that by looking into my rootfs.rpi-sdimg file :)
May 28 12:50:47 <vm__> fl0v01, its like you said,   PREFERRED_PROVIDER_virtual/bootloader = "filename"   i just typed PREFERRED with only one R at the end
May 28 15:25:04 <berndhs> happy sunday folks. I am trying to generate an rpm with bitbake for chrony, I need an ntp client. How do I generate the rpm?
May 28 15:39:54 <berndhs> is anyone awake here?
May 28 15:40:15 <berndhs> I would like to find out how to generate specific rpms for yocto
May 28 16:35:01 <berndhs> I would like to find out how to generate specific rpms for yocto
May 28 16:35:24 <berndhs> I am trying to generate an rpm with bitbake for chrony, I need an ntp client. How do I generate the rpm?
May 28 16:55:25 <hattzy> berndhs, have you tried changing PACKAGE_CLASSES to package_rpm in local.conf and then bitbake <your_package>
May 28 17:01:22 <berndhs> hattzy: yes i ended up trying that. Success! :) I was missing that I can do bitbake chrony, or bitbake mynewspecialpackage
May 28 20:43:20 <black_13> how is open-embedded related to yocto/poky
May 28 20:43:45 <black_13> is it just an layer of classes and scripts for other projects
May 28 22:31:11 <berndhs> in case anyone is here:
May 28 22:31:39 <berndhs> I would like to try to build yocto for raspi3 with fewer locals
May 28 22:32:05 <berndhs> to reduce size and build time, i want to build it without Chinese support first
May 28 22:32:36 <black_13> i am a newbie
May 28 22:33:51 <berndhs> if you're chinese, dont be insulted, I just want to build minimum config first
May 28 23:08:27 <kergoth> black_13: yocto is an umbrella project which encompasses a number of different projects, and is a means by which multiple companies can collaborate on a common embedded linux baseline. that baseline is openembedded components (bitbake, oe-core) and a reference / demo / testing distribution (poky)
May 28 23:14:22 <black_13> I am trying to get get qt5 as part of qemu image
May 28 23:14:47 <kergoth> use the meta-qt5 layer
May 28 23:15:11 <kergoth> https://layers.openembedded.org/layerindex/branch/master/layer/meta-qt5/
May 28 23:15:19 <black_13> would the meta-qt5 layer require the open-embedd layer
May 28 23:15:29 <black_13> oops i htink you just answered that
May 28 23:15:32 <black_13> maybe
May 28 23:16:07 <kergoth> you will not be able to build *anything* without oe-core, either directly or via the poky repository
May 28 23:16:18 <kergoth> the poky git repository includes bitbake and oe-core along with meta-yocto/meta-poky
May 28 23:16:26 <black_13> ah
May 28 23:16:56 <black_13> so what do i see instructions where the author clones poky and then cd's into poky and clones open embedded
May 28 23:17:05 <black_13> why i mean sorry
May 28 23:21:24 <kergoth> that wouldn't make sense. as i just said, poky includes oe-core already
May 28 23:22:18 <kergoth> meta-openembedded, on the other hand, is an entirely different layer
May 28 23:26:32 <black_13> that is what i had seen: "meta-openembedded" is what i saw.
May 28 23:31:04 <kergoth> meta-openembedded is a separate repository, not included in poky, which contains a number of different layers
May 28 23:37:00 <black_13> do you know of example of using meta-qt5 to make a qemu image
May 28 23:37:18 <black_13> i would need to clone the meta image
May 28 23:37:55 <black_13> and then update the local.conf to include a reference to the meta image ?
May 29 00:00:36 <black_13> http://www.jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.html
May 29 00:05:30 <berndhs> black_13: there is also this page http://www.instructables.com/id/Building-GNULinux-Distribution-for-Raspberry-Pi-Us/
May 29 00:06:41 <black_13> berndhs: thanks
May 29 00:24:14 <black_13> berndhs: would you know how to use the meta-qt5 layer
May 29 00:29:22 <berndhs> not really. I know you can do stuff like bitbake qt-core
May 29 00:29:27 <berndhs> to build rpms
May 29 00:32:03 <berndhs> and I find the rpms in this directory:
May 29 00:32:12 <black_13> berndhs: do you have an example of qt-core use ?
May 29 00:33:20 <berndhs> am i diconnected?
May 29 00:33:24 <berndhs> no
May 29 00:33:35 <berndhs> here /home/bernd/dawork/yocto/poky/rpi-build/tmp/deploy/rpm/cortexa7hf_neon_vfpv4
May 29 00:34:01 <berndhs> ah, a bug in my client, if input starts with a / it takes it as a command
May 29 00:34:11 <berndhs> like /join or /part or /whois
May 29 00:34:33 <berndhs> should do that, shoi;d ask probably
May 29 00:35:00 <berndhs> black_13: qt core is just bawsic doe, right?
May 29 00:35:20 <berndhs> I haven't managed to build qt-creator, just started yesterday
May 29 00:53:03 <berndhs> black_13: for your enjoyment: http://www.yoctoproject.org/bulk/devday-eu-2014/ypdd14-blanc-errors.pdf
May 29 01:52:53 <berndhs> my build seems to hang on the part 0: glib-2.0-1_2.50.3-r0 do_package - 7401s (pid 19900)
May 29 01:53:04 <berndhs> why would it hang there?
May 29 02:03:19 <bluelightning> berndhs: that's unusual
May 29 02:03:37 <bluelightning> berndhs: perhaps you can look in the task log for some clues?
May 29 02:04:19 <bluelightning> tmp/log/<arch>/glib-2.0/1_2.40.3-r0/temp/log.do_package
May 29 02:06:16 <berndhs> let me check there
May 29 02:11:30 <berndhs> i will just tail the next one over night, see what the end sayd
May 29 02:11:56 <berndhs> I think it has been hanging like that 2nd half of today, didn't matter much what I was building
May 29 02:13:33 <berndhs> as if it is runnign out of soemthing, but I can't tell what
May 29 02:14:02 <berndhs> plenty disk space, enough memory, all is there
May 29 02:38:30 <bluelightning> well, it would be interesting to see where the log ended for the one currently running (or that was running, if you already stopped it)
May 29 02:39:32 <berndhs> i whacked it already. Will report anything unusual on the next one, probably people want to know
**** ENDING LOGGING AT Mon May 29 03:00:04 2017