[OE-core] [PATCH] gcc: Ensure that the shared source directory shared the same sstate hashes
richard.purdie at linuxfoundation.org
Fri Jan 20 18:04:51 CET 2012
On Fri, 2012-01-20 at 00:19 -0800, Saul Wold wrote:
> I tried both a sstate build with and existing tmp and a clean tmp, the
> existing tmp seemed to work ok, but with a clean tmp (and sstate), I got
> the following patch issue still.
> This was with BB_SIGNATURE_HANDLER ?= 'basichash' set.
> ERROR: Command Error: exit status: 1 Output:
> Could not link file
> `.pc/gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch/configure' to `configure': No
> such file or directory
> Applying patch gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch
> patching file configure.ac
> Hunk #1 FAILED at 3073.
> 1 out of 1 hunk FAILED -- rejects in file configure.ac
> patching file configure
> Hunk #1 FAILED at 7594.
> 1 out of 1 hunk FAILED -- rejects in file configure
> Patch gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch does not apply (enforce with -f)
> ERROR: Function failed: patch_do_patch
> ERROR: Logfile of failure stored in:
> NOTE: package libgcc-4.6.2+svnr181430-r20: task do_patch: Failed
> ERROR: Task 882
> (/intel/poky2/distro/meta/recipes-devtools/gcc/libgcc_4.6.bb, do_patch)
> failed with exit code '1'
> I have not tried a clean sstate / clean tmp.
This only happens with basichash and is due to the stamp mismatch
Lianhao mentions. I happens if the stamps are inconsistent and race
against each other with the same WORKDIR. My patches should address this
problem (although the posted patch has a small bug).
More information about the Openembedded-core