> One interesting discovery from the build log when comparing to the
> working application shows that the working application creates a link to
> the systemd service, while the non-working application does not:
>
> Installing B on root
> Downloading file:[...]/B.ipk.
> Configuring B.
> B.postinst
> On 19/04/2023 11:02, Pelle Windestam wrote:
>> Any ideas? I do not know where to continue troubleshooting from here. Is
>> it possible to "debug" the postinstall scriptlet in the environment that
>> it is running in?
>>
> It's a shell script. You can ad
Hello everyone,
I'm having an issue with a postinstall scriptlet failing for a package
that I am trying to add to my Yocto image. Initially I had a simple
CMake C++ application that installs itself (a single binary file), a
systemd service and a d-bus interface file. This was causing no issues.
> I am using Yocto 2.5 and have a working multilib-enabled image based on poky
> which includes libgdiplus (64-bit). Due to requirements I had to add the
> 32-bit version, so I added lib32-libgdiplus to my image recipe. This caused
> the following error output from bitbake:
> WARNING:
Hi all,
I am using Yocto 2.5 and have a working multilib-enabled image based on poky
which includes libgdiplus (64-bit). Due to requirements I had to add the 32-bit
version, so I added lib32-libgdiplus to my image recipe. This caused the
following error output from bitbake:
WARNING:
Hi all,
I am using Yocto 2.5 and have a working multilib-enabled image based on poky
which includes libgdiplus (64-bit). Due to requirements I had to add the 32-bit
version, so I added lib32-libgdiplus to my image recipe. This caused the
following error output from bitbake:
WARNING:
> >>I added NAND and UBIFS support to my Yocto layer machine config file:
> >>
> >>UBOOT_CONFIG = "nand"
> >>UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_config"
> >>UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_nand_config"
> >>UBOOT_CONFIG[nand] += "ubi"
> >>UBOOT_CONFIG[nand] += "ubifs"
> >>
> >>But my
Subject: RE: [yocto] Trouble building mono (when building an image)
>
> > Just a quick thing for you to try: can you delete /usr/bin/monodis
> > from your host and retry building? (remember to clean sstate for your
> > package)
>
> It seems like I do not have a /usr/bin/monodis on my host,
I'm trying to include mono in my image. I can successfully build the mono
recipe by itself, but when I try to build my image it fails with the following
error message:
Error:
Problem: package test-sw-9.1.1b3-r0.aarch64 requires mono, but none of the
providers can be installed
- conflicting
