bazelbuild / bazelbuild/bazel

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

Open
#9,365 2 comments 0 reactions 0 assignees View on GitHub
help wanted P3 team-Documentation team-Rules-CPP type: documentation (cleanup)
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 18h
Merged PRs (30d)
75

Description

> 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 https://github.com/bazelbuild/bazel/issues/7075

Contributor guide

Open the contributing guide

Research direction

Start with the linked “Configuring C++ toolchains” tutorial and compare its cc_toolchain configuration with the deprecation guidance in issue 7075. Reproduce the example with Bazel 0.28.1 or the documented setup, then verify that following the tutorial no longer reports deprecated cpu and compiler attributes.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.