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

Problem building bitpacking v0.6.0 #632

Closed
didnt1able opened this issue Jul 9, 2019 · 5 comments
Closed

Problem building bitpacking v0.6.0 #632

didnt1able opened this issue Jul 9, 2019 · 5 comments
Labels
C: Bug Something isn't working Dependency Related to an external package that Plume uses

Comments

@didnt1able
Copy link

didnt1able commented Jul 9, 2019

When running cargo install --no-default-features --features postgres

error: failed to compile `plume v0.3.0 (/home/plume/Plume)`, intermediate artifacts can be found at `/home/plume/Plume/target


Caused by:
  Could not compile `bitpacking`.



Caused by:
  process didn't exit successfully: `rustc --crate-name bitpacking /home/plume/.cargo/registry/src/github.com-1ecc6299db9ec823/bitpacking-0.6.0/src/lib.rs --color always --crate-type lib --emit=dep-info,link -C opt-level=3 -C metadata=2470242703a6f858 -C extra-filename=-2470242703a6f858 --out-dir /home/plume/Plume/target/release/deps -L dependency=/home/plume/Plume/target/release/deps --extern crunchy=/home/plume/Plume/target/release/deps/libcrunchy-7e3361a81a9bb65a.rlib --cap-lints allow` (signal: 9, SIGKILL: kill)

  • v0.3.0:
  • Ubuntu 18.04:
@didnt1able didnt1able added the C: Bug Something isn't working label Jul 9, 2019
@trinity-1686a
Copy link
Contributor

trinity-1686a commented Jul 9, 2019

For some reason, bitpacking requires a lot of memory to compile. This also affect continuous integration. I'm looking into it but as of now, I have pretty much no idea why is that.
In the mean time, you may try to add some swap to your system before compiling

@didnt1able
Copy link
Author

For some reason, bitpacking requires a lot of memory to compile. This also affect continuous integration. I'm looking into it but as of now, I have pretty much no idea why is that.
In the mean time, you may try to add some swap to your system before compiling

Thank you for the information. I will try that

@igalic
Copy link
Contributor

igalic commented Jul 9, 2019

@fdb-hiroshima can we please open this issue upstream?

@trinity-1686a
Copy link
Contributor

waiting for tantivy 0.10.0 to come out

@trinity-1686a trinity-1686a removed the S: Blocked Something else needs to be fixed first label Jul 11, 2019
@marek-lach marek-lach added the Dependency Related to an external package that Plume uses label Jul 13, 2019
@trinity-1686a
Copy link
Contributor

this have been fixed in #643

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: Bug Something isn't working Dependency Related to an external package that Plume uses
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants