Failing to build on NetBSD

[pfr-dev]

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

[natejank]

While I'm not running NetBSD, but I think I might have a solution. I'm not sure if the situation is different for you, but on my system (Fedora) you need different packages compile ncurses programs from the ones you need to run them. For me those packages are ncurses for running them and ncurses-devel for compiling them.

[hrkfdn]

Do you have pkg-config installed?

[pfr-dev]

While I'm not running NetBSD, but I think I might have a solution. I'm not sure if the situation is different for you, but on my system (Fedora) you need different packages compile ncurses programs from the ones you need to run them. For me those packages are ncurses for running them and ncurses-devel for compiling them.

AFAIK NetBSD does not split packages, i.e. development headers are included in the packages.

Do you have pkg-config installed?

$ pkgin list | grep pkg-config 
pkgconf-1.6.0        API-driven pkg-config replacement

[pfr-dev]

FYI if anyone is interested, Pin (total champ) has pushed this to pkgsrc-wip where hopefully someone will figure it out.

[pfr-dev]

UPDATE: Tobias Nygren worked his magic and got it working. Still currently in pkgsrc-wip for now.

However, some strange characters displaying ... Why?

[ghost]

@hrkfdn Do you have any suggestions to what might be causing this?

I was the one packaging ncspot for NetBSD with the valuble help of tnn as already mentioned, but I would like to know why this is happening before importing the package to pkgsrc. TIA.
/pin

[hrkfdn]

Nice work! Hmm, it looks like it's having problems with the special characters (bars, dotted lines, etc.).

Are you running this in an UTF-8 capable environment? You could also try the ncurses-backend instead of pancurses.

[ghost]

Nice work!

Thanks!

Are you running this in an UTF-8 capable environment?

Probably not. NetBSD supports too many old archs where enabling it by dafault would not be adviseble. It can be enabled though. @Ramiferous, please try enabling it.

You could also try the ncurses-backend

You mean patching Cargo.toml, change the default backend and re-compiling, right?
NetBSD splitsncurses in two packages, ncurses and ncursesw, where w stands for wide. I wonder what the syntax should be to get it right... But, hopefully enabling UTF-8 will be enough.
Thanks for your reply and hint.

[hrkfdn]

Yes, you can select the backend in Cargo.toml. These are available: https://github.com/gyscos/Cursive/wiki/Backends

[ghost]

@Ramiferous please enable unicode and test. If this does not work, I'll patch it. Thx!

[ghost]

ncspot has been imported into pkgsrc.
Feel free to close this issue.

[hrkfdn]

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

[ghost]

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.

[pfr-dev]

As Pin said, I couldn't get UTF-8 supported working on NetBSD yet. Will keep trying and once resolved will report back here.

I had a thought though, is it possible to implement an option for no UTF-8 support and to just use normal text symbols in their place? a kind of fallback mode if you will? I don't really need the fancy characters, but I'd like it to look neat at least.

[pfr-dev]

Update & ust an FYI incase anyone's interested. It appears that is not a problem with NetBSD not supporting UTF-8 but rather an issue with cursive on NetBSD. See the issue raised here:
gyscos/cursive#494

This all began here:
https://www.unitedbsd.com/d/233-spotify/44