Yes, thanks. I am currently doing that but I am struggling to
understand where to look. From what I can tell the layers are not on
an official kirkstone release, not sure the reason for this. It is
based on a imx-5.15.71-2.2.0.xml release but then the layers have been
moved to a different sha. I have been able to build the
imx-5.15.71-2.2.0.xml from scratch but right now the customer would
like to be able to build the current setup. But I will continue to
work on it. The reference build still builds so it is just when trying
to duplicate the build and building from scratch.
/Måns
Den fre 1 dec. 2023 kl 13:20 skrev Alexander Kanavin <alex.kana...@gmail.com>:
>
> You need to try plain poky then because the error does not happen
> there. Then figure out where the difference is.
>
> Alex
>
> On Fri, 1 Dec 2023 at 12:56, Mans Zigher <mans.zig...@gmail.com> wrote:
> >
> > I have now tried building a multitude of different machines and
> > switched to core-minimal-image and still I get these postinstall
> > intercept scripts failing. Depending what distro and machine I build I
> > get different errors but It is always a postinstall intercept hook
> > script that fails and it is always related to missing some directory
> > under the rootfs of the image that I am currently trying to build.
> >
> > BR
> >
> > Den tors 30 nov. 2023 kl 19:11 skrev Måns <mans.zig...@gmail.com>:
> > >
> > > Hi,
> > >
> > > I have taken over a imx8mm project that is based on kirkstone. I don't
> > > think it is an official release and some layers are not even a
> > > kirkstone release. The project has a reference build but currently it
> > > is not possible to build from scratch. I have been fixing some issues
> > > on the way to try and build a complete build from scratch but now I
> > > have encountered an issue when creating the rootfs that I am
> > > struggling with. The issues that I am getting is
> > >
> > > ERROR: fsl-image-gui-1.0-r0 do_rootfs: The postinstall intercept hook
> > > 'update_mime_database' failed, details in
> > > /workspace/mender-imx8mm/builds/tmp/work/imx8mm_var_dart-fslc-linux/fsl-image-gui/1.0-r0/temp/log.do_rootfs
> > > ERROR: Logfile of failure stored in:
> > > /workspace/mender-imx8mm/builds/tmp/work/imx8mm_var_dart-fslc-linux/fsl-image-gui/1.0-r0/temp/log.do_rootfs.335539
> > > ERROR: Task
> > > (/workspace/mender-imx8mm/sources/meta-variscite-sdk/recipes-fsl/images/fsl-image-gui.bb:do_rootfs)
> > > failed with exit code '1'
> > >
> > > checking the log file
> > >
> > > NOTE: Running intercept scripts:
> > > NOTE: > Executing update_mime_database intercept ...
> > > NOTE: Exit code 1. Output:
> > > Updating MIME database... this may take a while.
> > > Directory
> > > '/workspace/mender-imx8mm/builds/tmp/work/imx8mm_var_dart-fslc-linux/fsl-image-gui/1.0-r0/rootfs/packages'
> > > does not exist!
> > >
> > > In poky/meta/classes/mime.bbclass there is a comment that seems to
> > > refer to this issue
> > >
> > > # $D${MIMEDIR}/packages belong to package shared-mime-info-data,
> > > # packages like libfm-mime depend on shared-mime-info-data.
> > > # after shared-mime-info-data uninstalled, $D${MIMEDIR}/packages
> > > # is removed, but update-mime-database need this dir to update
> > > # database, workaround to create one and remove it later
> > > if [ ! -d $D${MIMEDIR}/packages ]; then
> > > mkdir -p $D${MIMEDIR}/packages
> > > update-mime-database $D${MIMEDIR}
> > > rmdir --ignore-fail-on-non-empty $D${MIMEDIR}/packages
> > > else
> > > update-mime-database $D${MIMEDIR}
> > > fi
> > >
> > > This is not called so no packages directory doesn't exist and the
> > > intercept script failed. I can adjust the script
> > > poky/scripts/postinst-intercepts/update_mime_database
> > >
> > > echo "Updating MIME database... this may take a while."
> > > update-mime-database $D${mimedir}
> > >
> > > By adding a similar logic I will get forward but with my build but
> > > that doesn't seem like the right solution. Also I just get some other
> > > issue related to a second intercept script update_desktop_database so
> > > to me it seems more like something is not correctly set up in the
> > > build. I am trying to understand how these intercept scripts are
> > > configured and why they are not working for my build. Any pointers on
> > > how to move forward would be much appreciated.
> > >
> > > BR
> >
> >
> >
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61827): https://lists.yoctoproject.org/g/yocto/message/61827
Mute This Topic: https://lists.yoctoproject.org/mt/102901287/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
