Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The tutorial "Configuring C++ toolchains" uses deprecated mechanisms #9365

Open
ahyangyi opened this issue Sep 10, 2019 · 2 comments
Open

The tutorial "Configuring C++ toolchains" uses deprecated mechanisms #9365

ahyangyi opened this issue Sep 10, 2019 · 2 comments
Labels
help wanted Someone outside the Bazel team could own this P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-CPP Issues for C++ rules type: documentation (cleanup)

Comments

@ahyangyi
Copy link

ahyangyi commented Sep 10, 2019

ATTENTION! Please read and follow:

  • if this is a question about how to build / test / query / deploy using Bazel, or a discussion starter, send it to bazel-discuss@googlegroups.com
  • if this is a bug or feature request, fill the form below as best as you can.

Description of the problem / feature request:

The tutorial "Configuring C++ toolchains" uses deprecated mechanisms

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Follow the tutorial at https://docs.bazel.build/versions/master/tutorial/cc-toolchain-config.html
Get the following error message:

in cc_toolchain rule //asmjs_toolchain: attributes 'cpu' and 'compiler' have been deprecated, please remove them. See https://github.com/bazelbuild/bazel/issues/7075 for details.

What operating system are you running Bazel on?

Gentoo Linux

What's the output of bazel info release?

release 0.28.1- (@Non-Git)

If bazel info release returns "development version" or "(@Non-Git)", tell us how you built Bazel.

Built with portage (this shouldn't matter though)

Have you found anything relevant by searching the web?

Yeah, the error message itself points to #7075

@ahyangyi
Copy link
Author

ahyangyi commented Sep 10, 2019

Well, actually removing the cpu = ... line in cc_toolchain (but not the target_cpu = ... line in cc_toolchain_config.bzl) fixes the issue.

Anyway, this is a bug report for the documentation.

@irengrig irengrig added team-Rules-CPP Issues for C++ rules untriaged P1 I'll work on this now. (Assignee required) labels Sep 11, 2019
@scentini scentini added P2 We'll consider working on this in future. (Assignee optional) and removed untriaged labels Sep 12, 2019
@scentini scentini removed the P1 I'll work on this now. (Assignee required) label Sep 17, 2019
@oquenchil oquenchil added P3 We're not considering working on this, but happy to review a PR. (No assignee) and removed P2 We'll consider working on this in future. (Assignee optional) labels Nov 19, 2020
@UlrichEckhardt
Copy link

I don't see the issue in the documentation or maybe I just don't understand where you mean it's faulty. Can you give the actual filename and code? Or, maybe it was fixed and this can be closed.

@keertk keertk added the team-Documentation Documentation improvements that cannot be directly linked to other team labels label Jan 11, 2023
@keertk keertk added the help wanted Someone outside the Bazel team could own this label Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Someone outside the Bazel team could own this P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-CPP Issues for C++ rules type: documentation (cleanup)
Projects
None yet
Development

No branches or pull requests

8 participants