[yocto] [meta-raspberrypi] Current master broken

[Andrei Gherzan]

Hi Gary,


On Sat, Dec 3, 2016 at 2:16 PM, Paul Barker <paul at paulbarker.me.uk> wrote:
> On Sat, 3 Dec 2016 08:33:40 +0100
> Gary Thomas <gary at mlbassoc.com> wrote:
>
>> I'm currently unable to build for the RaspberryPi-3 using the master branch:
>>
>> Build Configuration:
>> BB_VERSION        = "1.32.0"
>> BUILD_SYS         = "x86_64-linux"
>> NATIVELSBSTRING   = "universal"
>> TARGET_SYS        = "arm-amltd-linux-gnueabi"
>> MACHINE           = "raspberrypi3"
>> DISTRO            = "amltd"
>> DISTRO_VERSION    = "2.2+snapshot-20161202"
>> TUNE_FEATURES     = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7"
>> TARGET_FPU        = "hard"
>> meta              = "master:9e63f81c78e284c9b325fe04a1b59e61c7ad8a1a"
>> meta-amltd        = "master:074120ab3a82cea0ac50d4e9eec89130a860a4fa"
>> meta-raspberrypi  = "master:44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9"
>>
>> Initialising tasks: 100% |#############################################################| Time: 0:00:00
>> Checking sstate mirror object availability: 100% |#####################################| Time: 0:00:00
>> NOTE: Executing SetScene Tasks
>> NOTE: Executing RunQueue Tasks
>> ERROR: linux-raspberrypi-1_4.4.28+gitAUTOINC+5afda48c34-r0 do_kernel_metadata: Function failed: do_kernel_metadata (log
>> file is located at
>> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.5647)
>> ERROR: Logfile of failure stored in:
>> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.5647
>> Log data follows:
>> | DEBUG: Executing shell function do_kernel_metadata
>> | [ERROR]: processing of file /tmp/tmp.bXPr8PVPz3 failed
>> | /build/rpi3_2016-09-13/tmp/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd: line 29: : No such file or directory
>> |
>> | Context around the error is:
>> |
>> |     #
>> |     prefix /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/
>> |     kconf non-hardware /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
>> |     prefix /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/
>> |     patch "/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch"
>> |     # run time: 0 seconds
>> |     # processed files:
>> |     # _cfg /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
>> |     # _cfg /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
>> |
>> | See pre-processed file /tmp/tmp.bXPr8PVPz3 for more details
>> | #
>> | # scc v0.8
>> | # processed: Fri Dec  2 04:12:25 CET 2016
>> | #
>> | # This is a scc output file, do not edit
>> | #
>> | [ERROR]: processing of file /tmp/tmp.eTLAT789Q2 failed
>> | # _reloc_dir /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux
>> | # _reloc_dir /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux
>> | /build/rpi3_2016-09-13/tmp/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd: line 29: : No such file or directory
>> |
>> | Context around the error is:
>> |
>> |     #
>> |     prefix /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/
>> |     kconf non-hardware /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
>> |     prefix /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/
>> |     patch "/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch"
>> |     # run time: 1 seconds
>> |     # processed files:
>> |     # _cfg /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
>> |     # _cfg /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
>> |
>> | See pre-processed file /tmp/tmp.eTLAT789Q2 for more details
>> | WARNING: exit code 1 from a shell command.
>> | ERROR: Function failed: do_kernel_metadata (log file is located at
>> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.5647)
>> ERROR: Task (/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata)
>> failed with exit code '1'
>>
>> I also tried kernel version 4.7:
>> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+a45a35c085-r0 do_fetch: Fetcher failure: Unable to find revision
>> a45a35c08598b23f9fd82e49c83b46c7d536244f in branch rpi-4.7.y even from upstream
>> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+a45a35c085-r0 do_fetch: Fetcher failure for URL:
>> 'git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.7.y'. Unable to fetch URL from any source.
>> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+a45a35c085-r0 do_fetch: Function failed: base_do_fetch
>> ERROR: Logfile of failure stored in:
>> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+a45a35c085-r0/temp/log.do_fetch.6133
>> ERROR: Task (/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.7.bb:do_fetch) failed
>> with exit code '1'
>>
>> I was able to build with 4.8, but X didn't come up :-(
>>
>> Any ideas?
>>
>> Note: I changed the 4.7 recipe to use a good revision (c2cbd9c611)
>> but then I suffered the same problem installing the .dtbo patch :-(
>>
>
> It looks like the following oe-core commit broke the build for
> meta-raspberrypi:
>
> http://git.openembedded.org/openembedded-core/commit/?id=83d10e2acef936b1f38804988f10eafa48db36f9
>
> Applying the following patch from the oe-core mailing list fixes it for
> me:
>
> http://lists.openembedded.org/pipermail/openembedded-core/2016-December/129567.html
>
> I'm just going to apply that locally until it's merged into master.

Does the referenced patch by Paul fix your issue here?


--
Andrei Gherzan