From the ICL_RSP.TXT you can see that for some reason, the compiler does not get the correct path to the linker:
If I understand correctly, $(VCInstallDir) should be substituted with real path. This is not immediately noticeable since compiler is being invoked with /c (compile only). However, if you remove /c it then complains:
icl: error #10037: could not find '$(VCInstallDir)\bin\x86_amd64'
I am not sure how to resolve that and whether it will help -- perhaps you can manually substitute it with fully qualified path in Visual Studio settings.
Also, my version of compiler complains about /Qftz-:
icl: command line remark #10148: option '/Qftz-' not supported
Moreover, I noticed that you have /Qipo enabled. It is known to cause problems in some cases and for smaller projects it may not give any performance benefits so it might be a good thing to try disabling it just to be sure.
Furthermore, I have noticed some environment variables which are unknown to me (Google shows nothing even remotely similar):
TRACKER_INTERMEDIATE=C:\Users\lee\Documents\Visual Studio 2010\Projects\test2\x64\Release
I see that it is mentioning icl so it might be worth looking into it -- perhaps you have insstalled an addon for VS2010 (or you have enabled some feature in VS2010?) which is causing Intel Compiler to crash?
Finally, I would like you to try compiling from the 64-bit Intel Compiler command prompt again -- since you have repaired your VS2010 installation it should work now. Please open 64-bit ICL command prompt, CD to your test2 solution folder and use the following command line:
icl /c /Qvc10 /Qlocation,link,"$(VCInstallDir)\bin\x86_amd64" /Zi /nologo /W3 /O2 /Oi /Qipo /Qftz- /D WIN32 /D NDEBUG /D _CONSOLE /D _UNICODE /D UNICODE /EHsc /MD /GS /Gy /fp:precise /Zc:wchar_t /Zc:forScope /Fo"x64\Release\" /Fd"x64\Release\vc100.pdb" /TC src\main.c
If that doesn't crash, try removing option /c to see if it crashes because of unexpanded $(VCInstallDir).
If you still have the same error when you open command prompt ("ERROR: Cannot determine the location of the VS Common Tools folder"), then your VS2010 installation is broken. Please check for the presence of one of the following registry keys:
Because that is where the vsvars32.bat and other VS2010 batch files look for the path. On my system, I found it in the underlined key.
What I meant is to replace the $(VCInstallDir) in the VS2010 Intel Compiler settings with fully qualified path and try building from the IDE.
That option is located under Tools->Options->Intel C++ Composer XE 2011->Compilers->Default Options.
Can you please try that as well and report back?
Also, you didn't comment on those TRACKER_<...> environment variables?
Regarding TRACKER, you are right, that is the executable which contains environment variables. It isBuild (MSBuild) File Tracker which is used to track the build process and generate those .tlog files which show read/write access to various files during compile time.
Back to square one then...
1. Is there any reason you did not install Windows 7 SP1?
2. Did you install VS2010 SP1?
Now that you told us that you have a very little free space available on your C: drive, I wonder if that is maybe contributing to your problems.
Namely, 1GB free out of 25GB is only 4% of free space. It is not recommended to have less than 15% of free space on an NTFS partition at any time (especially not on a system partition!).
Having that in mind, and the fact that 25GB is a partition way too small for normal Windows 7 functioning (you need space for system and per user TEMP folders, system restore points, previous versions of files, swap and hybernation), I would recommend that you reinstall your system from scratch using Windows 7 installation ISO with SP1 slipstreamed, and this time leave more free space on the C: partition.
OS reinstall would most likely also resolve your misterious compiler problem which we are failing to reproduce here.
If, by any chance, you have partitioned your disk using some 3rd party partitioning tool or if you have removed 100MB reserved partition when you installed Windows 7, I would also recommend to remove all partitions and allow Windows 7 Setup to create them. There is a reason why that 100MB partition is created other than just having boot files on it (hint: partition start alignment).
If you are unsure how much free space you need, here is a rough guideline:
1. Windows folder (22 GB current size here, includes assemblies, SxS, and Windows Installer software and patch installation cache which on my system is 4.7 GB at the moment)
2. hibernation + swap (approx. 2x amount of RAM you have, in my case 16 GB)
3. VS2010 (approx. 2.5 GB if you use only C++ plus 1.5GB if you need debugging simbols for OS files)
4. Intel Composer (2.5 GB if you also install static IPP libraries)
That totals to 44.5 GB of space just to get started. I also recommend at leasst 10 GB of free space for TEMP at any given time (so you can later install updates which require a lot of space such as service packs, etc).
((44.5 GB + space for other apps you need + 10 GB for temporary storage) + 5% of partition size for system restore) + 15% reserve for NTFS = C: partition size
An example calculation (if you need 3.5 GB for other applications such as Office, etc):
44.5 + 3.5 + 10 = 58
58 * 1.05 = 60.9
60.9 * 1.15 = ~70 GB
Don't forget to add space for Documents\Pictures\Video if you are using those locations, and keep in mind that web browsers and email clients can also take up a lot of space for caches.
Also, in my opinion, there is no advantage to installing programs to separate partition because C: partition is closer to the start of the drive and thus gives much faster loading times.
I can only recommend installing programs that can run in portable mode to a folder different from Program Files so you can easily get them running again if and when you need to reinstall. However, starting with Windows Vista, you must make sure that folder you install software into (in your case E:\ProgramsW7) has the same access permissions as Program Files to avoid potential installation and usage issues.
If you decide to follow my recommendations, make sure that after reinstalling Windows 7 you follow these steps:
1. Install latest chipset, video, audio, networking, and other drivers.
2. Install all available updates published after SP1 from Windows Update except language packs and other optional stuff you might not need
3. Install VS 2010
4. Install VS 2010 SP1
5. Install Intel Compiler
6. If it now works as it should, then create a restore point and continue installing other software.
Finally, I am afraid that we have reached the point where I will not be able to help you any further with your problem should you decide to keep your customized OS and software install.
Now that you told us that you have a very little free space available on your C: drive, I wonder if that is maybe contributing to your problems...
I absolutely agree with it. Good Luck!
No he does not. He can now build from ICL command prompt but not from Visual Studio.
Please read the whole thread again to see where we are at now. I also asked you a question.
I am now asking a second one -- why is icl.exe getting unexpanded $(VCInstallDir) in Qoptions,link from MSBuild?