[OE-core] util-linux_2.26.2.bb, do_patch failed with exit code '1

[Burton, Ross]

On 13 February 2016 at 12:35, Nathan Sowatskey <nathan at nathan.to> wrote:

> Thank you for you help. I must admit that I don’t know how to interpret
> the result, so I have attached env.txt to see if that means anything to
> you, or others


Understanding bitbake -e is very useful so whilst I could just tell you
that it's the meta-cube layer breaking, I'l show you what it all means
first. :)

As you're interested in a particular variable (in this case, SRC_URI),
search the file for the assignment.  It easiest to search for the
[newline]SRC_URI=, above the assignment is list of operations that resulted
in the final value.

# $SRC_URI [8 operations]
> #   append /home/builder/git/poky/meta/conf/bitbake.conf:600
> #     [vardepsexclude] "APACHE_MIRROR ..."
>

Source mirror variables being added to the variable dependencies exclusion
list so that changing source mirrors doesn't cause everything to re-fetch.


> #   set /home/builder/git/poky/meta/conf/bitbake.conf:618
> #     ""
>

Default SRC_URI or "" in bitbake.conf.


> #   set /home/builder/git/poky/meta/conf/documentation.conf:387
> #     [doc] "The list of source files -..."
>

Documentation added to the [doc] flag.


> #   set
> /home/builder/git/oe-core/meta/recipes-core/util-linux/util-linux.inc:26
> #
> "${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-linux-${PV}.tar.xz
>            "
>

util-linux.inc setting the tarball URI.


> #   append /home/builder/git/oe-core/meta/recipes-core/util-linux/
> util-linux_2.26.2.bb:19
> #     "file://util-linux-ng-replace-siginterrupt.patch
>  file://util-linux-ng-2.16-mount_lock_path.patch ..."
>

Version-specific patches appended in the recipe itself.

#   set /home/builder/git/oe-core/meta/recipes-core/util-linux/
> util-linux_2.26.2.bb:20
> #     [md5sum] "9bdf368c395f1b70325d0eb22c7f48fb"
> #   set /home/builder/git/oe-core/meta/recipes-core/util-linux/
> util-linux_2.26.2.bb:21
> #     [sha256sum]
> "0e29bda142528a48a0a953c39ff63093651a4809042e1790fbd6aa8663fd9666"
>

The recipe adding the version-specific checksum flags.


> #   append
> /home/builder/git/meta-overc/meta-cube/recipes-core/util-linux/util-linux_2.%.bbappend:8
> #     "         file://pam.d    ${NSENTER_PATCH} "
>

The meta-cube layer appending more patches via a non-version-specific
bbappend.  That ${NSENTER_PATCH} looks suspicious!

# pre-expansion value:
> #
> "${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-linux-${PV}.tar.xz
>             file://u
> til-linux-ng-replace-siginterrupt.patch
> file://util-linux-ng-2.16-mount_lock_path.patch
>   file://uclibc-__progname-conflict.patch
> file://configure-sbindir.patch             file://fix-pa
> rallel-build.patch             file://runuser.pamd
> file://runuser-l.pamd             ${OLDHOST}
>         file://pam.d    ${NSENTER_PATCH} "
>

This is what the SRC_URI looks like after all those expressions have been
evaluated, but before the variable references have been expanded.  Note
${NSENTER_PATCH} at the end.


> SRC_URI="
> http://kernel.org/pub/linux/utils/util-linux/v2.26/util-linux-2.26.2.tar.xz
>             file://util-linux-ng-replace-siginterrupt.patch
> file://util-linux-ng-2.16-mount_lock_path.patch
> file://uclibc-__progname-conflict.patch
> file://configure-sbindir.patch             file://fix-parallel-build.patch
>             file://runuser.pamd             file://runuser-l.pamd
>             file://pam.d    file://nsenter-to-be-more-flexible.patch "


The expanded variable value.  NSENTER_PATCH has been replaced with
nsenter-to-be-more-flexible.patch.

Conclusion: meta-cube broke.  I don't think util-linux in Jethro has
changed recently, so I'd suggest that meta-cube introduced a broken patch.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160215/01b95a83/attachment-0002.html>