* [meta-raspberrypi] Current master broken
@ 2016-12-03 7:33 Gary Thomas
2016-12-03 14:16 ` Paul Barker
` (2 more replies)
0 siblings, 3 replies; 19+ messages in thread
From: Gary Thomas @ 2016-12-03 7:33 UTC (permalink / raw)
To: yocto@yoctoproject.org
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 :-(
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-03 7:33 [meta-raspberrypi] Current master broken Gary Thomas
@ 2016-12-03 14:16 ` Paul Barker
2016-12-05 0:54 ` Andrei Gherzan
2016-12-03 20:18 ` Herve Jourdain
2016-12-06 21:32 ` Trevor Woerner
2 siblings, 1 reply; 19+ messages in thread
From: Paul Barker @ 2016-12-03 14:16 UTC (permalink / raw)
To: Gary Thomas; +Cc: yocto@yoctoproject.org
On Sat, 3 Dec 2016 08:33:40 +0100
Gary Thomas <gary@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.
Thanks,
Paul Barker
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-03 7:33 [meta-raspberrypi] Current master broken Gary Thomas
2016-12-03 14:16 ` Paul Barker
@ 2016-12-03 20:18 ` Herve Jourdain
2016-12-06 21:32 ` Trevor Woerner
2 siblings, 0 replies; 19+ messages in thread
From: Herve Jourdain @ 2016-12-03 20:18 UTC (permalink / raw)
To: 'Gary Thomas', yocto
Hi Gary,
Regarding the 4.7, did you try the patch I sent 1 week ago?
It uses 4.7.10, with revision " e7fa325a40f260ed9fb86391a0b65150eba8c112",
and is known to work.
The "good" revision you mention is known to not be "good" anymore.
The patch can be found on the list, or on
https://github.com/hjourdain/meta-raspberrypi.
Hope it helps,
Herve
-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org]
On Behalf Of Gary Thomas
Sent: samedi 3 décembre 2016 08:34
To: yocto@yoctoproject.org
Subject: [yocto] [meta-raspberrypi] Current master broken
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-raspb
errypi/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-raspb
errypi/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/patc
| h.cmd: line 29: : No such file or directory
|
| Context around the error is:
|
| #
| prefix
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/
| kconf non-hardware
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/defconfig
| prefix
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi-4.4/
| patch
"/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspbe
rrypi-4.4/0001-fix-dtbo-rules.patch"
| # run time: 0 seconds
| # processed files:
| # _cfg
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/defconfig
| # _cfg
| /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-r
| aspberrypi-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/patc
| h.cmd: line 29: : No such file or directory
|
| Context around the error is:
|
| #
| prefix
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/
| kconf non-hardware
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/defconfig
| prefix
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi-4.4/
| patch
"/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspbe
rrypi-4.4/0001-fix-dtbo-rules.patch"
| # run time: 1 seconds
| # processed files:
| # _cfg
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/defconfig
| # _cfg
| /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-r
| aspberrypi-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-raspb
errypi/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-raspbe
rrypi_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-raspb
errypi/1_4.7.7+gitAUTOINC+a45a35c085-r0/temp/log.do_fetch.6133
ERROR: Task
(/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspbe
rrypi_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 :-(
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-03 14:16 ` Paul Barker
@ 2016-12-05 0:54 ` Andrei Gherzan
2016-12-05 6:03 ` Gary Thomas
0 siblings, 1 reply; 19+ messages in thread
From: Andrei Gherzan @ 2016-12-05 0:54 UTC (permalink / raw)
To: Paul Barker; +Cc: yocto@yoctoproject.org, Gary Thomas
Hi Gary,
On Sat, Dec 3, 2016 at 2:16 PM, Paul Barker <paul@paulbarker.me.uk> wrote:
> On Sat, 3 Dec 2016 08:33:40 +0100
> Gary Thomas <gary@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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-05 0:54 ` Andrei Gherzan
@ 2016-12-05 6:03 ` Gary Thomas
2016-12-05 16:50 ` Khem Raj
0 siblings, 1 reply; 19+ messages in thread
From: Gary Thomas @ 2016-12-05 6:03 UTC (permalink / raw)
To: Andrei Gherzan, Paul Barker; +Cc: yocto@yoctoproject.org
On 2016-12-05 01:54, Andrei Gherzan wrote:
> Hi Gary,
>
>
> On Sat, Dec 3, 2016 at 2:16 PM, Paul Barker <paul@paulbarker.me.uk> wrote:
>> On Sat, 3 Dec 2016 08:33:40 +0100
>> Gary Thomas <gary@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?
Yes, for version 4.4.x
When I tried to build 4.7.x, I got these errors:
ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0 do_kernel_version_sanity_check: Package Version
(4.7.7+gitAUTOINC+c2cbd9c611) does not match of kernel being built (4.7.10). Please update the PV variable to match the
kernel source.
ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0 do_kernel_version_sanity_check: Function failed:
do_kernel_version_sanity_check (log file is located at
/build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_check.2574)
ERROR: Logfile of failure stored in:
/build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_check.2574
ERROR: Task
(/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.7.bb:do_kernel_version_sanity_check)
failed with exit code '1'
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-05 6:03 ` Gary Thomas
@ 2016-12-05 16:50 ` Khem Raj
2016-12-06 15:29 ` Andrei Gherzan
0 siblings, 1 reply; 19+ messages in thread
From: Khem Raj @ 2016-12-05 16:50 UTC (permalink / raw)
To: Gary Thomas; +Cc: yocto@yoctoproject.org
On Sun, Dec 4, 2016 at 10:03 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> On 2016-12-05 01:54, Andrei Gherzan wrote:
>>
>> Hi Gary,
>>
>>
>> On Sat, Dec 3, 2016 at 2:16 PM, Paul Barker <paul@paulbarker.me.uk> wrote:
>>>
>>> On Sat, 3 Dec 2016 08:33:40 +0100
>>> Gary Thomas <gary@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?
>
>
> Yes, for version 4.4.x
>
> When I tried to build 4.7.x, I got these errors:
>
> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
> do_kernel_version_sanity_check: Package Version
> (4.7.7+gitAUTOINC+c2cbd9c611) does not match of kernel being built (4.7.10).
> Please update the PV variable to match the kernel source.
> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
> do_kernel_version_sanity_check: Function failed:
> do_kernel_version_sanity_check (log file is located at
> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_check.2574)
> ERROR: Logfile of failure stored in:
> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_check.2574
> ERROR: Task
> (/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.7.bb:do_kernel_version_sanity_check)
> failed with exit code '1'
Yeah there are changes in OE-Core master to catch kernel verison
mismatches now and moreover rpi folks rebase the trees except 4.1 and
4.4 none of recipes may hold
true with SRCREV after sometime, we should bring this to notice of rpi
community if they could instead do merges instead of rebasing the
trees we can keep those recipes
locked to a given version, otherwise we are forced to move them as
soon as the rebase is detected.
>
> --
> ------------------------------------------------------------
> Gary Thomas | Consulting for the
> MLB Associates | Embedded world
> ------------------------------------------------------------
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-05 16:50 ` Khem Raj
@ 2016-12-06 15:29 ` Andrei Gherzan
2016-12-06 18:04 ` ***SPAM*** " Herve Jourdain
` (2 more replies)
0 siblings, 3 replies; 19+ messages in thread
From: Andrei Gherzan @ 2016-12-06 15:29 UTC (permalink / raw)
To: Khem Raj; +Cc: yocto@yoctoproject.org, Gary Thomas
On Mon, Dec 5, 2016 at 4:50 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Sun, Dec 4, 2016 at 10:03 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> On 2016-12-05 01:54, Andrei Gherzan wrote:
>>>
>>> Hi Gary,
>>>
>>>
>>> On Sat, Dec 3, 2016 at 2:16 PM, Paul Barker <paul@paulbarker.me.uk> wrote:
>>>>
>>>> On Sat, 3 Dec 2016 08:33:40 +0100
>>>> Gary Thomas <gary@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?
>>
>>
>> Yes, for version 4.4.x
>>
>> When I tried to build 4.7.x, I got these errors:
>>
>> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
>> do_kernel_version_sanity_check: Package Version
>> (4.7.7+gitAUTOINC+c2cbd9c611) does not match of kernel being built (4.7.10).
>> Please update the PV variable to match the kernel source.
>> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
>> do_kernel_version_sanity_check: Function failed:
>> do_kernel_version_sanity_check (log file is located at
>> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_check.2574)
>> ERROR: Logfile of failure stored in:
>> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_check.2574
>> ERROR: Task
>> (/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.7.bb:do_kernel_version_sanity_check)
>> failed with exit code '1'
>
> Yeah there are changes in OE-Core master to catch kernel verison
> mismatches now and moreover rpi folks rebase the trees except 4.1 and
> 4.4 none of recipes may hold
> true with SRCREV after sometime, we should bring this to notice of rpi
> community if they could instead do merges instead of rebasing the
> trees we can keep those recipes
> locked to a given version, otherwise we are forced to move them as
> soon as the rebase is detected.
I managed to hit this too. @Paul Is that patch coming to oe-core master soon?
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: ***SPAM*** Re: [meta-raspberrypi] Current master broken
2016-12-06 15:29 ` Andrei Gherzan
@ 2016-12-06 18:04 ` Herve Jourdain
2016-12-06 18:11 ` Andrei Gherzan
2016-12-06 22:50 ` Paul Barker
2016-12-07 15:19 ` Andrea Galbusera
2 siblings, 1 reply; 19+ messages in thread
From: Herve Jourdain @ 2016-12-06 18:04 UTC (permalink / raw)
To: 'Andrei Gherzan', 'Khem Raj'; +Cc: yocto, 'Gary Thomas'
Hi Andrei,
But I believe that the core of the problem is not necessarily the patch in
oe-core to detect the kernel version itself, but like Khem mentioned the
fact that a "well known" SRCREV is only valid for a brief period of time
under the RPI tree "constant" rebasing we've been experiencing lately.
So basically, the SRCREV that is used is not corresponding to what it used
to be, if it's still there in the tree, and the oe-core detects that - the
SRCREV thought it was one version of the kernel, and it just happened that
it corresponds to a different codebase with a different linux version.
Killing the error reporting by a patch will probably not prevent the
mismatch happening behind the scene.
So like Khem mentioned, either we find a way to "prevent" the rebasing at
the source, or we need to track down every version we want to support, and
update SRCREV and corresponding kernel version for those.
Cheers,
Herve
-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org]
On Behalf Of Andrei Gherzan
Sent: mardi 6 décembre 2016 16:29
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@yoctoproject.org; Gary Thomas <gary@mlbassoc.com>
Subject: ***SPAM*** Re: [yocto] [meta-raspberrypi] Current master broken
On Mon, Dec 5, 2016 at 4:50 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Sun, Dec 4, 2016 at 10:03 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> On 2016-12-05 01:54, Andrei Gherzan wrote:
>>>
>>> Hi Gary,
>>>
>>>
>>> On Sat, Dec 3, 2016 at 2:16 PM, Paul Barker <paul@paulbarker.me.uk>
wrote:
>>>>
>>>> On Sat, 3 Dec 2016 08:33:40 +0100
>>>> Gary Thomas <gary@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/l
>>>>> inux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_ker
>>>>> nel_metadata.5647)
>>>>> ERROR: Logfile of failure stored in:
>>>>>
>>>>> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/l
>>>>> inux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_ker
>>>>> nel_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/lin
>>>>> ux-raspberrypi/
>>>>> | kconf non-hardware
>>>>> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
>>>>> ux-raspberrypi/defconfig
>>>>> | prefix
>>>>> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
>>>>> ux-raspberrypi-4.4/
>>>>> | patch
>>>>>
"/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspbe
rrypi-4.4/0001-fix-dtbo-rules.patch"
>>>>> | # run time: 0 seconds
>>>>> | # processed files:
>>>>> | # _cfg
>>>>> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
>>>>> ux-raspberrypi/defconfig
>>>>> | # _cfg
>>>>> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
>>>>> ux-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/lin
>>>>> ux-raspberrypi/
>>>>> | kconf non-hardware
>>>>> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
>>>>> ux-raspberrypi/defconfig
>>>>> | prefix
>>>>> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
>>>>> ux-raspberrypi-4.4/
>>>>> | patch
>>>>>
"/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspbe
rrypi-4.4/0001-fix-dtbo-rules.patch"
>>>>> | # run time: 1 seconds
>>>>> | # processed files:
>>>>> | # _cfg
>>>>> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
>>>>> ux-raspberrypi/defconfig
>>>>> | # _cfg
>>>>> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
>>>>> ux-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/l
>>>>> inux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_ker
>>>>> nel_metadata.5647)
>>>>> ERROR: Task
>>>>> (/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/li
>>>>> nux-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/l
>>>>> inux-raspberrypi/1_4.7.7+gitAUTOINC+a45a35c085-r0/temp/log.do_fetc
>>>>> h.6133
>>>>> ERROR: Task
>>>>> (/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/li
>>>>> nux-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=83d10e2ace
>>>> f936b1f38804988f10eafa48db36f9
>>>>
>>>> Applying the following patch from the oe-core mailing list fixes it
>>>> for
>>>> me:
>>>>
>>>>
>>>> http://lists.openembedded.org/pipermail/openembedded-core/2016-Dece
>>>> mber/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?
>>
>>
>> Yes, for version 4.4.x
>>
>> When I tried to build 4.7.x, I got these errors:
>>
>> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
>> do_kernel_version_sanity_check: Package Version
>> (4.7.7+gitAUTOINC+c2cbd9c611) does not match of kernel being built
(4.7.10).
>> Please update the PV variable to match the kernel source.
>> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
>> do_kernel_version_sanity_check: Function failed:
>> do_kernel_version_sanity_check (log file is located at
>> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linu
>> x-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_ver
>> sion_sanity_check.2574)
>> ERROR: Logfile of failure stored in:
>> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linu
>> x-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_ver
>> sion_sanity_check.2574
>> ERROR: Task
>> (/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux
>> -raspberrypi_4.7.bb:do_kernel_version_sanity_check)
>> failed with exit code '1'
>
> Yeah there are changes in OE-Core master to catch kernel verison
> mismatches now and moreover rpi folks rebase the trees except 4.1 and
> 4.4 none of recipes may hold
> true with SRCREV after sometime, we should bring this to notice of rpi
> community if they could instead do merges instead of rebasing the
> trees we can keep those recipes locked to a given version, otherwise
> we are forced to move them as soon as the rebase is detected.
I managed to hit this too. @Paul Is that patch coming to oe-core master
soon?
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: ***SPAM*** Re: [meta-raspberrypi] Current master broken
2016-12-06 18:04 ` ***SPAM*** " Herve Jourdain
@ 2016-12-06 18:11 ` Andrei Gherzan
2016-12-06 21:21 ` Herve Jourdain
0 siblings, 1 reply; 19+ messages in thread
From: Andrei Gherzan @ 2016-12-06 18:11 UTC (permalink / raw)
To: Herve Jourdain; +Cc: yocto, 'Gary Thomas'
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
On Tue, Dec 06, 2016 at 07:04:31PM +0100, Herve Jourdain wrote:
> Hi Andrei,
>
> But I believe that the core of the problem is not necessarily the patch in
> oe-core to detect the kernel version itself, but like Khem mentioned the
> fact that a "well known" SRCREV is only valid for a brief period of time
> under the RPI tree "constant" rebasing we've been experiencing lately.
> So basically, the SRCREV that is used is not corresponding to what it used
> to be, if it's still there in the tree, and the oe-core detects that - the
> SRCREV thought it was one version of the kernel, and it just happened that
> it corresponds to a different codebase with a different linux version.
> Killing the error reporting by a patch will probably not prevent the
> mismatch happening behind the scene.
> So like Khem mentioned, either we find a way to "prevent" the rebasing at
> the source, or we need to track down every version we want to support, and
> update SRCREV and corresponding kernel version for those.
Got it now. What do you mean by "track down every version we want"?
--
Andrei Gherzan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 817 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: ***SPAM*** Re: [meta-raspberrypi] Current master broken
2016-12-06 18:11 ` Andrei Gherzan
@ 2016-12-06 21:21 ` Herve Jourdain
2016-12-06 23:00 ` Paul Barker
0 siblings, 1 reply; 19+ messages in thread
From: Herve Jourdain @ 2016-12-06 21:21 UTC (permalink / raw)
To: 'Andrei Gherzan'; +Cc: yocto, 'Gary Thomas'
Sorry, a bit tired...
I meant we need to track the changes happening to the versions we decide we
want to support, and update the recipes accordingly.
My understanding is we're interested in 4.4, 4.8 and 4.9. And I have a
personal interest in 4.7 for the moment, so I can try to keep the 4.7 recipe
up to date with the changes.
If 4.4 is "stable", then we need some people to focus on tracking the
changes happening on 4.8 and 4.9.
Cheers,
Herve
-----Original Message-----
From: Andrei Gherzan [mailto:andrei@gherzan.ro]
Sent: mardi 6 décembre 2016 19:11
To: Herve Jourdain <herve.jourdain@neuf.fr>
Cc: 'Khem Raj' <raj.khem@gmail.com>; yocto@yoctoproject.org; 'Gary Thomas'
<gary@mlbassoc.com>
Subject: Re: ***SPAM*** Re: [yocto] [meta-raspberrypi] Current master broken
On Tue, Dec 06, 2016 at 07:04:31PM +0100, Herve Jourdain wrote:
> Hi Andrei,
>
> But I believe that the core of the problem is not necessarily the
> patch in oe-core to detect the kernel version itself, but like Khem
> mentioned the fact that a "well known" SRCREV is only valid for a
> brief period of time under the RPI tree "constant" rebasing we've been
experiencing lately.
> So basically, the SRCREV that is used is not corresponding to what it
> used to be, if it's still there in the tree, and the oe-core detects
> that - the SRCREV thought it was one version of the kernel, and it
> just happened that it corresponds to a different codebase with a different
linux version.
> Killing the error reporting by a patch will probably not prevent the
> mismatch happening behind the scene.
> So like Khem mentioned, either we find a way to "prevent" the rebasing
> at the source, or we need to track down every version we want to
> support, and update SRCREV and corresponding kernel version for those.
Got it now. What do you mean by "track down every version we want"?
--
Andrei Gherzan
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-03 7:33 [meta-raspberrypi] Current master broken Gary Thomas
2016-12-03 14:16 ` Paul Barker
2016-12-03 20:18 ` Herve Jourdain
@ 2016-12-06 21:32 ` Trevor Woerner
2 siblings, 0 replies; 19+ messages in thread
From: Trevor Woerner @ 2016-12-06 21:32 UTC (permalink / raw)
To: Gary Thomas; +Cc: yocto@yoctoproject.org
Just to clarify, in the last couple days, there have been *two* major issues
that have independently broken raspi builds:
1) the rebase of the raspi kernel repository at
git://github.com/raspberrypi/linux.git
2) a bug in a recent commit to oe-core's kernel tools
Andrei pushed patches today to update the src revs so, as of this moment, the
SRC_URIs in meta-raspberrypi should be valid.
A patch for the kernel tools in oe-core is on the mailing list; hopefully it
will be pushed to master soon. Incidentally, this same bad commit also
included a second bug that made it impossible for two different users on the
same machine to perform OE builds. The fix addresses both issues.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-06 15:29 ` Andrei Gherzan
2016-12-06 18:04 ` ***SPAM*** " Herve Jourdain
@ 2016-12-06 22:50 ` Paul Barker
2016-12-07 15:19 ` Andrea Galbusera
2 siblings, 0 replies; 19+ messages in thread
From: Paul Barker @ 2016-12-06 22:50 UTC (permalink / raw)
To: Andrei Gherzan; +Cc: yocto@yoctoproject.org, Gary Thomas
On Tue, 6 Dec 2016 15:29:02 +0000
Andrei Gherzan <andrei@gherzan.ro> wrote:
> On Mon, Dec 5, 2016 at 4:50 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > On Sun, Dec 4, 2016 at 10:03 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> >> On 2016-12-05 01:54, Andrei Gherzan wrote:
> >>>
> >>> Hi Gary,
> >>>
> >>>
> >>> On Sat, Dec 3, 2016 at 2:16 PM, Paul Barker <paul@paulbarker.me.uk> wrote:
> >>>>
> >>>>
> >>>> 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?
> >>
> >>
> >> Yes, for version 4.4.x
> >>
>
> I managed to hit this too. @Paul Is that patch coming to oe-core master soon?
I'll let people know on the oe-core list that we need this. I'd imagine
it won't be stuck in the queue for long but depends how busy things
are I suppose.
Thanks,
Paul
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: ***SPAM*** Re: [meta-raspberrypi] Current master broken
2016-12-06 21:21 ` Herve Jourdain
@ 2016-12-06 23:00 ` Paul Barker
2016-12-07 2:17 ` Trevor Woerner
0 siblings, 1 reply; 19+ messages in thread
From: Paul Barker @ 2016-12-06 23:00 UTC (permalink / raw)
To: Herve Jourdain; +Cc: yocto, 'Gary Thomas'
On Tue, 6 Dec 2016 22:21:50 +0100
Herve Jourdain <herve.jourdain@neuf.fr> wrote:
> Sorry, a bit tired...
> I meant we need to track the changes happening to the versions we decide we
> want to support, and update the recipes accordingly.
> My understanding is we're interested in 4.4, 4.8 and 4.9. And I have a
> personal interest in 4.7 for the moment, so I can try to keep the 4.7 recipe
> up to date with the changes.
> If 4.4 is "stable", then we need some people to focus on tracking the
> changes happening on 4.8 and 4.9.
>
> Cheers,
> Herve
>
I've ran into this myself before.
Upstream effectively support one version, currently 4.4. When upstream
made that the default branch, the changes to the 4.1 branch stopped -
there wasn't really much overlap. Everything post-4.4 is active
development and gets rebased at will. At some point they'll move to the
next LTS release (4.9) and 4.4 will be dropped.
I'd class all recipes for kernel versions other than default branch
upstream as experimental. Perhaps we should just go with AUTOREV here?
Anything else is going to need changing really often.
Thanks,
Paul
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: ***SPAM*** Re: [meta-raspberrypi] Current master broken
2016-12-06 23:00 ` Paul Barker
@ 2016-12-07 2:17 ` Trevor Woerner
2016-12-07 7:25 ` Paul Barker
0 siblings, 1 reply; 19+ messages in thread
From: Trevor Woerner @ 2016-12-07 2:17 UTC (permalink / raw)
To: Paul Barker; +Cc: yocto, 'Gary Thomas'
On Tue 2016-12-06 @ 11:00:34 PM, Paul Barker wrote:
> Upstream effectively support one version, currently 4.4. When upstream
> made that the default branch, the changes to the 4.1 branch stopped -
> there wasn't really much overlap. Everything post-4.4 is active
> development and gets rebased at will. At some point they'll move to the
> next LTS release (4.9) and 4.4 will be dropped.
Are you speaking specifically about the kernel for raspberry pi, or in
general? Because the kernel for raspberry pi has several branches that are all
maintained and kept up-to-date. It's actually quite commendable how this
repository is maintained. Branches for 4.4, 4.7, 4.8, 4.9 and others are all
usable (ignoring the constant rebasing thing...)
> I'd class all recipes for kernel versions other than default branch
> upstream as experimental. Perhaps we should just go with AUTOREV here?
> Anything else is going to need changing really often.
Not every revision of those branches are usable for raspberry pi. Someone
named "popcornmix" has been keeping everything aligned with upstream, and
merging in the support for raspberry pi.
If you took the rpi-4.8.y branch, for example, and happened to check out
commit 356ccf6d2b0cfe9dca6c5d961bfd04dc8c0f4e64, you wouldn't have something
that would build.
The problem is they keep rebasing, which messes up the SRC_URIs :-(
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-07 2:17 ` Trevor Woerner
@ 2016-12-07 7:25 ` Paul Barker
2016-12-07 7:42 ` Paul Barker
0 siblings, 1 reply; 19+ messages in thread
From: Paul Barker @ 2016-12-07 7:25 UTC (permalink / raw)
To: Trevor Woerner; +Cc: yocto, 'Gary Thomas'
On Tue, 6 Dec 2016 21:17:55 -0500
Trevor Woerner <twoerner@gmail.com> wrote:
> On Tue 2016-12-06 @ 11:00:34 PM, Paul Barker wrote:
> > Upstream effectively support one version, currently 4.4. When upstream
> > made that the default branch, the changes to the 4.1 branch stopped -
> > there wasn't really much overlap. Everything post-4.4 is active
> > development and gets rebased at will. At some point they'll move to the
> > next LTS release (4.9) and 4.4 will be dropped.
>
> Are you speaking specifically about the kernel for raspberry pi, or in
> general?
Raspberrypi specifically.
> Because the kernel for raspberry pi has several branches that are all
> maintained and kept up-to-date. It's actually quite commendable how this
> repository is maintained. Branches for 4.4, 4.7, 4.8, 4.9 and others are all
> usable (ignoring the constant rebasing thing...)
4.4 is stable and never gets rebased.
4.7 was last updated Oct 25th so it's now inactive.
4.8 and 4.9 will be almost the same set of patches rebased on top of
the mainline kernel. I think they do things this way to make
upstreaming patches easier.
This is the pattern I've seen for the last couple of years - one stable
branch that never gets rebased and one or two development branches
which do get rebased.
>
> > I'd class all recipes for kernel versions other than default branch
> > upstream as experimental. Perhaps we should just go with AUTOREV here?
> > Anything else is going to need changing really often.
>
> Not every revision of those branches are usable for raspberry pi. Someone
> named "popcornmix" has been keeping everything aligned with upstream, and
> merging in the support for raspberry pi.
>
> If you took the rpi-4.8.y branch, for example, and happened to check out
> commit 356ccf6d2b0cfe9dca6c5d961bfd04dc8c0f4e64, you wouldn't have something
> that would build.
>
> The problem is they keep rebasing, which messes up the SRC_URIs :-(
This is true, AUTOREV would lead to occasionally picking up bad
commits.
How about mirroring the Raspberrypi Linux repository so that we can
control when certain commits disappear from the repository? We could
either have AUTOREV in the recipe and only update the mirror with
tested commits, or update meta-raspberrypi regularly as well.
Thanks,
Paul
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-07 7:25 ` Paul Barker
@ 2016-12-07 7:42 ` Paul Barker
2016-12-07 10:54 ` Andreas Müller
0 siblings, 1 reply; 19+ messages in thread
From: Paul Barker @ 2016-12-07 7:42 UTC (permalink / raw)
To: Trevor Woerner; +Cc: yocto, 'Gary Thomas'
On Wed, 7 Dec 2016 07:25:23 +0000
Paul Barker <paul@paulbarker.me.uk> wrote:
> On Tue, 6 Dec 2016 21:17:55 -0500
> Trevor Woerner <twoerner@gmail.com> wrote:
>
> > On Tue 2016-12-06 @ 11:00:34 PM, Paul Barker wrote:
> > > Upstream effectively support one version, currently 4.4. When upstream
> > > made that the default branch, the changes to the 4.1 branch stopped -
> > > there wasn't really much overlap. Everything post-4.4 is active
> > > development and gets rebased at will. At some point they'll move to the
> > > next LTS release (4.9) and 4.4 will be dropped.
> >
> > Are you speaking specifically about the kernel for raspberry pi, or in
> > general?
>
> Raspberrypi specifically.
>
> > Because the kernel for raspberry pi has several branches that are all
> > maintained and kept up-to-date. It's actually quite commendable how this
> > repository is maintained. Branches for 4.4, 4.7, 4.8, 4.9 and others are all
> > usable (ignoring the constant rebasing thing...)
>
> 4.4 is stable and never gets rebased.
>
> 4.7 was last updated Oct 25th so it's now inactive.
>
> 4.8 and 4.9 will be almost the same set of patches rebased on top of
> the mainline kernel. I think they do things this way to make
> upstreaming patches easier.
>
> This is the pattern I've seen for the last couple of years - one stable
> branch that never gets rebased and one or two development branches
> which do get rebased.
>
Sorry, quick follow up.
https://github.com/raspberrypi/linux/issues/1650 is a typical response from
the Raspberrypi folks about this:
Future rpi- branches (branches that aren't yet the main development
branch, currently rpi-4.4.y) are rebased against upstream commits.
Once we start making releases from a branch we stop rebasing and
start merging.
The commit you refer to still exists but with a different commit
ID. You need to tell whoever gave you the hash that bookmarking
commits in our future branches is futile because they are regularly
rebased.
Thanks,
Paul
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-07 7:42 ` Paul Barker
@ 2016-12-07 10:54 ` Andreas Müller
0 siblings, 0 replies; 19+ messages in thread
From: Andreas Müller @ 2016-12-07 10:54 UTC (permalink / raw)
To: Paul Barker; +Cc: Yocto Project, Gary Thomas
On Wed, Dec 7, 2016 at 8:42 AM, Paul Barker <paul@paulbarker.me.uk> wrote:
> On Wed, 7 Dec 2016 07:25:23 +0000
> Paul Barker <paul@paulbarker.me.uk> wrote:
>
>> On Tue, 6 Dec 2016 21:17:55 -0500
>> Trevor Woerner <twoerner@gmail.com> wrote:
>>
>> > On Tue 2016-12-06 @ 11:00:34 PM, Paul Barker wrote:
>> > > Upstream effectively support one version, currently 4.4. When upstream
>> > > made that the default branch, the changes to the 4.1 branch stopped -
>> > > there wasn't really much overlap. Everything post-4.4 is active
>> > > development and gets rebased at will. At some point they'll move to the
>> > > next LTS release (4.9) and 4.4 will be dropped.
>> >
>> > Are you speaking specifically about the kernel for raspberry pi, or in
>> > general?
>>
>> Raspberrypi specifically.
>>
>> > Because the kernel for raspberry pi has several branches that are all
>> > maintained and kept up-to-date. It's actually quite commendable how this
>> > repository is maintained. Branches for 4.4, 4.7, 4.8, 4.9 and others are all
>> > usable (ignoring the constant rebasing thing...)
>>
>> 4.4 is stable and never gets rebased.
>>
FWIW: patch fixing 4.4 just arrived in oe-core
Andreas
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-06 15:29 ` Andrei Gherzan
2016-12-06 18:04 ` ***SPAM*** " Herve Jourdain
2016-12-06 22:50 ` Paul Barker
@ 2016-12-07 15:19 ` Andrea Galbusera
2016-12-07 15:23 ` Andrei Gherzan
2 siblings, 1 reply; 19+ messages in thread
From: Andrea Galbusera @ 2016-12-07 15:19 UTC (permalink / raw)
To: Andrei Gherzan; +Cc: yocto@yoctoproject.org, Gary Thomas
[-- Attachment #1: Type: text/plain, Size: 9720 bytes --]
On Tue, Dec 6, 2016 at 4:29 PM, Andrei Gherzan <andrei@gherzan.ro> wrote:
> On Mon, Dec 5, 2016 at 4:50 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > On Sun, Dec 4, 2016 at 10:03 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> >> On 2016-12-05 01:54, Andrei Gherzan wrote:
> >>>
> >>> Hi Gary,
> >>>
> >>>
> >>> On Sat, Dec 3, 2016 at 2:16 PM, Paul Barker <paul@paulbarker.me.uk>
> wrote:
> >>>>
> >>>> On Sat, 3 Dec 2016 08:33:40 +0100
> >>>> Gary Thomas <gary@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:9e63f81c78e284c9b325fe04a1b59e
> 61c7ad8a1a"
> >>>>> meta-amltd = "master:074120ab3a82cea0ac50d4e9eec891
> 30a860a4fa"
> >>>>> meta-raspberrypi = "master:44d41bf3e94c4c8fe5ad5a3650572c
> 8d17ef36c9"
> >>>>>
> >>>>> 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?
> >>
> >>
> >> Yes, for version 4.4.x
> >>
> >> When I tried to build 4.7.x, I got these errors:
> >>
> >> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
> >> do_kernel_version_sanity_check: Package Version
> >> (4.7.7+gitAUTOINC+c2cbd9c611) does not match of kernel being built
> (4.7.10).
> >> Please update the PV variable to match the kernel source.
> >> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
> >> do_kernel_version_sanity_check: Function failed:
> >> do_kernel_version_sanity_check (log file is located at
> >> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-
> gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/
> temp/log.do_kernel_version_sanity_check.2574)
> >> ERROR: Logfile of failure stored in:
> >> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-
> gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/
> temp/log.do_kernel_version_sanity_check.2574
> >> ERROR: Task
> >> (/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-
> raspberrypi_4.7.bb:do_kernel_version_sanity_check)
> >> failed with exit code '1'
> >
> > Yeah there are changes in OE-Core master to catch kernel verison
> > mismatches now and moreover rpi folks rebase the trees except 4.1 and
> > 4.4 none of recipes may hold
> > true with SRCREV after sometime, we should bring this to notice of rpi
> > community if they could instead do merges instead of rebasing the
> > trees we can keep those recipes
> > locked to a given version, otherwise we are forced to move them as
> > soon as the rebase is detected.
>
> I managed to hit this too. @Paul Is that patch coming to oe-core master
> soon?
>
It just landed in oe-core as commit 0fd7da7375f0dcc59b56791fd482de557507c04c
a few hours ago and in yocto too as
commit 80683aa4f8c01b1fab430554838906d3d4aeda10. FYI, without this fix,
also kernel builds of other BSP layers like meta-altera were broken...
those are back to green light now.
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
[-- Attachment #2: Type: text/html, Size: 14491 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [meta-raspberrypi] Current master broken
2016-12-07 15:19 ` Andrea Galbusera
@ 2016-12-07 15:23 ` Andrei Gherzan
0 siblings, 0 replies; 19+ messages in thread
From: Andrei Gherzan @ 2016-12-07 15:23 UTC (permalink / raw)
To: Andrea Galbusera; +Cc: yocto@yoctoproject.org, Gary Thomas
On Wed, Dec 7, 2016 at 3:19 PM, Andrea Galbusera <gizero@gmail.com> wrote:
> On Tue, Dec 6, 2016 at 4:29 PM, Andrei Gherzan <andrei@gherzan.ro> wrote:
>>
>> On Mon, Dec 5, 2016 at 4:50 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> > On Sun, Dec 4, 2016 at 10:03 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> >> On 2016-12-05 01:54, Andrei Gherzan wrote:
>> >>>
>> >>> Hi Gary,
>> >>>
>> >>>
>> >>> On Sat, Dec 3, 2016 at 2:16 PM, Paul Barker <paul@paulbarker.me.uk>
>> >>> wrote:
>> >>>>
>> >>>> On Sat, 3 Dec 2016 08:33:40 +0100
>> >>>> Gary Thomas <gary@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?
>> >>
>> >>
>> >> Yes, for version 4.4.x
>> >>
>> >> When I tried to build 4.7.x, I got these errors:
>> >>
>> >> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
>> >> do_kernel_version_sanity_check: Package Version
>> >> (4.7.7+gitAUTOINC+c2cbd9c611) does not match of kernel being built
>> >> (4.7.10).
>> >> Please update the PV variable to match the kernel source.
>> >> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
>> >> do_kernel_version_sanity_check: Function failed:
>> >> do_kernel_version_sanity_check (log file is located at
>> >>
>> >> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_check.2574)
>> >> ERROR: Logfile of failure stored in:
>> >>
>> >> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_check.2574
>> >> ERROR: Task
>> >>
>> >> (/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.7.bb:do_kernel_version_sanity_check)
>> >> failed with exit code '1'
>> >
>> > Yeah there are changes in OE-Core master to catch kernel verison
>> > mismatches now and moreover rpi folks rebase the trees except 4.1 and
>> > 4.4 none of recipes may hold
>> > true with SRCREV after sometime, we should bring this to notice of rpi
>> > community if they could instead do merges instead of rebasing the
>> > trees we can keep those recipes
>> > locked to a given version, otherwise we are forced to move them as
>> > soon as the rebase is detected.
>>
>> I managed to hit this too. @Paul Is that patch coming to oe-core master
>> soon?
>
>
> It just landed in oe-core as commit
> 0fd7da7375f0dcc59b56791fd482de557507c04c a few hours ago and in yocto too as
> commit 80683aa4f8c01b1fab430554838906d3d4aeda10. FYI, without this fix, also
> kernel builds of other BSP layers like meta-altera were broken... those are
> back to green light now.
Happy days.
--
Andrei Gherzan
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2016-12-07 15:23 UTC | newest]
Thread overview: 19+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-12-03 7:33 [meta-raspberrypi] Current master broken Gary Thomas
2016-12-03 14:16 ` Paul Barker
2016-12-05 0:54 ` Andrei Gherzan
2016-12-05 6:03 ` Gary Thomas
2016-12-05 16:50 ` Khem Raj
2016-12-06 15:29 ` Andrei Gherzan
2016-12-06 18:04 ` ***SPAM*** " Herve Jourdain
2016-12-06 18:11 ` Andrei Gherzan
2016-12-06 21:21 ` Herve Jourdain
2016-12-06 23:00 ` Paul Barker
2016-12-07 2:17 ` Trevor Woerner
2016-12-07 7:25 ` Paul Barker
2016-12-07 7:42 ` Paul Barker
2016-12-07 10:54 ` Andreas Müller
2016-12-06 22:50 ` Paul Barker
2016-12-07 15:19 ` Andrea Galbusera
2016-12-07 15:23 ` Andrei Gherzan
2016-12-03 20:18 ` Herve Jourdain
2016-12-06 21:32 ` Trevor Woerner
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.