Skip to content
This repository has been archived by the owner on Oct 10, 2022. It is now read-only.

Broken on latest Rust nightly #75

Open
anyputer opened this issue Jan 13, 2019 · 2 comments · May be fixed by #77
Open

Broken on latest Rust nightly #75

anyputer opened this issue Jan 13, 2019 · 2 comments · May be fixed by #77

Comments

@anyputer
Copy link

RUST_TARGET_PATH=/d/projects/3ds-test xargo build --release
    Updating crates.io index
   Compiling cc v1.0.28
   Compiling core v0.0.0 (C:\Users\yarsa\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\src\libcore)
   Compiling compiler_builtins v0.1.5
   Compiling rustc-std-workspace-core v1.0.0 (C:\Users\yarsa\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\src\tools\rustc-std-workspace-core)
   Compiling alloc v0.0.0 (C:\Users\yarsa\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\src\liballoc)
    Finished release [optimized] target(s) in 36.42s
   Compiling libc v0.2.46
error[E0412]: cannot find type `Option` in this scope
   --> C:\Users\yarsa\.cargo\registry\src\github.com-1ecc6299db9ec823\libc-0.2.46\src\unix\newlib\mod.rs:723:36
    |
723 |     pub fn pthread_atfork(prepare: Option<unsafe extern fn()>,
    |                                    ^^^^^^ not found in this scope
help: possible candidates are found in other modules, you can import them into scope
    |
1   | use core::option::Option;
    |
1   | use core::prelude::v1::Option;
    |

error[E0412]: cannot find type `Option` in this scope
   --> C:\Users\yarsa\.cargo\registry\src\github.com-1ecc6299db9ec823\libc-0.2.46\src\unix\newlib\mod.rs:724:35
    |
724 |                           parent: Option<unsafe extern fn()>,
    |                                   ^^^^^^ not found in this scope
help: possible candidates are found in other modules, you can import them into scope
    |
1   | use core::option::Option;
    |
1   | use core::prelude::v1::Option;
    |

error[E0412]: cannot find type `Option` in this scope
   --> C:\Users\yarsa\.cargo\registry\src\github.com-1ecc6299db9ec823\libc-0.2.46\src\unix\newlib\mod.rs:725:34
    |
725 |                           child: Option<unsafe extern fn()>) -> ::c_int;
    |                                  ^^^^^^ not found in this scope
help: possible candidates are found in other modules, you can import them into scope
    |
1   | use core::option::Option;
    |
1   | use core::prelude::v1::Option;
    |

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0412`.
error: Could not compile `libc`.

To learn more, run the command again with --verbose.
error: `"cargo" "build" "--release" "--manifest-path" "C:\\Users\\yarsa\\AppData\\Local\\Temp\\xargo.S4U22119KTa1\\Cargo.toml" "--target" "3ds" "-p" "panic_abort"` failed with exit code: Some(101)
stack backtrace:
   0: <no info> (0x7ff6657eefb2)
   1: <no info> (0x7ff6657ef053)
   2: <no info> (0x7ff6657a3035)
   3: <no info> (0x7ff6657acf0b)
   4: <no info> (0x7ff6657b2acd)
   5: <no info> (0x7ff6657c0cf3)
   6: <no info> (0x7ff66579b736)
   7: <no info> (0x7ff665808207)
   8: <no info> (0x7ff665812c92)
   9: <no info> (0x7ff665808ac2)
  10: <no info> (0x7ff6657c1da7)
  11: <no info> (0x7ff665822518)
  12: BaseThreadInitThunk (0x7ff92b0f3034)
make: *** [Makefile:20: target/3ds/release/rust3ds-template.elf] Error 1```
@anyputer
Copy link
Author

I'm on Windows 10, if that matters.

@FenrirWolf
Copy link
Member

FenrirWolf commented Jan 23, 2019

What version of Rust are you using? The currently known-working nightly is nightly-2018-08-18 if you wanna try that one. std and other core libs depend on every unstable feature under the sun, so they tend to break pretty quickly as nightly rust churns along.

And yes, that version is quite old. I do plan to eventually get it compiling on current compilers but haven't gotten around to it as of yet.

@anyputer anyputer changed the title libc: cannot find type Option in this scope Broken on latest Rust nightly Feb 3, 2019
@DarkKirb DarkKirb linked a pull request Mar 15, 2019 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants