[yocto] unmodified binary RPM installed on rootfs?
Russell Peterson
bluehills7 at comcast.net
Sun May 21 16:43:06 PDT 2017
Hello,
I am fairly new to yocto and I think I’m having trouble installing an RPM on the rootfs. What I am trying to do is install an arm64 binary RPM file straight onto the root file system without a recipe… just use the native rpm tool to put it there. There are several reasons why I’m experimenting with this. Seems fairly simple but I have now been messing around for days with little to show for it. Here is what I’m doing…
Added to the image bb file:
————————
ROOTFS_POSTPROCESS_COMMAND += "install_mtt ; "
IMAGE_LINGUAS ?= "en-US” <— Wondered if this was a UTF-8 issue
fakeroot install_mft () {
${STAGING_BINDIR_NATIVE}/rpm -i --nodeps --root=${IMAGE_ROOTFS}/ /mtt-4.7.0-21-arm64-rpm/RPMS/mtt-4.7.0-21.arm64.rpm
}
———————
This is the error I see.
DEBUG: Executing shell function install_mft
error: unpacking of archive failed: cpio: Bad magic
WARNING: /yocto-00dc025f/work/mymach-poky-linux/core-image-full/1.0-r0/temp/run.install_mtt.2846:1 exit 1 from '/yocto-00dc025f/sysroots/x86_64-linux/usr/bin/rpm -i ---nodeps --root=/yocto-00dc025f/work/mymach-poky-linux/core-image-full/1.0-r0/rootfs/ /mtt-4.7.0-21-arm64-rpm/RPMS/mtt-4.7.0-21.arm64.rpm’
Seems like this should work. I have no idea what magic number the file command doesn’t like. I looked through the files and they all look legit. Maybe this is an RPM version issue? I think the original RPM was created with 4.8 and the poky version I’m using is 5.3?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170521/895b700f/attachment.html>
More information about the yocto
mailing list