Newbie: building arm64-generic (actually, porting to a 64 bit ARM system)

251 views
Skip to first unread message

David Rusling

unread,
Aug 6, 2014, 9:51:25 AM8/6/14
to chromiu...@chromium.org
I'm new to Gentoo, let alone Chromium OS.  I'm trying to create an overlay for an ARMv8 board and using arm64-generic and veyron as guidelines.   My environment is set up and I can easily build arm-generic, but trying to build my platform or arm64-generic, I get "ERROR: no toolchain specified in board overlay or on command line"

My toolchain.conf references aarch64-cros-linux-gnu (strangely not gnueabi).   Any clues?

Many thanks, Dave

Mike Frysinger

unread,
Aug 6, 2014, 10:12:56 AM8/6/14
to David Rusling, chromium-os-dev
you have to use --nousepkg the first time you run setup_board

the toolchain tuple is correct -- aarch64 doesn't have an EABI, so using gnueabi would be strange
-mike


--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en


David Rusling

unread,
Aug 6, 2014, 11:53:30 AM8/6/14
to chromiu...@chromium.org, david....@linaro.org
I deleted and started from scratch - it produces the same error when run first time with --nousepkg

Mike Frysinger

unread,
Aug 6, 2014, 8:42:17 PM8/6/14
to David Rusling, chromium-os-dev
are you sure your board is in the right place ?  the conf is formatted correctly ?  you're running the right --board for the named overlay ?

i'd suggest starting small from a known working base and going from there.  this works for me:
$ cd ~/chromiumos/src/overlays/
$ cp -a overlay-arm64-generic overlay-foo
$ cros_sdk
$ ./setup_board --board=foo --nousepkg
-mike

David Rusling

unread,
Aug 7, 2014, 6:25:46 AM8/7/14
to chromiu...@chromium.org, david....@linaro.org
Mike,
   that gave me the clue I wanted.  it was the ./setup_board --board=foo rather than $export BOARD=foo that did it.   I'm catching my self out with Bash-isms.   That unblocked me for real work, so thanks...
Dave

Mike Frysinger

unread,
Aug 7, 2014, 8:06:43 AM8/7/14
to David Rusling, chromium-os-dev
our docs do commonly use examples of `export BOARD=foo`, but that's only so it can later do `./setup_board --board=$BOARD`.  you only need to modify the export line to be able to copy & paste the rest of the examples.  the actual existence of BOARD in the environment has no meaning to any of our tools.
-mike
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages