Installing Lame & Pine (missing compiler components)

[Eric Dunbar]

Q: Why touch on both at the same time?  A: Because I happened to
tackle both projects on the same day.

FYI lame is in freshrpms repository so I didn't need to compile from
scratch... of course, I don't know if it was compile with
--with-vorbis.

As a pre-amble, I must say that the GREATEST frustration I have
experienced with Linux (YellowDog to be specific but not necessarily
b/c it's YDL) has been trying to install the components necessary to
build from source!

==============
General Packages
==============
To newbies (& not-so-newbies): make sure that you have the gcc and
rpm-builder packages installed before you tackle anything.

Logged in as root (sometimes su will allow you to do this):

yum install rpm-build
yum install gcc

The preceding packages are all needed to (a) compile/build anything
(gcc & rpm-build).

===========
Installing Lame
===========
[Lame is an MP3 encoder that's part of another project I'm working on]

FYI I just discovered that Lame is available from the freshrpms repository.

If you build lame from source, you may run into an error when you run
./configure (/lib/cpp). Your system is missing a needed file so you'll
need to install it for your system (32 bit (G4 or earlier) or 64 bit
(G5)).

This is the output from the ./configure --with-vorbis (I wanted ogg support):

configure: error: C++ preprocessor "/lib/cpp" fails sanity check

Check the config.log file for specifics but chances are that it'll be
cc1plus is missing (I've also seen comments in a google search
suggesting that missing kernel headers can cause this error (?))

Run "yum provides cc1plus" to find out the current version of the
package available for your system and then install...

yum install gcc-c++-ppc32
(replace 32 with 64 if you're on a G5)

That should fix things...

Then you can
./compile
make
make install

===========
Compiling Pine
===========
Downlad the source code from the uwash site
<http://www.washington.edu/pine/getpine/linux.html>

Extract it to somewhere (I used the GUI app) and then cd to the
directory in a console.

rpmbuild --rebuild pine-4.63-1.src.rpm
(or whatever the new version number is)

Keep an eye on the console output. It'll tell you where rpmbuild put
the compiled .rpm.

In my case this is what I needed to run...
rpm -ivh /usr/src/yellowdog/RPMS/ppc/pine-4.63-1.ppc.rpm

After that, run pine and see what a well designed CLUI interface looks
like (I still know people who use only pine and nothing else... I just
wanted something other than the pathetic and user-unfriendly mail that
ships as default with every Linux distro I've ever tried).

Hope these comments help someone else stuck with compiler problems.

Eric.