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

HEAD rust fails to compile #50

Closed
steveklabnik opened this issue Mar 4, 2015 · 6 comments
Closed

HEAD rust fails to compile #50

steveklabnik opened this issue Mar 4, 2015 · 6 comments

Comments

@steveklabnik
Copy link
Member

Sorry for not writing a PR, but my jetlagged brain isn't working for some reason. Seems easy:

   Compiling regex v0.1.16 (file:///home/steve/src/regex)
src/parse.rs:661:26: 661:41 error: mismatched types:
 expected `&'static [(&'static str, &'static &'static [(char, char)])]`,
    found `&'static [(&'static str, &'static [(char, char)])]`
(expected &-ptr,
    found slice) [E0308]
src/parse.rs:661         match find_class(UNICODE_CLASSES, name.as_slice()) {
                                          ^~~~~~~~~~~~~~~
error: aborting due to previous error
Could not compile `regex`.

@gchp
Copy link
Contributor

gchp commented Mar 4, 2015

I fixed this in my fork, however it still fails to build:

rustc src/lib.rs --crate-name regex --crate-type lib -g -C metadata=e4601a68be576f97 -C extra-filename=-e4601a68be576f97 --out-dir /home/gchp/github.com/gchp/regex/target --emit=dep-info,link -L dependency=/home/gchp/github.com/gchp/regex/target -L dependency=/home/gchp/github.com/gchp/regex/target/deps
[2]    19122 illegal hardware instruction (core dumped)  rustc src/lib.rs --crate-name regex --crate-type lib -g -C  -C  --out-dir   -

My changes are here: gchp@f1a13c8

@BurntSushi
Copy link
Member

rustc dumped core? That doesn't seem like a problem with regex...

But yeah, that fix looks about what I expected.

@gchp
Copy link
Contributor

gchp commented Mar 4, 2015

@BurntSushi yup! I'm not sure how to get more information than that though, to create an issue against rust.

Should I submit those changes in a PR anyway, or wait until it actually builds?

@BurntSushi
Copy link
Member

Yeah, please submit a PR. I'm getting the same behavior here too. (The latest nightly is out.)

@gchp
Copy link
Contributor

gchp commented Mar 4, 2015

Ok, done!

@laumann
Copy link
Contributor

laumann commented Mar 4, 2015

I'm having the exact same problem with rustc, getting the illegal hardware instruction. Should we open an issue on rust?

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

No branches or pull requests

4 participants