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

Unable to run the project from scratch #121

Closed
FernandoKGA opened this issue Mar 4, 2021 · 2 comments
Closed

Unable to run the project from scratch #121

FernandoKGA opened this issue Mar 4, 2021 · 2 comments
Labels
type: bug Something is not working as it should.

Comments

@FernandoKGA
Copy link

FernandoKGA commented Mar 4, 2021

Describe the bug
Cannot run the project due to a package build problem.
Error:

   ... many downloads and compiles later...
   Compiling owned_ttf_parser v0.6.0
error: failed to run custom build command for `x11 v2.18.2`

Caused by:
  process didn't exit successfully: `/home/ferkarchiloff/Airshipper/target/release/build/x11-9f19e8c63dd62c9f/build-script-build` (exit code: 101)
  --- stdout
  cargo:rerun-if-env-changed=X11_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=X11_STATIC
  cargo:rerun-if-env-changed=X11_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Failure { command: "\"pkg-config\" \"--libs\" \"--cflags\" \"x11\" \"x11 >= 1.4.99.1\"", output: Output { status: ExitStatus(ExitStatus(256)), stdout: "", stderr: "Package x11 was not found in the pkg-config search path.\nPerhaps you should add the directory containing `x11.pc\'\nto the PKG_CONFIG_PATH environment variable\nNo package \'x11\' found\nPackage x11 was not found in the pkg-config search path.\nPerhaps you should add the directory containing `x11.pc\'\nto the PKG_CONFIG_PATH environment variable\nNo package \'x11\' found\n" } }', /home/ferkarchiloff/.cargo/registry/src/github.com-1ecc6299db9ec823/x11-2.18.2/build.rs:36:67
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed
ferkarchiloff@ferkarchiloff-desktop:~/Airshipper$ 

To Reproduce
Steps to reproduce the behavior:

  1. Clone the repository.
  2. cd into it.
  3. Run the cargo run --release command.
  4. See error.

Expected behavior
I was expecting to run it and get Airshipper running.

Desktop (please complete the following information):

  • OS: Ubuntu MATE 20.04.2 LTS (Focal Fossa) 64-bit
  • GPU: AMD RX580 8GB AREZ OC
@FernandoKGA FernandoKGA added the type: bug Something is not working as it should. label Mar 4, 2021
@FernandoKGA FernandoKGA changed the title Cannot run project from scrap Unable to run the project from scratch Mar 4, 2021
@FernandoKGA
Copy link
Author

FernandoKGA commented Mar 5, 2021

There is an issue in other repository that talk about this: Issue that mentions this error.

To resolve it:

sudo apt install libx11-dev

I had another issue in sequence, about the openssl (related), resolved with:

sudo apt install libssl-dev

Both problems are probably related because is a Debian based system.

The README.md must have clearer instructions, some of them are isolated in the Veloren book, in the 3.1.3. Compiling session, they should be at the repository too, as the code is here.

@FernandoKGA
Copy link
Author

After doing this, deleting the repository and doing the README.md steps again makes the project build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something is not working as it should.
Projects
None yet
Development

No branches or pull requests

1 participant