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.

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

Add flang-activation #27470

Merged
merged 20 commits into from
Sep 10, 2024
Merged

Add flang-activation #27470

merged 20 commits into from
Sep 10, 2024

Conversation

h-vetinari
Copy link
Member

@conda-forge-webservices
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/flang-activation/meta.yaml) and found some lint.

Here's what I've got...

For recipes/flang-activation/meta.yaml:

  • The following maintainers have not yet confirmed that they are willing to be listed here: isuruf. Please ask them to comment on this PR if they are.

@h-vetinari
Copy link
Member Author

@isuruf, this should handle the flang compiler activation split, PTAL! :)

I added you as a maintainer, please let me know if you'd prefer not to be.

@h-vetinari
Copy link
Member Author

Gentle ping @isuruf

h-vetinari and others added 4 commits September 5, 2024 11:48
@conda-forge-webservices
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/flang-activation/meta.yaml) and found it was in an excellent condition.

@h-vetinari
Copy link
Member Author

Thanks for the review - that should all be fixed now.

@h-vetinari
Copy link
Member Author

Anything else here @isuruf?

@h-vetinari
Copy link
Member Author

Gentle ping @isuruf

@h-vetinari
Copy link
Member Author

Any last comments here @isuruf?

Comment on lines 41 to 42
# rename flang-new -> flang is happening soon:
# https://discourse.llvm.org/t/proposal-rename-flang-new-to-flang/69462
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment seems irrelevant

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an updated version from what we currently have in the flang feedstock. As it was looking like it would finally happen a few days ago (until the goalposts shifted yet again), I was debating with myself whether we want to do the rename for flang 19 already. Might make the fortran migration a bit simpler. 🤷

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't mean the contents of the comment. I was referring to why this comment needs to be in the test section. It seems irrelevant.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's more visible in the recipe than in the activation script, and the test section is where we're using the name (or now, the value of FC).

@h-vetinari
Copy link
Member Author

Thanks for the review! 🙏

@h-vetinari
Copy link
Member Author

Good to merge now?

Co-authored-by: Isuru Fernando <isuruf@gmail.com>
@h-vetinari h-vetinari merged commit 4f96b50 into conda-forge:main Sep 10, 2024
5 checks passed
@h-vetinari h-vetinari deleted the flang branch September 10, 2024 16:24
@h-vetinari
Copy link
Member Author

Thanks for iterating on this. We can keep polishing things on the feedstock, flang 19.1.0 GA is around the corner anyway. :)

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

Successfully merging this pull request may close these issues.

2 participants