-
Notifications
You must be signed in to change notification settings - Fork 34
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
Can't compile substudy #5
Comments
Oh, my mistake. I misinterpreted your bug report. The part we need is the list of undefined symbols that should appear somewhere after |
Here's the full stacktrace:
|
Any ideas? |
Sorry for the slow response. This appears to be a problem with the Rust I don't have access to a Mac, so this may be tricky for me to solve. I'll Le 10 sept. 2016 12:56 PM, "Arthaey Angosii" notifications@github.com a
|
No worries about the slow response; I'm totally getting the support that I am paying for. ;) Let me know if you're game for a remote-debugging session (chat or screen-sharing) to see if we can figure out what's the deal with the Mac setup? |
A coworker of mine who knows Rust suggests that you distribute cross-piled binaries. Is that something you could do? |
Unfortunately, cross-compiling for the Mac is tricky, because you need various Apple headers that aren't freely redistributable, I think. Maybe he has a tutorial somewhere? I do compile MacOS X binaries for some of my programs using Travis CI, but occasionally they don't work, and I have no way to debug them without help from some kind soul who wants to share a screen with me. |
This should fix #5, but it may result in slightly lower-quality character set detection in some cases. Please try this out and let me know if it works.
OK, it turns out that this was an Xcode 8 compatibility issue affecting my Rust I've fixed this issue (and some Windows build issues) and made a pre-release version of substudy. If you have a moment, could you please test this for me by running:
If you don't have a reasonably up-to-date Rust installation, see https://www.rustup.rs/ for instructions. Thank you for the bug report and for any feedback you can provide! |
|
That looks like an upstream bug.
Le 1 mars 2017 7:50 PM, "Arthaey Angosii" <notifications@github.com> a
écrit :
… Compiling cmake v0.1.21
error: attributes on non-item statements and expressions are experimental. (see issue #15701)
--> /Users/arthaey/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.21/src/lib.rs:400:21
|
400 | #[cfg(windows)] {
| ^^^^^^^^^^^^^^
|
= help: add #![feature(stmt_expr_attributes)] to the crate attributes to enable
error: aborting due to previous error
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AACQY4VmQ1Y4sEMETsAvuXDuSImSw5VUks5rhhI7gaJpZM4J1Nad>
.
|
Does that mean there's nothing either of us can do about it? |
We may need to run |
I ran I don't see any mention of "cmake" in Cargo.toml, so I don't know how to upgrade the version number, nor to what version it should be upgraded. (FWIW, the version installed on my machine is cmake 3.5.2.) Below is the output of
|
Hmm. It's probably the rust-uchardet library, also on my account, that
depends on cmake. This will be hard to fix without cloning rust-uchardet
and building manually to find out what's going on.
(Sorry, juggling a few too many balls right now, so it may take me a bit.)
Le 5 mars 2017 9:21 PM, "Arthaey Angosii" <notifications@github.com> a
écrit :
I ran cargo update, which seemed to be successful, but cargo install --vers
0.4.1-pre.1 substudy still fails with the same cfg(windows) error on my Mac.
I don't see any mention of "cmake" in Cargo.toml, so I don't know how to
upgrade the version number, nor to what version it *should* be upgraded.
(FWIW, the version installed on my machine is cmake 3.5.2.)
Below is the output of cargo update, in case it's helpful to you:
$ cargo update
Updating registry `https://github.com/rust-lang/crates.io-index`
<https://github.com/rust-lang/crates.io-index>
Removing advapi32-sys v0.1.2
Updating aho-corasick v0.3.4 -> v0.5.3
Updating byteorder v0.3.13 -> v0.5.3
Updating csv v0.14.3 -> v0.14.7
Updating docopt v0.6.76 -> v0.6.86
Updating encoding v0.2.32 -> v0.2.33
Updating env_logger v0.3.2 -> v0.3.5
Updating gcc v0.3.20 -> v0.3.43
Adding kernel32-sys v0.2.2
Removing lazy_static v0.1.15
Adding lazy_static v0.1.16
Adding lazy_static v0.2.4
Removing libc v0.1.12
Removing libc v0.2.2
Adding libc v0.2.21
Updating log v0.3.3 -> v0.3.6
Updating memchr v0.1.7 -> v0.1.11
Updating num v0.1.28 -> v0.1.37
Adding num-bigint v0.1.36
Adding num-complex v0.1.36
Adding num-integer v0.1.33
Adding num-iter v0.1.33
Adding num-rational v0.1.36
Adding num-traits v0.1.37
Updating pkg-config v0.3.6 -> v0.3.9
Updating rand v0.3.12 -> v0.3.15
Updating regex v0.1.41 -> v0.1.80
Updating regex-syntax v0.2.2 -> v0.3.9
Updating rustc-serialize v0.3.16 -> v0.3.22
Updating strsim v0.3.0 -> v0.5.2
Adding thread-id v2.0.0
Adding thread_local v0.2.7
Updating toml v0.1.24 -> v0.1.30
Adding utf8-ranges v0.1.3
Updating winapi v0.2.5 -> v0.2.8
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AACQY5YfZnqc9SYMNR3nh68kEMwGxwARks5ri22-gaJpZM4J1Nad>
.
|
I know you're busy, so I'm not expecting a resolution on any sort of "schedule". But I wanted to bump this issue again, so you know there's still Mac interest out there. ;) |
Ah, thank you! Have you tried again lately? I updated a whole bunch of the dependencies of substudy sometime within the last couple of months, and there were Mac build fixes in there, IIRC. I really ought to get out my Mac and check. Maybe after the Super Challenge bot is back online. :-/ |
Yeah, I tried again before bumping the thread. :( Specifically, I ran |
Try just |
So tonight I decided to run through all the installation steps again. It involved re-installing Rust, plus upgrading cmake and ffmpeg. And.... :drumroll:
:D Not sure if any of the upgrades were what made the difference, or if the stars were just aligned today, or what. But I'm not complaining. :) |
Whoooo! |
We were just waiting on `docopt` to provide `serde` support. Fixes #5.
I'm trying to update substudy and get it running again after a long time not using it. It used to work! On this same laptop, even, but before I'd upgraded to El Capitan.
I'm on a Mac (El Capitan 10.11.5). I ran
multirust update stable
andbrew install cmake ffmpeg
to make sure those dependencies were all up to date. No issues there.But whether I run
cargo install substudy
orcargo build
, I get the same error message:Running with --verbose didn't give any more useful output.
The text was updated successfully, but these errors were encountered: