Hi Steve, http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-connectivity/inetutils?h=zeus&id=9e13dad6ea76dd036098ef62427804e4138bf83b It's disabled by default now. You can probably re

#yocto #kernel

I'd say yes except for task-specific variables (one can do QB_OPT_APPEND_task-install for example). Make sure you expand the variable though (d.getVar('QB_OPT_APPEND', True) IIRC?) so that if QB_OPT_A

Hi Sergey, A "hack" I'm thinking about right now would be to remove those variables by hand in a python anonymous function. You want to expand the variable first, then do some python regex or however

Hi VR, I told you on StackOverflow to checkout the dunfell branch of meta-clang. Do that, and recompile again instead of cherry-picking recipes, classes, patches and whatnot. Once you've something tha

#yocto

Hi Jupiter, This should have nothing to do with a Yocto version, if your recipe is not found, it's just not found and it is usually a tell that you either put your recipe in the wrong tree layout or t

Do you have B set up somewhere in your recipe? Otherwise try ${S}/lib/libopentok.so for the source path. Quentin

#dunfell #yocto

If you go into ${WORKDIR} of your recipe (tmp/work/<arch>/<recipe name>), what is the path to libopentok.*.so? Quentin

#dunfell #yocto

Hi, S = "${WORKDIR}/libopentok_linux_llvm_arm64" This is the root directory of your archive and should be used for `S` Cheers, Quentin

#dunfell #yocto

Hi Jupiter, [...] [...] Not sure this will fly nicely (the kernel headers being older than your kernel). Otherwise ok. And here we have the winner :) You don't have a 5.10 linux-yocto recipe so obviou

Hi, So we can stop half guessing and help you can you give us the output of: bitbake -e virtual/kernel | grep -e "^PREFERRED_PROVIDER_" bitbake -e virtual/kernel | grep -e "^PREFERRED_VERSION_" bitbak

Hi Sateesh, Are you sure all layers are checked out at the same branch? (e.g. `dunfell` branch (or a branch with LAYERSERIESCOMPAT in conf/layer.conf with dunfell in it))? I suspect there was a change

Hi Andrew, MACHINE is automatically added to MACHINEOVERRIDES which in turn is automatically added to OVERRIDES. Doc patches welcome if something would benefit more or clearer explanation :) Quentin

Hi, No target named install. Add one or override do_install task since by default it "calls" the install target. [...] IIRC, gitsm in SRC_URI instead of git should handle that: https://docs.yoctoproje

#yocto #toolchain #linux

Hi Andrew, OVERRIDES is set in configuration files usually (always?). It can be either in a distro if you use DISTROOVERRIDES, in a machine if you use MACHINEOVERRIDES, and you might be able to add ma

Hi VR, You need to put the SDK filename into SRC_URI as well otherwise Yocto does not fetch it from the files directory. Also, Ross had a good suggestion too, please check that the recipe or a similar

#dunfell #linux #yocto

Hi VR, If you don't give us the log, we won't be able to help you. Where is the sdk? You need to add it into your SRC_URI (you can also just pass a URL to a git repo or tarball download link). Quentin

#dunfell #linux #yocto

Hi, To be able to help you we'd need the logs of this task. You can either paste the whole output on the console or send us the task log you can find if you carefully read the console output. Quentin

Hi Michael, Use an anonymous python function that sets VERSION, e.g.: python __anonymous() { d.setVar('VERSION', find_version(d)) } as anonymous python functions are always executed during parsing. Th

Hi, You're not compiling a package, you're compiling a recipe named obexpushtest whose output is packages (one of which is named the same as the recipe, hence the confusion). But here, you're adding a

Hi, You're not compiling a package, you're compiling a recipe named obexpushtest whose output is packages (one of which is named the same as the recipe, hence the confusion). But here, you're adding a