Chromium-pi/2015 06 28

[[pagelist(^chromium-pi)]]

실험

배경

TBA

가설

arm-generic overlay가 armv7에 기반하며, armv6에 대한 대응이 없다.

검정

결과: 실패

overlay-raspberrypi 내용을 rpi2 프로세서 내용으로 바꿔서 빌드 시도했으나 실패 함.

``` raspberrypi-kernel-3.6-r3: >>> Configuring source in /build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/work/raspberrypi-kernel-3.6 ... raspberrypi-kernel-3.6-r3: * Using kernel config: /build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/work/raspberrypi-kernel-3.6/arch/arm/configs/bcmrpi_2_defconfig raspberrypi-kernel-3.6-r3: cp: cannot stat '/build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/work/raspberrypi-kernel-3.6/arch/arm/configs/bcmrpi_2_defconfig': No such file or directory raspberrypi-kernel-3.6-r3: * ERROR: sys-kernel/raspberrypi-kernel-3.6-r3::raspberrypi failed (configure phase): raspberrypi-kernel-3.6-r3: * (no error message) raspberrypi-kernel-3.6-r3: * raspberrypi-kernel-3.6-r3: * Call stack: raspberrypi-kernel-3.6-r3: * ebuild.sh, line 93: Called src_configure raspberrypi-kernel-3.6-r3: * environment, line 4786: Called cros-kernel2_src_configure raspberrypi-kernel-3.6-r3: * environment, line 1372: Called die raspberrypi-kernel-3.6-r3: * The specific snippet of code: raspberrypi-kernel-3.6-r3: * cp -f "${config}" "$(get_build_cfg)" || die; raspberrypi-kernel-3.6-r3: * raspberrypi-kernel-3.6-r3: * If you need support, post the output of `emerge --info '=sys-kernel/raspberrypi-kernel-3.6-r3::raspberrypi'`, raspberrypi-kernel-3.6-r3: * the complete build log and the output of `emerge -pqv '=sys-kernel/raspberrypi-kernel-3.6-r3::raspberrypi'`. raspberrypi-kernel-3.6-r3: * The complete build log is located at '/build/raspberrypi/tmp/portage/logs/sys-kernel:raspberrypi-kernel-3.6-r3:20150628-105058.log'. raspberrypi-kernel-3.6-r3: * For convenience, a symlink to the build log is located at '/build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/temp/build.log'. raspberrypi-kernel-3.6-r3: * The ebuild environment file is located at '/build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/temp/environment'. raspberrypi-kernel-3.6-r3: * Working directory: '/build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/work/raspberrypi-kernel-3.6' raspberrypi-kernel-3.6-r3: * S: '/build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/work/raspberrypi-kernel-3.6' raspberrypi-kernel-3.6-r3: >>> Failed to emerge sys-kernel/raspberrypi-kernel-3.6-r3 for /build/raspberrypi/, Log file: raspberrypi-kernel-3.6-r3: >>> '/build/raspberrypi/tmp/portage/logs/sys-kernel:raspberrypi-kernel-3.6-r3:20150628-105058.log' raspberrypi-kernel-3.6-r3: raspberrypi-kernel-3.6-r3: * Messages for package sys-kernel/raspberrypi-kernel-3.6-r3 merged to /build/raspberrypi/: raspberrypi-kernel-3.6-r3: raspberrypi-kernel-3.6-r3: * Using kernel config: /build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/work/raspberrypi-kernel-3.6/arch/arm/configs/bcmrpi_2_defconfig raspberrypi-kernel-3.6-r3: * ERROR: sys-kernel/raspberrypi-kernel-3.6-r3::raspberrypi failed (configure phase): raspberrypi-kernel-3.6-r3: * (no error message) raspberrypi-kernel-3.6-r3: * raspberrypi-kernel-3.6-r3: * Call stack: raspberrypi-kernel-3.6-r3: * ebuild.sh, line 93: Called src_configure raspberrypi-kernel-3.6-r3: * environment, line 4786: Called cros-kernel2_src_configure raspberrypi-kernel-3.6-r3: * environment, line 1372: Called die raspberrypi-kernel-3.6-r3: * The specific snippet of code: raspberrypi-kernel-3.6-r3: * cp -f "${config}" "$(get_build_cfg)" || die; raspberrypi-kernel-3.6-r3: * raspberrypi-kernel-3.6-r3: * If you need support, post the output of `emerge --info '=sys-kernel/raspberrypi-kernel-3.6-r3::raspberrypi'`, raspberrypi-kernel-3.6-r3: * the complete build log and the output of `emerge -pqv '=sys-kernel/raspberrypi-kernel-3.6-r3::raspberrypi'`. raspberrypi-kernel-3.6-r3: * The complete build log is located at '/build/raspberrypi/tmp/portage/logs/sys-kernel:raspberrypi-kernel-3.6-r3:20150628-105058.log'. raspberrypi-kernel-3.6-r3: * For convenience, a symlink to the build log is located at '/build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/temp/build.log'. raspberrypi-kernel-3.6-r3: * The ebuild environment file is located at '/build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/temp/environment'. raspberrypi-kernel-3.6-r3: * Working directory: '/build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/work/raspberrypi-kernel-3.6' raspberrypi-kernel-3.6-r3: * S: '/build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/work/raspberrypi-kernel-3.6'

Complete: job raspberrypi-kernel-3.6-r3 (0m24.9s)

Failed sys-kernel/raspberrypi-kernel-3.6-r3 (in 0m24.9s). Your build has failed. Pending 4/4, Time 0m53.5s Load 1.18 0.43 1.49 Packages failed:

       sys-kernel/raspberrypi-kernel-3.6-r3

```

Hint

/build/raspberrypi/tmp/portage/sys-kernel/raspberrypi-kernel-3.6-r3/work/raspberrypi-kernel-3.6/arch/arm/configs/bcmrpi_defconfig

/mnt/host/source/src/third_party/u-boot/files/configs/rpi_defconfig /mnt/host/source/src/third_party/u-boot/files/configs/rpi_2_defconfig