gstreamer1.0-plugins-bad failure

[PaulDeMetrotion]

I am in the process of migrating to the new Freescale repository linux-imx.git and upgrading the kernel to version 4.1.15 for a Yocto build project. Everything is proceeding well - I can build my u-boot and linux images and can build the core-image-minimal images. When I try to build the fsl-image-multimedia image, I get the following error:

ERROR: Command Error: exit status: 1 Output:
Applying patch 0001-PATCH-install-gstaggregator-and-gstvideoaggregator-h.patch
patching file gst-libs/gst/base/Makefile.am
patching file gst-libs/gst/video/Makefile.am
Hunk #1 FAILED at 19.
1 out of 1 hunk FAILED -- rejects in file gst-libs/gst/video/Makefile.am
Patch 0001-PATCH-install-gstaggregator-and-gstvideoaggregator-h.patch does not apply (enforce with -f)
ERROR: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: /home/pauldemet/fsl-arm-yocto-bsp-tesla/build-c421/tmp/work/cortexa9hf-vfp-neon-mx6qdl-poky-linux-gnueabi/gstreamer1.0-plugins-bad/1.6.0-r0/temp/log.do_patch.15994
ERROR: Task 1324 (/home/pauldemet/fsl-arm-yocto-bsp-tesla/sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.6.0.bb, do_patch) failed with exit code '1'

The following link discusses this error over a year ago but I cannot find the resolution.

[meta-fsl-arm] gstreamer1.0-plugins-bad failure - Patchwork 

Anybody have the answer???

[nfkt_geon]

Hi,

  Facing same issue, trying to build for MYD-C8MMX, its SDK still tries to fetch from CodeAurora, so i manually changed the repo from CodeAurora to Github manually, but after fetch is complete, and when tried to build face with same issue.

[gusarambula]

Hello Paul DeMetrotion,

Are you still having issues with the migration?

Since you are switching to a newer kernel version you would need to make sure that the available images do use the correct package versions. It may be that the multimedia image recipe requires or makes reference to an older version of gstreamer.

The case of the thread you mention actually covers this scenario where it’s looking for headers that were not available. Since it’s an old reported issue I would expect it to be fixed on the Community BSP.

If the image builds normally on the unchanged BSP (which I would expect, I’ll try to test it later) perhaps there was a configuration missing when migrating.

Regards,