Build fails with no such target '@platforms//cpu:ppc64le' error

[giordano]

When building a downstream package using commit 469329e of XLA we get the following error message:

ERROR: /workspace/bazel_root/097636303b1142f44508c1d8e3494e4b/external/xla/xla/tsl/BUILD:297:15: no such target '@platforms//cpu:ppc64le': target 'ppc64le' not declared in package 'cpu' defined by /workspace/bazel_root/097636303b1142f44508c1d8e3494e4b/external/platforms/cpu/BUILD (Tip: use `query "@platforms//cpu:*"` to see all the targets in that package) and referenced by '@xla//xla/tsl:linux_ppc64le'
ERROR: /workspace/bazel_root/097636303b1142f44508c1d8e3494e4b/external/xla/xla/tsl/BUILD:455:29: errors encountered resolving select() keys for @xla//xla/tsl:linux_any_3
ERROR: /workspace/bazel_root/097636303b1142f44508c1d8e3494e4b/external/xla/xla/tsl/platform/default/BUILD:330:11: errors encountered resolving select() keys for @xla//xla/tsl/platform/default:platform_port

Most likely due to 4ee2886 (#21088)

[pzembrod]

Thanks for the bug report. Author of #21088 here.
That change has been rolled back for now due to another problem it caused.
In the case you are reporting it's likely that @platforms isn't yet declared as a dependency of XLA - my bad; I'll look into that.
But as said - with XLA synced to head you should be good again for now.

[giordano]

Uhm, we were having the error above on 469329e, so maybe the culprit is something else than #21088?

[pzembrod]

Hm, I'm not sure, 4ee2886 aka #21088 is before 469329e, isn't it? So I guess it could still be the culprit; from the content of the commit it would make sense to me.
The rollback doesn't seem to have propagated to github, though.

[giordano]

The rollback doesn't seem to have propagated to github, though.

Ah, ok, that's what was confusing me then 🙂

[pzembrod]

Hi @giordano, 4b89299 contains the roll forward with the fix for the build break you reported; do you think you could give it a spin and see if you can still build?

[giordano]

Yes, sorry, I forgot to report back, new xla versions are working good now after the upgrade a few days ago, thanks!

[pzembrod]

Ah, thanks :-)
Actually, what I had meant is if you could try building again at current head; my latest commit 4b89299 contains the same changes as the (now reverted) commit that broke your build, plus what I believe is the fix for your break.
So I of course believe your build should still work but I'd love to see that confirmed. :-)