Actually, I found the upstream patch I backported, which you're probably
better off using (same diff though).
https://lore.kernel.org/patchwork/patch/773330/
On Sat, Jan 30, 2021 at 2:26 AM Joel A Cohen via lists.yoctoproject.org
wrote:
> I'm not sure if this is your issue, but I had a simi
:=
>> msm8909_defconfig`, so I tried to set `KBUILD_DEFCONFIG =
>> "msm8909_defconfig"`, but that is failing with different errors, such as:
>> >
>> > ```
>> > error: 'VM_ARM_DMA_CONSISTENT' undeclared (first use in this function);
>> did you mean
I think you need to set SYSTEMD_AUTO_ENABLE = “disable” (actually any value
other than “enable”) in your bbappend.
(It looks like SYSTEMD_AUTO_ENABLE_${PN} is intended to work too, but I
can’t verify it at the moment and reading over systemd.bbclass I’m not sure
if it works or not)
—Aaron
On
You would need to add libgpiod-dev, presumably, to get the build
requirements.
On Fri, Jul 17, 2020 at 4:23 PM Scott Whitney wrote:
> I should also note that gpioinfo and other tools from libgpiod run as
> expected on the target, and that /usr/lib has libgpiod.so.2
> (libgpiod.so.2.1.1) in it.
Centos 8 'which' installs an alias by default: alias which='(alias; typeset
-f) | /usr/bin/which --tty-only --read-alias --read-functions --show-tilde
--show-dot'
This comes from the which rpm, in /etc/profile.d/which.sh
This breaks in OE, I'm guessing because the shell used doesn't support
One of my most frequent annoying mistakes is to forget to run package index.
It would be nice if I could INHERIT += "auto-package-index" or something
like that.
Is there a hook that such a class would easily be able to hook into?
--Aaron
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages
I'm trying to create a multi-partition image, and just ran across a
difficult to track-down issue that I'm a little curious about.
It's the intersection of rm_work, and needing to get to the sysroot of
another image recipe. RM_WORK_EXCLUDE_ITEMS is respected insomuch as I have
an empty directory
On Wed, Mar 4, 2020 at 10:53 PM Kent Dorfman
wrote:
> On 3/3/20, Aaron Cohen wrote:
> >> > # Once satisfied with changes:
> >> > 3) git add $BUILDDIR/workspace/sources/ && git commit -m
> "Added
>
> Does the git add have to be done as specified above? I made changes
> and inside the directory
The “git commit” step is just how you tell devtool about your changes. Each
commit will result in a patch file in your layer (conversely, each patch
file ends up as a commit in the sources directory after your initial
“devtool modify”)
Notably, this git repo is only loosely connected to the repo
devshell is good for playing around, but I don't know of any blessed way to
just have it somehow modify recipes and create patches magically. I'd be
interested to hear if there is something like that.
The closest to what I think you want is the "devtool" workflow
On Tue, Feb 25, 2020 at 2:28 PM Martin Jansa wrote:
> On Tue, Feb 25, 2020 at 02:10:15PM -0500, Joel A Cohen wrote:
>
>
> > PV_pn-recipe1 = "1.0.1+git${SRCPV}" # I'm not sure if this would
> actually
> > work?
>
> Yes, this is how SRCPV
gt; On Tue, Feb 25, 2020 at 01:21:53PM -0500, Joel A Cohen wrote:
> > Hi all,
> >
> > What I've done for quite a while when creating recipes for code that is
> > under heavy development is create 2 version of the recipe.
> >
> > 1) recipe_1.0.0.bb (a known-s
Hi all,
What I've done for quite a while when creating recipes for code that is
under heavy development is create 2 version of the recipe.
1) recipe_1.0.0.bb (a known-stable recipe)
2) recipe_git.bb (which contains something like:
SRCREV="${AUTOREV}"
SRCPV="1.0.1+git${SRCPV}"
DEFAULT_PREFERENCE
I’m using thud latest and trying to update the initramfs that is bundled
into my kernel.
For some reason, my initramfs is updated in the images directory, but I’m
still getting some old version of the initramfs bundled into the kernel
when I rebuild my image.
Anyone have advice about what to
As a user, I much prefer having one MESON_BUILD_TYPE variable that I can
modify using the pn-operator, even if the acceptable values are a little
less pretty. The alternative is a variable that I have to guess that name
of and what valid values are per-recipe. Sure it's just MESA_BUILD_TYPE
now,
Hi all,
My layer has a bunch of "development" recipes that contain something like:
PV = "1.1.2+git${SRCPV}"
SRCREV = "${AUTOREV}"
DEFAULT_PREFERENCE = "-1"
In these cases, my recipes have a "known good" version that has a specific
known-good version number (recipe_1.1.2.bb), and then the
16 matches
Mail list logo
