Please edit instead of double posting

if you have a symlink to jam already, then you can safely delete the symlink without harming the executable, and you can easily restore it.
if there isn\'t a symlink, and you just found bjam \'cuz it
sounded like jam... then you can do this (no quotes, except the inner singlequotes) \"alias jam=\'/home/foo/development/jam-2.5/bin.linuxx86/jam\' >> ~/.bashrc\". Replace /home/foo/development/ with the path to the jam-2.5 folder.
Another way to do it is to write \"export PATH=/path/to/jam-2.5/bin.linuxx86/:$PATH\" ... But that will not carry over into a new shell, and could be annoying since each time you open a shell you have to type that out...

About Bison...
From acraigs instructions...
If you don\'t have a recent version of bison then you will need to get a more up to date file. Check your bison version by:
molblue$ bison -V
If it is not 1.35 you need to get a new file:
molblue$ cd $HOME/molblue/CS/plugins/aws
molblue$ wget -t0 -c http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/crystal/CS/plugins/aws/skinpars.cpp?rev=1.5
aws$ rm skinpars.cpp
aws$ mv skinpars.cpp\\?rev\\=1.5 skinpars.cpp
So, just try it with the current revision of the file you have, if that works then woohoo, the world is a utopia! Otherwise, follow acraig\'s steps...
Cheers!
josePhoenix