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.

Sign up for GitHub

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

Jump to bottom

Getting-Started package issue #3896

Closed
keys-i opened this issue Apr 17, 2024 · 3 comments
Closed

Getting-Started package issue #3896

keys-i opened this issue Apr 17, 2024 · 3 comments
Labels
inactive Issues and PRs which have been inactive for at least 90 days.

Comments

@keys-i
Copy link

keys-i commented Apr 17, 2024

Description of the bug:

bazel is not a package of Ubuntu

Link to documentation:

https://github.com/carbon-language/carbon-lang

What should it say instead?

bazel-bootstrap \

Any other information, logs, or outputs that you want to share?

I tried running this on Ubuntu 23.10 which told me to use bazel-bootstrap
@jonmeow
Copy link
Contributor

jonmeow commented Apr 17, 2024 •
edited
Loading

Thanks. Note that bazel-bootstrap is not the same, and will conflict with a correct bazel install [both try to install /usr/bin/bazel]. We should fix notes, but in the meantime bazel's install instructions are at https://bazel.build/install/ubuntu#install-on-ubuntu; I'd suggest either setting up bazel's apt repo (commands here), or downloading bazelisk.

@jonmeow jonmeow mentioned this issue Jul 12, 2024
Merged
github-merge-queue bot pushed a commit that referenced this issue Jul 15, 2024
@jonmeow
Add a run_bazelisk wrapper script for linux. (#4129)
407b9e4 
I was considering making a "/bazel" alias for this, but I'm really on
the fence about whether that's a good choice. However, I do think this
is good to have to simplify installs.

Fixes #3071 and #3896
@github-actions GitHub Actions
Copy link

We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please comment or remove the inactive label. The long term label can also be added for issues which are expected to take time.

This issue is labeled inactive because the last activity was over 90 days ago.

@github-actions github-actions bot added the inactive Issues and PRs which have been inactive for at least 90 days. label Jul 17, 2024
@jonmeow
Copy link
Contributor

jonmeow commented Jul 17, 2024

Instructions updated by #4129

@jonmeow jonmeow closed this as completed Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
inactive Issues and PRs which have been inactive for at least 90 days.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonmeow @keys-i