Skip to content

gh-102533: llvm-gcc should be detected correctly, and the correspond ar too… #102534

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

hbjzxzx
Copy link

@hbjzxzx hbjzxzx commented Mar 8, 2023

@bedevere-bot
Copy link

Most changes to Python require a NEWS entry.

Please add it using the blurb_it web app or the blurb command-line tool.

@ghost
Copy link

ghost commented Mar 8, 2023

The following commit authors need to sign the Contributor License Agreement:

Click the button to sign:
CLA not signed

@hbjzxzx
Copy link
Author

hbjzxzx commented Mar 8, 2023

Most changes to Python require a NEWS entry.

Please add it using the blurb_it web app or the blurb command-line tool.

The following commit authors need to sign the Contributor License Agreement:

Click the button to sign:CLA not signed

OK, I hava done all the requirements.

@hbjzxzx hbjzxzx changed the title fix: llvm-gcc should be detected correctly, and the correspond ar too… gh102533: llvm-gcc should be detected correctly, and the correspond ar too… Mar 8, 2023
@hbjzxzx hbjzxzx changed the title gh102533: llvm-gcc should be detected correctly, and the correspond ar too… gh-102533: llvm-gcc should be detected correctly, and the correspond ar too… Mar 8, 2023
@hbjzxzx hbjzxzx force-pushed the p/xzx/fix/configure branch 5 times, most recently from d31def5 to 4ed388b Compare March 8, 2023 16:19
@hbjzxzx hbjzxzx force-pushed the p/xzx/fix/configure branch from 4ed388b to 432749f Compare March 8, 2023 16:20
@corona10 corona10 self-assigned this Mar 9, 2023
@erlend-aasland
Copy link
Contributor

Please sign the CLA, @hbjzxzx.

@arhadthedev
Copy link
Member

OK, I hava done all the requirements.

Do you have your ZhenXingXu.cn@gmail.com email added into https://github.com/settings/emails?

@arhadthedev
Copy link
Member

Anyway, retriggering the bot by adding new commits, just to be safe.

@CAM-Gerlach
Copy link
Member

Closing and re-opening to retrigger bot (no need to add new commits)

@CAM-Gerlach CAM-Gerlach closed this Apr 5, 2023
@CAM-Gerlach CAM-Gerlach reopened this Apr 5, 2023
@CAM-Gerlach
Copy link
Member

CAM-Gerlach commented Apr 5, 2023

@hbjzxzx , could you re-try signing the CLA by clicking the red button and following the indicated steps (while signed in with your GitHub account)? After double-checking the bot's records, it seems that if you did attempt to sign previously, it didn't actually go through. Thanks!

@hbjzxzx
Copy link
Author

hbjzxzx commented Apr 10, 2023

@arhadthedev thank you so much for commit! I will follow your instruct later... these day is busy

@python-cla-bot
Copy link

python-cla-bot bot commented Apr 6, 2025

The following commit authors need to sign the Contributor License Agreement:

CLA signed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants