Since nobody else has answered...

I only have Ubuntu in a virtual machine, so this might not work, but should give you an idea anyway.

First I downloaded allegro-5.1.0.tar.gz from the "Allegro 5.1.0 released!" thread at http://www.allegro.cc/forums/thread/608861 and saved it.

{"name":"605180","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/8\/5\/85b028d895bacf4da6cef36f28ea4720.png","w":801,"h":603,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/8\/5\/85b028d895bacf4da6cef36f28ea4720"}

I made a directory called "progdir" to hold allegro and any other programming junk (not likely in a virtual machine), then copied allegro tarfile to it, and extracted it, then followed the directions in the wiki entry.

{"name":"605181","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/3\/4\/3417fe3ff365117301529598827cd494.png","w":905,"h":789,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/3\/4\/3417fe3ff365117301529598827cd494"}

It turned out I didn't have cmake installed, so I followed those directions and tried it again.

{"name":"605182","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/3\/0\/3021fdf79a63cbe5b950b4055b8600d8.png","w":905,"h":789,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/3\/0\/3021fdf79a63cbe5b950b4055b8600d8"}
{"name":"605183","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/b\/3\/b38d344e96bf70e53f2048d553b0524d.png","w":1440,"h":900,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/b\/3\/b38d344e96bf70e53f2048d553b0524d"}

The cmake command bombed out saying I needed X11 development libraries (forgot to save the screenshot saying so) so I went to System | Administration | Synaptic Package Manager

{"name":"605184","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/7\/a\/7a82b24bb06c198c6738bdc0998170bd.png","w":816,"h":682,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/7\/a\/7a82b24bb06c198c6738bdc0998170bd"}

and typed in "x11 development" and searched

{"name":"605185","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/c\/c\/cc21942b6a7e718f6b47e16a1d16fc1b.png","w":1440,"h":900,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/c\/c\/cc21942b6a7e718f6b47e16a1d16fc1b"}

and ran cmake again. This time it said I lacked OpenGL libs, at which point I got frustrated and quit. (I already have a5 on my native Slackware)

This should get you pointed in the right direction anyway.

[EDIT]

To wrap up, I would have used the synaptic package manager for OpenGL and whatever else needed every time cmake complained, then (while still in the /home/pepsi/progdir/allegro-5.1.0/build directory) typed "make <enter>", then "sudo make install <enter>". Then you can "cd examples <enter>" and "ls <enter>" to see the executable names of example programs to enjoy. If some message comes up "can't find liballeg-umpty-ump.so" or similar, try the "sudo ldconfig <enter>" command to see if that'll fix it.

[EDIT2]

64 bit OS shouldn't affect anything, it should Just Work

I don't use any IDE's, although I like a windowed debugger such as ddd so I can watch variables without them scrolling off the screen, and they update automatically too.

Menu->Project->Build Options :

Search Directories tab -> Compiler -> Add /usr/local/include here, or wherever you installed allegro's headers

Search Directories tab -> Linker -> Add /usr/local/lib here, or wherever you installed the *.a files for allegro.

Linker Settings tab -> [Link Libraries | Other linker options] -> Add the path to the libraries to link to, or add the linker flags to link to them.

Link to a library named lib*.a by using -l*, where you replace * with whatever is there in the library name.

The necessary allegro libraries to link to are named the same as the header you include to use them - for example, #include <allegro5/allegro_font.h> corresponds to -lallegro_font.