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

support for GNU configure syntax #9760

Closed
wants to merge 3 commits into from
Closed

support for GNU configure syntax #9760

wants to merge 3 commits into from

Conversation

cnd
Copy link
Contributor

@cnd cnd commented Oct 8, 2013

Re-created: #9565

t will be useful for unix systems, some package managers and external tools that is passing / maybe looking for GNU configure syntax options.

One of related bugs: #5138

Also that could be useful in future if project will really install man pages / other stuff using those variables.

@pnkfelix
Copy link
Member

pnkfelix commented Oct 8, 2013

cc me

@brson
Copy link
Contributor

brson commented Oct 8, 2013

Oh sorry @Heather I missed your questions in the other PR. I think my previous comment explained more or less how to convert to the new variable names.

To make mandir do something useful you'll need to export CFG_MANDIR from configure using putvar here. Then use that variable for copying the man pages in install.mk.

@cnd
Copy link
Contributor Author

cnd commented Oct 9, 2013

@brson thank you , I never used to work with hand-written configure scripts.

@adrientetar
Copy link
Contributor

Maybe old commands can be dropped as soon as the buildbots are edited to work with GNU commands?

@brson
Copy link
Contributor

brson commented Oct 11, 2013

@adridu59 yes

@cnd
Copy link
Contributor Author

cnd commented Oct 17, 2013

This pull request is ready / and waiting for review.

@cnd
Copy link
Contributor Author

cnd commented Oct 18, 2013

fork moved to Cynede organization

@brson
Copy link
Contributor

brson commented Oct 19, 2013

Besides my comment about the linux target triple, this looks great! Thanks for sticking with it. It does need a rebase now though.

@cnd
Copy link
Contributor Author

cnd commented Oct 19, 2013

@brson thank you, but one of #rust irc users was confused about renaming all CFG_***_TRIPLE to remove TRIPLE word, so I really hope it's fine thing to do.

Re-base is easy but separating unknown fix is a bit more of work ... I can do it but it will take some more time. Are you sure that it's not safe to replace unknown-lunux-gnu with pc-linux-gnu right now? Because at least mingw already on pc- and I don't get why linux is still being on unknown.

@cnd
Copy link
Contributor Author

cnd commented Oct 19, 2013

re-based.

@brson
Copy link
Contributor

brson commented Oct 21, 2013

Superseded by #9990

@brson brson closed this Oct 21, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Nov 21, 2022
Add new lint [`let_underscore_future`]

This closes rust-lang#9721
---

changelog: add new lint [`let_underscore_future`]
flip1995 pushed a commit to flip1995/rust that referenced this pull request Mar 10, 2023
Downgrade let_underscore_untyped to restriction

From reading rust-lang#6842 I am not convinced of the cost/benefit of this lint even as a pedantic lint.

It sounds like the primary motivation was to catch cases of `fn() -> Result` being changed to `async fn() -> Result`. If the original Result was ignored by a `let _`, then the compiler wouldn't guide you to add `.await`. **However, this situation is caught in a more specific way by [let_underscore_future](https://rust-lang.github.io/rust-clippy/master/index.html#let_underscore_future) which was introduced _after_ the original suggestion (rust-lang#9760).**

In rust-lang#10410 it was mentioned twice that a <kbd>restriction</kbd> lint might be more appropriate for let_underscore_untyped.

changelog: Moved [`let_underscore_untyped`] to restriction
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants