Despite my best efforts to build aila for Linux and Windows it proved not possible  .
But the good news is, Windows users can use aila on Windows at native (i.e. GNU/Linux) speed thanks to Cygwin. So here we go.
Update! Binary file delivery is proving difficult so we now recommand building from source. This is documented on a blog entry here on Connect [https://www-secure.symantec.com/connect/blogs/building-aila-source-cygwin]. The Cygwin install process thus changes to manually select the following 3 packages:
Installing Cygwin to run aila (using binaries delivered here on Symantec Connect or via the CWoC Google code pages):
To use Cygwin you must download and install it. The download is available on http://www.cygwin.com, and is a single executable file (setup.exe).
The installation is a 10 step process described here.
1. Run setup.exe
2. Install mode (I use default - download from Internet)
3. Choose the install path (default to C:\Cygwin)
4. Choose the package download location (I used C:\CygwinPackages)
5. The installer will prompt you to create the download directory if it doesn't exist
6. Select a mirror site to download from (I picked the first one proposed which works nicely)
7. The installer will pop-up an alert (to ensure the user understand the changes on version 1.7)
8. Select the packages to install: (Update! add gcc-core, make and subversion)
9. The installer downloads and install the necessary packages
10. Finalise the installation
Once this is done you can start Cygwin, which will initially create the user profile files and give you a standard Bash shell:
Update! The following section remains but you should use the instructions here to get the source (on Connect or via subversions): https://www-secure.symantec.com/connect/blogs/building-aila-source-cygwin.
Extract the aila binary file attached to the user directory (which should not be named Ludovic_Ferre ^_^):
This is it. You are now ready to run aila (using the "./" prefix to tell thge shell to look for the binary in the current directory, rathen than to search in the binary paths):
 I am using MinGW tool-chains to compile for Windows on my Linux server and unfortunately the resulting binary contains a bug I cannot get rid of. The bug shows up only on the windows binary in the form of a memory corruption of the ip address cache tree. This tree is build up from with nodes, each containing the payload (the cached string and a hit counter) allocated when the node is created and the string is cached. Strangely enough a tree node becomes corrupt and caused invalid memory read - and rashes the process (handled crash, but still).
 Using MinGW I compile the Win32 binaries however Windows is a UTF16 operating system, so all the string and system calls with strings need to be translated from the ANSI encoding to UTF16. This make the execution of aila much much slower on Windows than it is on GNU/Linux