Skip to content

Switch macOS minimum version flag to gcc compatible version#20798

Closed
keith wants to merge 1 commit intobazelbuild:masterfrom
keith:ks/switch-macos-minimum-version-flag-to-gcc-compatible-version
Closed

Switch macOS minimum version flag to gcc compatible version#20798
keith wants to merge 1 commit intobazelbuild:masterfrom
keith:ks/switch-macos-minimum-version-flag-to-gcc-compatible-version

Conversation

@keith
Copy link
Copy Markdown
Member

@keith keith commented Jan 8, 2024

Fixes #20698

I'm not sure how that user got into that state yet, but it doesn't hurt for this to be gcc compatible just in case the user is intentionally using gcc on macOS

Fixes bazelbuild#20698

I'm not sure how that user got into that state yet, but it doesn't hurt
for this to be gcc compatible just in case the user is intentionally
using gcc on macOS
@github-actions github-actions Bot added team-Rules-CPP Issues for C++ rules awaiting-review PR is awaiting review from an assigned reviewer labels Jan 8, 2024
@keith
Copy link
Copy Markdown
Member Author

keith commented Jan 22, 2024

@comius can you review?

1 similar comment
@keith
Copy link
Copy Markdown
Member Author

keith commented Feb 2, 2024

@comius can you review?

@comius comius added awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally and removed awaiting-review PR is awaiting review from an assigned reviewer labels Feb 5, 2024
@copybara-service copybara-service Bot closed this in 05b1f06 Feb 6, 2024
@github-actions github-actions Bot removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Feb 6, 2024
@brentleyjones
Copy link
Copy Markdown
Contributor

@bazel-io flag

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Feb 6, 2024
@fmeum
Copy link
Copy Markdown
Collaborator

fmeum commented Feb 6, 2024

@bazel-io fork 7.1.0

@bazel-io bazel-io removed the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Feb 6, 2024
bazel-io pushed a commit to bazel-io/bazel that referenced this pull request Feb 6, 2024
Fixes bazelbuild#20698

I'm not sure how that user got into that state yet, but it doesn't hurt for this to be gcc compatible just in case the user is intentionally using gcc on macOS

Closes bazelbuild#20798.

PiperOrigin-RevId: 604515755
Change-Id: Ib9087fe6afbbb3514513a7d5d120fcf448e54f65
github-merge-queue Bot pushed a commit that referenced this pull request Feb 7, 2024
…21219)

Fixes #20698

I'm not sure how that user got into that state yet, but it doesn't hurt
for this to be gcc compatible just in case the user is intentionally
using gcc on macOS

Closes #20798.

Commit
05b1f06

PiperOrigin-RevId: 604515755
Change-Id: Ib9087fe6afbbb3514513a7d5d120fcf448e54f65

Co-authored-by: Keith Smiley <keithbsmiley@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

team-Rules-CPP Issues for C++ rules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants