Skip to content

configure should fail if subcommands fail #1196

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
Closed
brson opened this issue Nov 19, 2011 · 1 comment
Closed

configure should fail if subcommands fail #1196

brson opened this issue Nov 19, 2011 · 1 comment
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Nov 19, 2011

In particular, calls to git or to llvm's configure script
@brson
Copy link
Contributor Author

brson commented Jan 6, 2012

c74d5ce

@brson brson closed this as completed Jan 6, 2012
@Fierelier Fierelier mentioned this issue Mar 11, 2023
Closed
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@adpaco-aws
Correct types for alignment expressions (rust-lang#1196)
2aef548 
* Correct types for alignment expressions

* Rename `dst` to `ptr`
Kobzol pushed a commit to Kobzol/rust that referenced this issue Dec 30, 2024
@steffahn
Trailing date comments in a line inside of a paragraph caused beginni…
858d7be 
…ng of a new paragraph. (rust-lang#1196)

This PR fixes the 2 occurrences of that.
(I'm not sure if there's an underlying issue with mdbook or if this is working as intended.)
bors pushed a commit to rust-lang-ci/rust that referenced this issue Jan 2, 2025
@steffahn
Trailing date comments in a line inside of a paragraph caused beginni…
5575d62 
…ng of a new paragraph. (rust-lang#1196)

This PR fixes the 2 occurrences of that.
(I'm not sure if there's an underlying issue with mdbook or if this is working as intended.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brson