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

[7.0.1] After upgrading to bazel 7.0.0 gcc fails with: --push-state: unknown option #20835

Closed
bazel-io opened this issue Jan 10, 2024 · 3 comments
Closed

[7.0.1] After upgrading to bazel 7.0.0 gcc fails with: --push-state: unknown option #20835

bazel-io opened this issue Jan 10, 2024 · 3 comments
Milestone
7.0.1 release blo...

Comments

@bazel-io
Copy link
Member

Forked from #20834
@bazel-io bazel-io added this to the 7.0.1 release blockers milestone Jan 10, 2024
@bazel-io
Copy link
Member Author

Cherry-pick was attempted, but there may be merge conflict(s). Please resolve manually.
cc: @bazelbuild/triage

@meteorcloudy
Copy link
Member

/cc @fmeum This one has to be cherry picked manually.

@fmeum fmeum mentioned this issue Jan 15, 2024
Merged
@fmeum
Copy link
Collaborator

fmeum commented Jan 15, 2024

Sent #20901

meteorcloudy pushed a commit that referenced this issue Jan 15, 2024
@fmeum
Fix linker feature detection being performed on wrong linker (#20901)
a42bea7 
Bazel forces use of `lld` and `ld.gold` if found, but performed feature
detection on the default linker instead.

Fixes #20834

Closes #20833.

PiperOrigin-RevId: 598565598
Change-Id: I4890f278c5cc33d4e6a6ebb10d796fb1c22f9ba6

Closes #20835
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
7.0.1 release blockers
Development

No branches or pull requests
3 participants
@meteorcloudy @fmeum @bazel-io