New issue
Advanced search Search tips

Issue 923659 link

Starred by 0 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Task
Build-Toolchain



Sign in to add a comment

rename i686-pc-linux-gnu toolchain to i686-cros-linux-gnu

Project Member Reported by vapier@chromium.org, Jan 19 (3 days ago)

Issue description

using "i686-pc-linux-gnu" as our 32-bit cross-compiler runs into conflicts on systems where "i686-pc-linux-gnu" is the native toolchain.  we've used vendor=cros to avoid that everywhere else, so we should migrate the 32-bit toolchain.

since we don't have any boards using this as their CHOST anymore, and a lot of packages have moved to coreboot's toolchain, this should hopefully not be too disruptive.
 

Comment 1 by vapier@chromium.org, Today (7 hours ago)

Components: Infra>ChromeOS>Build
hrm, we'll need to do a bit of prep work on the build side

in the past, we'd run `update_chroot` with specific board names which meant the bot would install+update only the toolchains that board used.  but we changed the builders to run `update_chroot` w/out board info, so now we install+update all default toolchains for all boards now.

the old way allowed us to list new toolchain tuples in boards that didn't have active builders.  the sdk would detect that & build the new target & make binaries available.  then we could update active builders to rely on that toolchain once a sdk run finished.

i think i need to expand the toolchain.conf syntax to add a knob like "don't install it by default, but the sdk bot should build binaries for it".  that way the process would be:
- add new tuple to toolchain.conf w/that sdk setting
- wait for the sdk bot to finish & upload prebuilts
- update toolchain.conf to require the prebuilts

not really that much more work than before.

Sign in to add a comment