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

Allow opting-out of rpath usage #11744

Merged
merged 1 commit into from
Jan 24, 2014
Merged

Conversation

alexcrichton
Copy link
Member

By default, the compiler and libraries are all still built with rpaths, but this
can be opted out of with --disable-rpath to ./configure or --no-rpath to rustc.

Closes #5219

@alexcrichton
Copy link
Member Author

I've built this on OSX and linux and confirmed that no rpaths remain and the build actually finishes.

@brson
Copy link
Contributor

brson commented Jan 23, 2014

While this resolves #5219 according to its title, I think there's more to consider for 1.0 regarding rpaths so that we are sure we're doing what the distro's want.

@alexcrichton
Copy link
Member Author

Amended commit message and description to not close the bug.

@thestinger
Copy link
Contributor

@brson: I think we could close that old bug and open a fresh one discussing the defaults. I do think this should be off by default, but I'd rather present it in a new issue.

@brson
Copy link
Contributor

brson commented Jan 23, 2014

I opened #11746 and #11747

@alexcrichton
Copy link
Member Author

Re-editing PR description to close 5219 when merged.

bors added a commit that referenced this pull request Jan 23, 2014
By default, the compiler and libraries are all still built with rpaths, but this
can be opted out of with --disable-rpath to ./configure or --no-rpath to rustc.

Closes #5219
bors added a commit that referenced this pull request Jan 23, 2014
By default, the compiler and libraries are all still built with rpaths, but this
can be opted out of with --disable-rpath to ./configure or --no-rpath to rustc.

Closes #5219
By default, the compiler and libraries are all still built with rpaths, but this
can be opted out of with --disable-rpath to ./configure or --no-rpath to rustc.

cc rust-lang#5219
bors added a commit that referenced this pull request Jan 24, 2014
By default, the compiler and libraries are all still built with rpaths, but this
can be opted out of with --disable-rpath to ./configure or --no-rpath to rustc.

Closes #5219
@bors bors closed this Jan 24, 2014
@bors bors merged commit e715cdb into rust-lang:master Jan 24, 2014
@alexcrichton alexcrichton deleted the issue-5219 branch February 1, 2014 00:26
flip1995 pushed a commit to flip1995/rust that referenced this pull request Nov 2, 2023
Fix get_first false negative for VecDeque

fixes rust-lang#11695

Also run the lint on `VecDeque` and suggest using `.front()` instead of `.get(0)` when trying to access the first element.

PS: At first I implemented the VecDeque Lint in a separate `if_chain` (see the previous commit).
Let me know if thats the preferred way, then I will remove the refactoring into one block.

changelog: [`get_first`]: fix false negative: Also lint `VecDeque` and suggest using `front()`
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.

Make rpath usage optional
4 participants