-
Notifications
You must be signed in to change notification settings - Fork 308
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
Upgrade rust-toolchain to nightly-2018-09-09 #852
Conversation
@@ -26,28 +26,22 @@ max_width = 100 | |||
merge_derives = true | |||
newline_style = "Unix" | |||
normalize_comments = false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these still supported in some way?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are default already. The options are deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good! Thanks.
#![feature(const_fn)] | ||
#![feature(const_size_of)] | ||
#![allow(non_upper_case_globals)] | ||
#![allow(non_snake_case)] | ||
#![allow(private_no_mangle_fns)] | ||
#![allow(non_camel_case_types, non_snake_case, non_upper_case_globals)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe move this comment before the allow instead of allowing it to be placed after?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I looked at this last there were issues with the OSX allocation code. I do not see any patches in here for that. What was the final resolution?
@shaleh Yes, you are right. After checking the travis-ci output, I found this PR breaks the build on OSX (allocation code). |
A significant number of us use OSX. I am loathe to merge this without a solution. I had not worked on it because the Rust team was still deciding on the API for the allocation interface. If that has settled porting this over should not be too hard. |
|
@SolarAquarion Which platform did you build on?The code can built on Linux perfectly while has some issues on MacOS. Besides, do |
I had a git version of atk which caused the issue
On Sep 6, 2018 10:00 PM, "Harry Fei" <notifications@github.com> wrote:
@SolarAquarion <https://github.com/SolarAquarion> Which platform did you
build on?The code can build on Linux perfectly while has some issue on
MacOS.
Besides, do make clean may be helpful in some situation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#852 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFD6iECvd2muAfQixoAzW_t3bJ6mpvNnks5uYdNFgaJpZM4WYTub>
.
|
@shaleh I will try my best to fix the OSX build issues in future updates. |
|
Thanks! Last time I tried the alloc code was not settled enough. That diff is what I was hoping to eventually see. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work!
I tried doing a build of this (Linux - Debian) and had failures: There were a number of broken references when trying to make temacs: /home/cbbrowne/GitStuff/remacs/rust_src/src/lists.rs:184: undefined reference to I'm hoping that this moves things forwards soon; my last successful remacs build was back in June, and I certainly have been assortedly getting bitten by changes to the rust toolchain obsolescing some code within remacs. I tried forcing a build using the 2018-03-03 nightly rust, and that's breaking somewhat similarly, with some different missing objects upon trying to build temacs. |
Use the version in |
I was able to build this on my macOS |
@cbbrowne It's so odd, I don't have any idea about that. Could you try to build on both the master and this branch cleanly? The results may be helpful to find the root cause. Besides, don't override the toolchain using |
Do you mean you can build on OSX now? |
@harryfei no, I meant they should not be trying to use any version of Rust that is not in the checked in |
OSX does build now. But the test segfaults. So the alloc change is either incomplete or incorrect. |
@shaleh If you find the root cause, you can update this PR as you wish. FWIW, the Travis CI shows that the tests can be run normally (except for one failed test). |
Fix `make check` segfaults on mac
@sbillig has fixed the macOS |
I'll admit that I'm not entirely sure yet why rand::thread_rng causes a seg fault. I'm hoping that the portable dumper lands on the emacs master branch "soon", so the unexec stuff can go away, which should clear this up for good. https://www.reddit.com/r/emacs/comments/95vwej/pdumper_status/e3xkvt3/ |
OSX still failing? |
@shaleh Are you saying that it's still failing for you? If so, could you describe where it's failing and post relevant log messages, etc here? |
Oh, I see that the travis mac build is failing. The results are the same as on the master branch ("FAILED 1/7 epg-decrypt-1"). Seems like a travis environment issue; incompatible gpg version, perhaps. Definitely not introduced by this PR, anyway. |
We need a ticket to track the gpg issue. |
@harryfei thanks for helping carry this. |
Added a ticket for the gpg failure: #858 |
@harryfei Awesome, thank you! |
@harryfei I've also made you a collaborator, so you can review/merge PRs if you wish! :) |
Closes #752
Closes #759
Closes #725
Unblock #757