R69 didn't build for --board=raspberrypi

[Jeremy Shute]

I'm having trouble following the quick start instructions on release-R69-10895.B. Issuing 'cros_sdk -- ./setup_board --force --board=raspberrypi' fails to compile a simple test program. Command line output is available here:

https://gist.github.com/shutej/6f73e6daf12fbf5fde31d311652c2a0a

I've excerpted it in the hope that I'm missing something obvious...

FAILED: cmTC_6bfb9

: && /usr/bin/armv6j-cros-linux-gnueabi-clang -O2 -O2 -pipe -march=armv6zk
-mtune=arm1176jzf-s -mfloat-abi=hard -mfpu=vfp -g -mfpu=vfpv3
-I/build/raspberrypi/tmp/portage/sys-libs/libcxxabi-4.0.0-r35/work/libcxxabi-4.0.0.src/libunwind_llvm/include
-stdlib=libstdc++ -Wl,-O1 -Wl,-O2 -Wl,--as-needed
CMakeFiles/cmTC_6bfb9.dir/testCCompiler.c.o -o cmTC_6bfb9 && :


/usr/x86_64-pc-linux-gnu/armv6j-cros-linux-gnueabi/binutils-bin/2.27.0/ld.gold.real:
error: cannot open
/usr/lib64/clang/7.0.0/lib/linux/libclang_rt.builtins-armhf.a: No such file
or directory


/usr/x86_64-pc-linux-gnu/armv6j-cros-linux-gnueabi/binutils-bin/2.27.0/ld.gold.real:
error: cannot open
/usr/lib64/clang/7.0.0/lib/linux/libclang_rt.builtins-armhf.a: No such file
or directory

clang-7: error: linker command failed with exit code 1 (use -v to see
invocation)

[Alpha Tang]

Jeremy,

The overlay-raspberrypi you have been using was written for early generations of Raspberry Pi model with BCM2835 (ARMv6) SoC, there is little support for the armv6j toolchain in cros_sdk. As discussed in earlier threads, it not likely to get any more support.

If you are looking to run Chromium OS for newer generation of the Raspberry Pi 3B, you may try our WIP overlay here.

Best

Alpha

--
--
Chromium OS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss
---
You received this message because you are subscribed to the Google Groups "Chromium OS Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-dis...@chromium.org.