Okay, I figured out the autogen.sh, no one told me it depended on autoconf
and automake...
Anyway, ./autogen.sh outputs this:
$ ./autogen.sh
configure.ac:18: installing `etc/compile'
configure.ac:9: installing `etc/config.guess'
configure.ac:9: installing `etc/config.sub'
configure.ac:7: installing `etc/install-sh'
configure.ac:7: installing `etc/missing'
Makefile.am: installing `etc/depcomp'
Can't exec "libtoolize": No such file or directory at /usr/bin/autoreconf
line 195.
Use of uninitialized value in pattern match (m//) at /usr/bin/autoreconf
line 195.
Which I'm assuming is ok, since ./configure && make went ahead on its merry
way:
$ ./configure && make
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking bitstring.h usability... no
checking bitstring.h presence... no
checking for bitstring.h... no
checking curses.h usability... no
checking curses.h presence... no
checking for curses.h... no
checking dirent.h usability... yes
checking dirent.h presence... yes
checking for dirent.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for inttypes.h... (cached) yes
checking libutil.h usability... no
checking libutil.h presence... no
checking for libutil.h... no
checking ncurses.h usability... no
checking ncurses.h presence... no
checking for ncurses.h... no
checking ndir.h usability... no
checking ndir.h presence... no
checking for ndir.h... no
checking paths.h usability... yes
checking paths.h presence... yes
checking for paths.h... yes
checking pty.h usability... yes
checking pty.h presence... yes
checking for pty.h... yes
checking for stdint.h... (cached) yes
checking sys/dir.h usability... yes
checking sys/dir.h presence... yes
checking for sys/dir.h... yes
checking sys/ndir.h usability... no
checking sys/ndir.h presence... no
checking for sys/ndir.h... no
checking sys/tree.h usability... no
checking sys/tree.h presence... no
checking for sys/tree.h... no
checking term.h usability... no
checking term.h presence... no
checking for term.h... no
checking util.h usability... no
checking util.h presence... no
checking for util.h... no
checking for gcc that whines about -I... yes
checking for glibc... yes
checking for library containing clock_gettime... -lrt
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBEVENT... no
checking for library containing event_init... no
configure: error: "libevent not found"
... and it ends not so merry. Seriously, every time I try to compile some
form of source code, it backfires and there's usually a whole month before
I figure out what's wrong. I hate it! What am I missing? Where could I have
found it?
- Hameed
On Tue, Mar 19, 2013 at 11:56 AM, Stroller
<strol...@stellar.eclipse.co.uk>wrote:
> git is a way for developers to store and access programming code.
>
> The git repository (surely?) contains newer code than your distro's
> packages.
>
> The feature you require is relatively new and is (presumably) not
> available in release versions of tmux.
>
>
> On 18 March 2013, at 14:41, Hameed Gifford wrote:
>
> > Build from git, as in compile the code myself and not install from apt?
> > Whats the difference?
> >
> > On Mon, Mar 18, 2013 at 6:04 AM, Nicholas Marriott wrote:
> >
> >> If you build tmux from git you can resize to an absolute size with
> >> resize-pane, so you can probably use that.
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> tmux-users mailing list
> tmux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tmux-users
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
