SYSTEMD_SERVICE_${PN} should just be set to the service name, not the full path. So… SYSTEMD_SERVICE_${PN} = "testapp-extra@.service" Also, consider using ${systemd_system_unitdir} instead of ${system

Hi all, I’m hoping that someone can just answer this off the top of their head – don’t bother if you have to dig much. We’ve got a C recipe (built with cmake, if that’s relevant) that seems to be othe

I retract my question and apologize for being an idiot… Apparently somewhere along the line while I wasn’t paying attention, the entirety of that upstream git repo got pulled into our local codebase,

Hi all, I have a component in our build that’s pulling from an upstream git server, so I decided to set the PATCHTOOL=”git” so that it’s easier to determine in the local repository what patches have b

Assuming you’re using the default rpm packaging, you can extract the contents of the rpm (from tmp/deploy/rpm/<target>) file to a staging directory using rpm2cpio and piping to cpio (easiest way I kno

FYI, we’re doing the same internally (vendor supplied FIPS supported openssl 1.0.2), and the layer Armin suggests worked for us on zeus with minimal additional tweaking. Good luck! -Sean

#python

The simplest thing I've found is checking/comparing the BuildID that GCC embeds in the ELF file after I force it to recompile. Eg: $ file tmp/work/qemux86_64-poky-linux/linux-yocto/5.2.28+gitAUTOINC+d

I don’t know offhand, but the kernel documentation seems relatively straightforward. I can start investigating in that direction and see how complex it looks like it’s going to be. When you say that r

Anyone have any thoughts or guidance on this? It seems like a pretty major bug to me. We’re willing to put the work in to fix it, and if it’s not something the upstream community is interested in, I’l

The kernel doesn’t have reproducible builds by default because of a handful of variables (including timestamps). If you rebuild, you get a different binary every time. Those can be changed and overrid

Hi all, We’ve discovered that (quite frequently) the kernel that we deploy doesn’t match the unstripped one that we’re saving for debug symbols. I’ve traced the issue to a combination of an sstate mis

I actually went on vacation right after I sent that message. (Thank you for your incredibly quick reply, by the way!) Once I get back late next week, I'll try to see how reproducible it is in our envi

Hi all, This is probably a fairly short question (I hope): I’m working on a branch based on zeus. I found a bug in the way that one of our recipes was handling something during do_configure (which cau

Hi all, Short version: We have an intermittent issue where under certain circumstances, a build that fails on a fetch task may result in a corrupted parent repo. I’m wondering if anyone has heard of a

If the issue were just that your FILES_* variables were set incorrectly, you’d at least end up with the .ko file somewhere in your ${WORKDIR}/image (${D}) directory. You’d almost certainly find anothe

Hi all, I’m in the middle of our organization’s upgrade to the most recent version of poky (3.0) and I’m finding that more recent versions of recipes in our poky layer aren’t showing up as the most re

I’m not an expert on compiling kernel modules, but I can at least answer some of your questions to get started. I’m also not an actual expert, but just another user, so it’s entirely possible that som

I finally found it… §25 of the mega manual. Not sure if it’s anywhere else that’s easier to find but I guess I just needed to ask. Thanks! -Sean

Hi all, This is probably a super easy question, but I’ve been searching half the day and decided it would be faster to ask for help. I know I’ve seen documentation in one of the manuals that points ou