stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Farid Zaripov" <Farid_Zari...@epam.com>
Subject RE: Windows build failures
Date Wed, 05 Sep 2007 18:50:15 GMT
> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com] 
> Sent: Tuesday, September 04, 2007 8:28 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: Windows build failures
> 
> What is the status of the Windows builds on trunk? There 
> still are a large number of severe failures that need to be 
> resolved for the 4.2 release:
> 
> win_2000-4-x86	icl-10.0	all
  The command call "%ICPP_COMPILER10%\IA32\Bin\iclvars.bat" failed with
error:
"The system cannot find the path specified."

> win_2000-4-x86	icl-9.1		all
  The command call "%ICPP_COMPILER91%\IA32\Bin\iclvars.bat" failed with
error:
"The system cannot find the path specified."

  Is needed to check whether that path valid or not. Andrew, can you
chek this?


> win_2000-4-x86	msvc-7.1	all
  The tests did not invoked. I think that maximum command line length
was exceeded. The Windows 2000 command line limited by MAX_PATH value
(MAX_PATH == 260).
We need to add the ability to pass files list into exec utility using
external file, i.e.:
  exec.exe [OPTIONS] @files.lst

>From MSDN (function CreateProcess):
-----------------
lpCommandLine 
[in, out] Pointer to a null-terminated string that specifies the command
line to execute.
            The maximum length of this string is 32K characters.
Windows 2000:  The maximum length of this string is MAX_PATH characters.

-----------------


> win_2003-1-x86	msvc-7.1	11s
  Seems to be ok for now...


> win_xp-1-em64t	icl-10.0	12D-win32
> win_xp-1-em64t	icl-10.0	12d-win32
> win_xp-2-x86	icl-10.0	8s
> win_xp-2-x86	icl-9.1		all
  The "build.wsf(163, 14) (null): Invalid pointer" error.
Trying to fix thus: http://svn.apache.org/viewvc?rev=573012&view=rev

Farid.

Mime
View raw message