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

error: no matching package named libnx-rs found #4

Open
slax57 opened this issue Nov 28, 2020 · 2 comments
Open

error: no matching package named libnx-rs found #4

slax57 opened this issue Nov 28, 2020 · 2 comments

Comments

@slax57
Copy link

slax57 commented Nov 28, 2020

Hi!

Well, this repo seems to be unmaintained for a while now, but I'll still try my luck.

I tried building this example using the provided docker image (3rd method).

I get the following error:

[...]
    Updating git repository `https://github.com/ischeinkman/libnx-rs-std`
    Updating git repository `https://github.com/ischeinkman/libnx-rs`
error: no matching package named `libnx-rs` found
location searched: https://github.com/ischeinkman/libnx-rs
required by package `std v0.0.0 (https://github.com/ischeinkman/libnx-rs-std?branch=switch#197cdb04)`
    ... which is depended on by `sysroot v0.0.0 (/tmp/xargo.qdwnV04ZQWJb)`
error: `"cargo" "build" "--release" "--manifest-path" "/tmp/xargo.qdwnV04ZQWJb/Cargo.toml" "--target" "aarch64-none-elf" "-v" "-p" "std"` failed with exit code: Some(101)
   0: error_chain::backtrace::imp::InternalBacktrace::new
   1: <error_chain::State as core::default::Default>::default
   2: <std::process::Command as xargo::extensions::CommandExt>::run
   3: xargo::sysroot::build
   4: xargo::sysroot::update
   5: xargo::main_inner
   6: std::sys_common::backtrace::__rust_begin_short_backtrace
   7: std::rt::lang_start::{{closure}}
   8: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/1c389ffeff814726dec325f0f2b0c99107df2673/library/core/src/ops/function.rs:259:13
      std::panicking::try::do_call
             at /rustc/1c389ffeff814726dec325f0f2b0c99107df2673/library/std/src/panicking.rs:379:40
      std::panicking::try
             at /rustc/1c389ffeff814726dec325f0f2b0c99107df2673/library/std/src/panicking.rs:343:19
      std::panic::catch_unwind
             at /rustc/1c389ffeff814726dec325f0f2b0c99107df2673/library/std/src/panic.rs:396:14
      std::rt::lang_start_internal
             at /rustc/1c389ffeff814726dec325f0f2b0c99107df2673/library/std/src/rt.rs:51:25
   9: main
  10: __libc_start_main
  11: _start

root@ee6f9f45ad27:/workdir#

Has anyone a clue where that might come from?

Thanks.

@ischeinkman
Copy link
Owner

So the TLDR of it is that you should probably be using the stuff here.

The issue is that the entire libnx-rs and "rust on switch via libnx" project went through some iteration and movement from libnx-rs to nx-rs, a parallel project originally started as a fork by @XorTroll that eventually superseded libnx-rs, thanks to both they're large amount of effort and my own new circumstances no longer allowing me to risk a ban (or really have a lot of time to commit libnx-rs. I did make a couple of commits here or there to nx-rs, though, which due to how Github works had me overwrite my own ischeinkman/libnx-rs Github repo with the new nx-rs one.
Meanwhile, this crate and Docker image don't know about this, so they are still trying to pull the non-rewritten libnx-rs crate from my ischeinkman/libnx-rs repo, even though what really lives there is the nx-rscrate. If you are really, 100% sure that you want to use the pre-rewrite stuff, which I would not recommend at this point, the final pre-rewrite commit of libnx-rs is this.

@slax57
Copy link
Author

slax57 commented Nov 29, 2020

Woaw. I don't know how I completely missed that group during my research for something similar.
Indeed this seems to be a good starting point for what I'm looking for, I'll give it a try.
Many thanks for your quick and accurate answer! 🙂

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

2 participants