Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Intel C++/Windows XP build failures
Date: Tue, 18 Sep 2007 14:31:06 -0600
Message-ID: 
 <C8506D6098A6F545BA3745D0CE359E830194E837@qxvcexch01.ad.quovadx.com>
In-Reply-To: <7BDB2168BEAEF14C98F1901FD2DE6438F57EB4@epmsa009.minsk.epam.com>
Thread-Topic: Intel C++/Windows XP build failures
Thread-Index: Acf5tYFyQbzhi4IqTA6fQGPkqe8bUwAS4yRAAAw1JiA=
References: <46EF631C.904@roguewave.com>
 <7BDB2168BEAEF14C98F1901FD2DE6438F57EB4@epmsa009.minsk.epam.com>
From: "Travis Vitek" <tvitek@quovadx.com>
To: <stdcxx-dev@incubator.apache.org>

=20

>Farid Zaripov wrote:
>
>> Travis, can you please try to determine the difference=20
>> between the "good" and the "bad" servers to see if we're=20
>> missing patches or what else could be causing the failures?=20
>> If there is a problem with the environment (incorrectly set=20
>> up compilers, etc.), please let Andrew know so he can start=20
>> working on getting it corrected.
>
>  I suggest to try re-intergare ICC into VisualStudio by invoking
>
>"C:\Program Files (x86)\Intel\Compiler\VS
>Integration\C++\VS2005\integrate.bat" "C:\Program Files (x86)\Microsoft
>Visual Studio 8"
>
>Farid.
>

I looked at the versions, and everything matched up as expected. As a
test I tried to open the Visual Studio on 'stein'. I got an error
message...

  [Intel(R) Vtune(TM) Performance Analyzer]------[X]
  |                                                |
  | One or more components did not load correctly. |
  | You may need to reinstall the product.         |
  |                                                |
  +------------------------------------------------+

I do not get this error message on the machines that are known to work
work [box, mug]. I went ahead and ran the integration script as
suggested by Farid above, and after running it I had no problems running
Visual Studio. I'm pretty sure that this is going to fix the problems.

Travis