forked from mobile-shell/mosh
-
Notifications
You must be signed in to change notification settings - Fork 1
Build Instructions
kmcallister edited this page May 21, 2012
·
23 revisions
Most of this is noted in the main README. But here are some additional bits.
As of Mosh 1.2, Boost is no longer needed.
- Should be in ports as "mosh" and homebrew as "mobile-shell"
- Tested on Snow Leopard and Lion
-
clang++
works. (export CXX=clang++
) - You may need a newer autoconf to build from master. But the tarballs are fine.
Manually: (adapt as needed)
brew install protobuf
brew install boost
brew install pkg-config
git clone https://github.com/keithw/mosh.git
cd mosh
./autogen.sh
./configure
make
make install
You don't need to build here. It's in the mosh_project
locker. --server='athrun mosh_project mosh-server'
Nobody's packaged mosh for Debian stable yet. In lieu of doing so myself, here is the quick list of packages I found I needed to install before mosh would compile, and run:
apt-get install protobuf-compiler libprotobuf-dev libutempter-dev libboost-dev libio-pty-perl pkg-config
Notes:
-
libio-pty-perl
is not needed for compilation/installation, just runtime - I installed all of the libboost-*1.42-dev pkgs as well, but I'm guessing libboost-dev is the minimum needed
sudo apt-get install automake libtool g++ protobuf-compiler libprotobuf-dev libboost-dev libutempter-dev libncurses5-dev zlib1g-dev libio-pty-perl
git clone https://github.com/keithw/mosh.git
cd mosh
./autogen.sh
./configure
make
make install
Notes:
-
libio-pty-perl
is not needed for compilation/installation, just runtime -
mosh-server
andmosh-client
will be insrc/frontend/
In case you want to install mosh on an Amazon Linux AMI:
- Enable the EPEL repository.
sudo yum install protobuf-compiler protobuf-devel libutempter-devel ncurses ncurses-devel zlib-devel boost-devel
- Download the latest release from http://mosh.mit.edu, unzip, and
./configure
,make
,sudo make install
.
Some of the yum
packages may be unnecessary, but this worked for me.
Note that you'll also have to open up ports 60000-61000. On EC2, you can do this through the AWS management console under EC2 > Security Groups.