10XGenomics / bamtofastq

Convert 10x BAM files to the original FASTQs compatible with 10x pipelines
MIT License
59 stars 6 forks source link

Compiling #14

Closed dslater82 closed 3 months ago

dslater82 commented 4 years ago

When I compile by running 'cargo build --release', I receive the following error. I am using rust version 1.41.1.

[easybuild@compute-0-0 bamtofastq]$ cargo build --release Compiling libc v0.2.43 error[E0463]: can't find crate for std

error: aborting due to previous error

For more information about this error, try rustc --explain E0463. error: could not compile libc.

To learn more, run the command again with --verbose

Yale73 commented 4 years ago

We don't need to run the 'cargo build --release', use the bamtofastq direcely.

pmarks commented 4 years ago

@dslater82 that's really bizarre... are you sure you have a working Rust setup? Are you able to compile other crates. Any more info on the platform you're using would also be useful.

cjfields commented 4 years ago

@dslater82 @pmarks I can add a little, I am attempting to compile on the same system. I see the same error, but it seems to be missing some libraries?

EDIT: I should note the below output was from rerunning cargo so many of the crates are already cached.

[cjfields@biologin-hpcbio bamtofastq]$ cargo build --release
  Downloaded human-panic v1.0.3
  Downloaded rust-htslib v0.30.0
  Downloaded bio-types v0.6.0
  Downloaded derive-new v0.5.8
   Compiling cc v1.0.50
   Compiling libc v0.2.68
   Compiling proc-macro2 v1.0.9
   Compiling unicode-xid v0.2.0
   Compiling syn v1.0.17
   Compiling cfg-if v0.1.10
   Compiling serde v1.0.105
   Compiling autocfg v1.0.0
   Compiling version_check v0.9.1
   Compiling memchr v2.3.3
   Compiling lazy_static v1.4.0
   Compiling pkg-config v0.3.17
   Compiling bitflags v1.2.1
   Compiling rustc-demangle v0.1.16
   Compiling ryu v1.0.3
   Compiling regex-syntax v0.6.17
error[E0463]: can't find crate for `std`

error[E0463]: can't find crate for `std`

error[E0463]: can't find crate for `std`

error[E0463]: can't find crate for `std`

error[E0463]: can't find crate for `std`

error[E0463]: can't find crate for `std`

error[E0463]: can't find crate for `core`

error[E0463]: can't find crate for `std`

error[E0463]: can't find crate for `std`

error[E0463]: can't find crate for `core`

error[E0463]: can't find crate for `core`

error[E0463]: can't find crate for `std`

error[E0463]: can't find crate for `std`

error[E0463]: can't find crate for `core`

error[E0463]: can't find crate for `std`

error: aborting due to previous error

error: aborting due to previous error

error: aborting due to previous error

error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
For more information about this error, try `rustc --explain E0463`.
For more information about this error, try `rustc --explain E0463`.
error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
For more information about this error, try `rustc --explain E0463`.
error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: aborting due to previous error

error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
For more information about this error, try `rustc --explain E0463`.
error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: could not compile `bitflags`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `ryu`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `rustc-demangle`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `cc`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `pkg-config`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `memchr`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `cfg-if`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `unicode-xid`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `lazy_static`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `syn`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `serde`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `proc-macro2`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `autocfg`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `version_check`.
warning: build failed, waiting for other jobs to finish...
error: could not compile `libc`.
warning: build failed, waiting for other jobs to finish...
error[E0463]: can't find crate for `std`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: could not compile `regex-syntax`.

To learn more, run the command again with --verbose.
pmarks commented 4 years ago

Hi @cjfields -- I've never seen an error anything like that in Rust before - it really makes me suspect somethings wrong with your Rust installation. Can post the result from cargo --version. Could you also try building some other popular tool like ripgrep: https://github.com/BurntSushi/ripgrep and see if that works?

cjfields commented 4 years ago

Hi @pmarks, I suspect this as well. We did notice that you made a binary release that does seem to work so this isn't currently high priority. @dslater82 should we close this ticket?

evolvedmicrobe commented 3 months ago

Closing as this looks like it was solved.