5 ms·
I hit the same thing, so I figured I would try compiling from source. I built ncurses 6.0 from source (installed to $HOME/local) and then htop 2.0 (also to $HO
by wrigby 11y ago
I hit the same thing, so I figured I would try compiling from source.
I built ncurses 6.0 from source (installed to $HOME/local) and then htop 2.0 (also to $HOME/local) and it worked a charm. This was on a clean (took it out of the box today) 10.11 system.
- nodesocket 11y agoEhhhhhhhhhhhh, really want to stick with using native package managers (brew, apt). Did you just add htop to the apt exclude?
- wrigby 11y agoAck, my bad. I meant OS X 10.11 (El Capitan). Same should probably work on any Linux distro with standard build tools installed. I keep a ~/local directory with built-from-source programs in it. That way I don't get any conflicts with system-wide package managers. Configure line for ncurses: ./configure --enable-pc-files --with-pkg-config-libdir=$HOME/local/lib/pkgconfig --with-shared --prefix=$HOME/local make -j8 && make install And for htop, a regular configure worked fine: ./configure --prefix=$HOME/local make -j8 && make install A quick check in my .bashrc (actually .zshrc) prepends $HOME/local/bin to my $PATH if it exists.
- alphonse23 11y agoI too would like to know how to install via brew.
- brianxq3 11y agoI quickly and hackily did `brew edit htop` and made these changes to install htop 2.0: https://gist.github.com/bmorton/231bc3d6b3aa6fbefd48 https://gist.github.com/bmorton/231bc3d6b3aa6fbefd48 I've got it on my list to fully fix it up and submit a PR, but feel free to flesh out my changes and submit instead :D