**** BEGIN LOGGING AT Mon Jun 03 02:59:57 2019 Jun 03 05:09:53 How can I tell a bitbake recipe that I want to to use the `go` compiler without having it to try to do the normal `go` installation/packaging? Jun 03 05:10:26 I'm trying to install this: https://github.com/LukeShu/systemd-timesyncd-wait which looks like it doesn't fit the normal way a go project is packaged but is very simple and comes with a Makefile Jun 03 06:36:13 Hacky solution is to overwrite the do_unpack, do_install etc! Pretty sure there must be a better way but it sure isn't easy to find what it is Jun 03 06:42:53 Nope, this is dumb. Think it will be simpler for me to reimplement this package in another language than try to fight against Yocto. Really frustrating. Jun 03 10:01:03 hi, how can I get libatomic.so.1 into my yocto image? (not libatomic-ops) Jun 03 10:02:14 I can download this https://rpmfind.net/linux/RPM/fedora/devel/rawhide/armhfp/l/libatomic-9.1.1-1.fc31.armv7hl.html and rsync the contents into the target image, which works (but does not seem viable) Jun 03 10:21:39 I'm still trying to build a 32bit kernel for a 32bit image with meta-intel and with the kernel-provider "linux-intel" Jun 03 10:22:05 however, I'm still failing. I have set this TARGET_CC_KERNEL_ARCH: TARGET_CC_KERNEL_ARCH = "-m32 -march=nehalem -mtune=generic -mfpmath=sse -msse4.2 -Wformat -Wformat-security -Werror=format-security" Jun 03 10:22:26 but kernel modules are still linked as ELF 64-bit LSB relocatable, x86-64 Jun 03 10:24:56 litb: could you try to build with intel-core2-32 machine instead? I don't know how much compatible it is with corei7-64 from kernel side, but since many things are handled not through the DeviceTree (ACPI instead?) it might work. Disclaimer: I don't know much about Intel so just throwing ideas at you basically :D Jun 03 10:27:38 qschulz, thanks, I will try if I'm not getting results soon Jun 03 10:28:30 qschulz, I'm confused that even though kernel-arch.bb has a `TARGET_CC_KERNEL_ARCH ?= ""` which is documented as saying it should be assigned the kernel compile flags, I don't see a use anywhere with git grep! Jun 03 10:28:49 the only occurance of TARGET_CC_KERNEL_ARCH actually is in that file, and in my local.conf. how can that be? Jun 03 10:29:24 (kernel-arch.bb is in OE's meta/classes/) Jun 03 10:30:42 ah sorry, it's assigned in the line below to HOST_CC_KERNEL_ARCH .. Jun 03 11:45:55 hmm, I executed the devshell like so bitbake -c devshell linux-intel Jun 03 11:46:21 but the shell prompt that is opened doesn't have the variables in its environment, like MACHINE Jun 03 11:46:27 "echo $MACHINE" gives nothing Jun 03 11:49:29 litb: did you run 'source poky/oe...' Jun 03 11:51:04 opennandra, yes. I'm able to do a normal build even, but devshell doesn't appear to have the yocto variables available? Jun 03 11:51:37 litb: maybe you have some exotic shell? I have samne when e.g. run devshell in docker Jun 03 11:51:51 using bash Jun 03 11:51:51 litb: what is your build evn? Jun 03 11:52:05 litb: I mean terminal Jun 03 11:52:12 screen Jun 03 11:53:43 variables like BUILD_CC and others from yocto are visible. but those are only few Jun 03 11:55:34 I'm just going to try genericx86 now Jun 03 12:14:56 qschulz, i'm using genericx86 now, using the core2-32 tune, and use TUNE_CCARGS_append = " -march=nehalem -msse4.2" now in my local.conf. Jun 03 12:15:19 if it works, I'll make a proper -bsp layer and put that into the layer Jun 03 12:31:55 one other question: I removed the directories below tmp/work, and now when I want to rebuild the image, it complains about files being missing in work/ Jun 03 12:32:19 I think this is because the cache is now in inconsistent state with regard to files in tmp/work. How can I fix this? Jun 03 12:33:11 what were you trying to achieve by deleting directories beloew tmp/work ? Jun 03 12:33:43 qschulz, since I changed the machine name, I wanted to clean-up space on my disk Jun 03 12:34:41 so I removed the built intermediate files in work/. I thought, since many of the intermediay files are in buildenv/cache anyway, I could run a new build without waiting for too long. Jun 03 13:32:18 New news from stackoverflow: Why does BitBake error if it can't find www.example.com? Jun 03 15:41:02 What is the best practice to build a .bb receipt that aims two targets? With slightly different SRC_URI for each target Jun 03 15:41:46 two machines? Jun 03 15:44:17 same machine, two different image types. Jun 03 15:44:42 basically two different .sh I want to install depending on the image type Jun 03 15:45:03 how would that work if you run 'bitbake one-image two-image three-image'? Jun 03 15:45:21 you can't modify a recipe based on what image it installs into, you dont know what image it installs into until after the package has been built from it Jun 03 15:45:37 if you want to go by *machine*, you can do that, but not by image Jun 03 15:45:58 recipes emit packages, packages are installed into images Jun 03 15:46:00 leitao: you could build two different packages Jun 03 15:46:17 and install only the one with the sh script you want in it Jun 03 15:46:29 qschulz: hmm, is this a best practice? Jun 03 15:46:31 (that's one way to do it, might not be the best) Jun 03 15:47:05 well, the overriding method with _machine for example, does not exist for images Jun 03 15:48:03 can I ask why you have two different .sh in the first place? in which ways are they different? Jun 03 15:48:51 qschulz well, I have two images, and depending on the image, a specific package should "install" a specific .sh for that image Jun 03 15:49:06 if I have SRC_URI_machine = "", it seems to work Jun 03 15:49:12 just make two recipes / two packages and add the appropriate one to image_install Jun 03 15:49:20 machine and image are two completely different things Jun 03 15:49:28 right Jun 03 15:49:29 and are largely orthogonal Jun 03 15:49:40 leitao: the question is, what is this sh script doing. You might be choosing the wrong path Jun 03 15:50:19 (I mean, you might need to adapt your SW and not Yocto for it to be cleaner) Jun 03 15:50:25 Sometimes you have a choice, some other times not Jun 03 15:51:29 right Jun 03 15:51:41 let me try to think more about it. Thanks Jun 03 15:54:11 newbee here, trying to get advice on debugging patch files that seem to be failing silently. Is this the right irc? Jun 03 17:02:52 New news from stackoverflow: Where can I find what drivers built in my yocto project Linux kernel image? Jun 03 17:51:54 hm, I have checked-out the warrior branch of poky, but there's no "yocto-bsp" and "yocto-kernel" script in poky/scripts ? Jun 03 17:58:40 ah, apparently they dropped it Jun 03 19:03:08 New news from stackoverflow: Set python dist-packages path for autotools in Yocto bitbake Jun 03 19:17:54 Hi, I'm wondering if anyone has used Yocto to create web / app / server images to run as VMs as part of an immutable infrastructure pattern. Jun 03 19:18:44 From what I understand the leading tools in the space are Packer, which creates a production ready image by running scripts in a running VM and then memorializing it, Jun 03 19:19:17 and LinuxKit, which works similar to Yocto in that it builds an image offline in a build environment, but was created by the Docker people so uses Docker containers everywhere. Jun 03 19:20:50 For example - the postgresql recipe is in meta-oe. Has anyone created an image using the postgresql layer, along with a custom layer to run a database initialization script, taken the image and run it in a VM as a 'code-as-infrastructure' copy of their database server? **** ENDING LOGGING AT Tue Jun 04 03:00:18 2019