It looks like a problem with the LIB path. How do you set up your paths; are you using 32-bit ifort? I open an ifort Build Environment window, then start cygwin.bat in that window. This relies on both ifortvars.bat and ifort.cfg being set up, to avoid cygwin tool paths over-riding the Microsoft paths. Neither Microsoft nor Intel support this, so it is up to you to get it working.
cygwin link and ar work (usually) with 32-bit ifort, but not with 64-bit ifort. You might want to avoid using cygwin link, in case that is part of your problem. For example, you could un-install cygwin binutils as a test.
There is an apparently known problem where the Windows environment variables aren't always accessible. Microsoft apparently doesn't intend to fix it, unless it can be shown repeatably to impact customers using exclusively Microsoft tools under Vista. We have shown that it happens also under SFU with XP. I don't know any solution to that, except to try over.
