ncspot: Failing to build on NetBSD

Hopefully someone running ncspot on OpenBSD can help me here. I’m really keen to get this working on my NetBSD machine but I get a build error:

$ cargo run --no-default-features --features portaudio_backend,cursive/pancurses-backend 
...
error: failed to run custom build command for `ncurses v5.99.0`

Caused by:
  process didn't exit successfully: `/home/dave/Downloads/ncspot/target/debug/build/ncurses-cca56809b8b206f2/build-script-build` (exit code: 101)
--- stdout
cargo:rerun-if-env-changed=PKG_CONFIG_PATH
cargo:rustc-link-lib=ncursesw
OPT_LEVEL = Some("0")
TARGET = Some("x86_64-unknown-netbsd")
HOST = Some("x86_64-unknown-netbsd")
CC_x86_64-unknown-netbsd = None
CC_x86_64_unknown_netbsd = None
HOST_CC = None
CC = None
CFLAGS_x86_64-unknown-netbsd = None
CFLAGS_x86_64_unknown_netbsd = None
HOST_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("true")
CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")

--- stderr
/home/dave/Downloads/ncspot/target/debug/build/ncurses-c07513f36080cdf7/out/chtype_size.c:6:10: fatal error: ncurses.h: No such file or directory
 #include <ncurses.h>
          ^~~~~~~~~~~
compilation terminated.
thread 'main' panicked at 'assertion failed: command.status().expect("compilation failed").success()', /home/dave/.cargo/registry/src/github.com-1ecc6299db9ec823/ncurses-5.99.0/build.rs:105:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

warning: build failed, waiting for other jobs to finish...
error: build failed

Poraudio & ncurses are installed

$ pkgin list | grep portaudio                                                            
portaudio-190600.20161030nb5 Portable cross-platform audio API
$ pkgin list | grep ncurses                                                              
ncurses-6.2nb2       CRT screen handling and optimization package

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (4 by maintainers)

Commits related to this issue

Most upvoted comments

Awesome, out of curiosity: how was the issue with the incorrectly displayed characters fixed?

It hasn’t really, I don’t have a Spotify account, but I’m convinced its an UTF-8 issue. I’ve decided to import the package and if it happens to someone else, take it from there.

@Ramiferous also said the software has been working fine for him otherwise.