Re: emacs 22.1 install on Ubuntu 7.04, 'Feisty Fawn'

[Tim X]

"Dave Pawson" <dave.pawson@gmail.com> writes:

> Thanks to Eli and others from this list who helped me get this list together.
>
>
> I found the following Ubuntu packages necessary prior to build.
> All were found (with deps) using synaptic package manager.
>
>
> build-essential      Y
> libc6-dev          Y  
>  *1   libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtk2.0-dev
> libice-dev         Y
> libice6-dev        Y
> libice6                    Y
> libjpeg62-dev      Y
> libjpeg62          Y
> libncurses5-dev            Y
> libpng12-dev       Y
> libpng12-0         Y
> libsm-dev          Y
> libtiff4-dev       Y
> libtiff4           Y
> libx11-dev                 Y
> libxext-dev                Y
> libxmu-dev         Y
> libxmu-headers             Y
> libxpm-dev         Y  
> libxt-dev          Y
> xlibs-dev          Y
>

As a useful tip, you would have been able to identify many of these and the
correct Debian/Ubuntu package names by having a look at the dependencies
for emacs21 using something like aptitude, semantic or even dselect. Also,
when using lets say aptitude, installing a runtime library also usually
suggests or ecommends the dev version of that library. The other package
management tools also do this.

>
> Issues.
>
> libfig and libungif seemed to cause some contention.
> No idea what they are.

Start aptitude, search for libungif by hitting / and entering the search
string. When you get the package, hit enter and you will get an explination
of what the package is, a list of packages it depends on a list of packages
which depend on it and some recommendations and/or suggestions of other
packages to install. Package management is probably the greatest advantage
of Debian based distros over RPM - learn its tools and save yourself lots
of wasted time. 


> Building, for a graphical interface. As root.
>

This has nothing to do with building emacs. Learn about X, read about the
differences between su and su -, read about Xauth and your .Xauthority file
and all will be clearer. 

>
> Download, from normal source.
> gunzip
>
> ./configure --with-x-toolkit=gtk
> make
> make install.
>
> Seems to put it into /usr/local/bin
>

Your life was made much much more difficult because you missed the most
important step that would have saved you days. 

Inbetween the gunzip and configure steps, you need to add

read the README file in the root of the src tree
read the INSTALL file in the root of the src tree

Also, note that the only stage which is likely to need root privs is the
make install. The rest can and should be done as a normal user, not root.

having done that, you would probably have built emacs on the second attempt
- the first attempt at running configure wold have alerted you to missing
libraries. Armed with the crucial information form the INSTALL and README
files, you would have understood what configure was telling you and known
what you needed to install. As you are new to Debian/Ubuntu, it may have
taken a bit of time to work out how to use the package management support
and find the packages you needed, but once you had done that, a re-run of
configure, followed by make and then make install would have worked fine. 

Tim

-- 
tcross (at) rapttech dot com dot au