You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@stdcxx.apache.org by "Travis Vitek (JIRA)" <ji...@apache.org> on 2008/06/06 01:28:45 UTC

[jira] Commented: (STDCXX-685) [Windows] slashes in Windows pathnames in build logs

    [ https://issues.apache.org/jira/browse/STDCXX-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602852#action_12602852 ] 

Travis Vitek commented on STDCXX-685:
-------------------------------------

Here is the output from an 15s build of the {{accumulate}} example on the 4.2.x branch on win-xp-msvc-7.1.

{noformat}
Creating temporary file "$(BUILDDIR)\15s\examples\accumulate\RSP000005.rsp" with contents
[
/Od /I "$(TOPDIR)\examples\include" /I "$(TOPDIR)\include" /I "$(TOPDIR)\include\ansi" /I "$(BUILDDIR)\15s\include" /D "_RWSTDDEBUG" /D "_MBCS" /Gm /EHsc /MTd /GS /GR /Fo"$(BUILDDIR)\15s\examples\accumulate/" /Fd"$(BUILDDIR)\15s\examples\accumulate/vc70.pdb" /W3 /c /Zi /TP   
"\bman5\builds\34829230\source-buildspace\examples\manual\accumulate.cpp"
]
Creating command line "cl.exe @"$(BUILDDIR)\15s\examples\accumulate\RSP000005.rsp" /nologo"
Creating temporary file "$(BUILDDIR)\15s\examples\accumulate\RSP000006.rsp" with contents
[
/OUT:"$(BUILDDIR)\15s\examples\accumulate.exe" /INCREMENTAL:NO /NOLOGO /NODEFAULTLIB:"libcpmtd.lib" /DEBUG /PDB:"$(BUILDDIR)\15s\examples\accumulate.pdb" /SUBSYSTEM:CONSOLE   kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib "\bman5\builds\34829230\source-buildspace\build\msvc-7.1\15s\lib\libstd15s.lib" "\bman5\builds\34829230\source-buildspace\build\msvc-7.1\15s\lib\libstd15s.lib"
"\bman5\builds\34829230\source-buildspace\build\msvc-7.1\15s\examples\accumulate\accumulate.obj"
]
Creating command line "link.exe @"$(BUILDDIR)\15s\examples\accumulate\RSP000006.rsp""
{noformat}

Here is the output from an 15s build of the {{accumulate}} example on the 4.2.x branch on win-xp-msvc-8.0.

{noformat}
Creating temporary file "$(BUILDDIR)\15s\examples\accumulate\RSP00000580885604.rsp" with contents
[
/Od /I "$(TOPDIR)\examples\include" /I "$(TOPDIR)\include" /I "$(TOPDIR)\include\ansi" /I "$(BUILDDIR)\15s\include" /D "_RWSTDDEBUG" /D "_MBCS" /Gm /EHsc /MTd /Fo"$(BUILDDIR)\15s\examples\accumulate\\" /Fd"$(BUILDDIR)\15s\examples\accumulate\vc80.pdb" /W3 /c /Zi /TP  /D_CRT_SECURE_NO_DEPRECATE 
"..\..\..\..\examples\manual\accumulate.cpp"
]
Creating command line "cl.exe @"$(BUILDDIR)\15s\examples\accumulate\RSP00000580885604.rsp" /nologo /errorReport:prompt"
Creating temporary file "$(BUILDDIR)\15s\examples\accumulate\RSP00000680885604.rsp" with contents
[
/OUT:"$(BUILDDIR)\15s\examples\accumulate.exe" /INCREMENTAL:NO /MANIFEST /MANIFESTFILE:"$(BUILDDIR)\15s\examples\accumulate\accumulate.exe.intermediate.manifest" /NODEFAULTLIB:"libcpmtd.lib" /DEBUG /PDB:"$(BUILDDIR)\15s\examples\accumulate.pdb" /SUBSYSTEM:CONSOLE   kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib "..\..\15s\lib\libstd15s.lib"
"..\..\15s\examples\accumulate\accumulate.obj"
]
Creating command line "link.exe @"$(BUILDDIR)\15s\examples\accumulate\RSP00000680885604.rsp" /NOLOGO /ERRORREPORT:PROMPT"
Creating temporary file "$(BUILDDIR)\15s\examples\accumulate\RSP00000780885604.rsp" with contents
[
/outputresource:"..\..\15s\examples\accumulate.exe;#1" /manifest
"..\..\15s\examples\accumulate\accumulate.exe.intermediate.manifest"
]
Creating command line "mt.exe @"$(BUILDDIR)\15s\examples\accumulate\RSP00000780885604.rsp" /nologo"
Creating temporary file "$(BUILDDIR)\15s\examples\accumulate\BAT00000880885604.bat" with contents
[
@echo Manifest resource last updated at %TIME% on %DATE% > "..\..\15s\examples\accumulate\mt.dep"
]
Creating command line """$(BUILDDIR)\15s\examples\accumulate\BAT00000880885604.bat"""
{noformat}

Notice that the last slash for the {{/Fo}} and {{/Fd}} options differs between the two versions of Visual Studio. I checked the project files and they are nearly identical, so VC is putting the slash into the path names. Same issue with Intel builds.

> [Windows] slashes in Windows pathnames in build logs
> ----------------------------------------------------
>
>                 Key: STDCXX-685
>                 URL: https://issues.apache.org/jira/browse/STDCXX-685
>             Project: C++ Standard Library
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 4.2.0
>            Reporter: Martin Sebor
>            Assignee: Travis Vitek
>            Priority: Trivial
>             Fix For: 4.2.2
>
>
> The Windows build logs are mixing slashes and backclashes in pathnames when linking library objects (see below). We should be consistent and use the same path separator everywhere.
> Build started: Project: .stdcxx, Configuration: 8s Optimized Static|Win32
> ...
> Creating command line "cmd.exe /c C:\DOCUME~1\batman\LOCALS~1\Temp\VadA21F.bat"
> Creating temporary file "C:\DOCUME~1\batman\LOCALS~1\Temp\RSPA222.bs" with contents
> [
> /c /O2 /I "$(TOPDIR)\include" /I "$(TOPDIR)\include\ansi" /I "$(BUILDDIR)\8s\include" /D "_MBCS" /FD /EHsc /MT /GS- /GR /Fo"$(BUILDDIR)\8s\src/" /W3 /nologo /Zi /Gd /D_CRT_SECURE_NO_DEPRECATE /Qvc8 /Qlocation,link,"C:\Program Files\Microsoft Visual Studio 8\VC\bin"
> ..\..\..\src\strtol.cpp
> ..\..\..\src\ti_time_get.cpp
> ..\..\..\src\locale_global.cpp
> ...
> ]
> Creating command line "icl.exe "@C:\DOCUME~1\batman\LOCALS~1\Temp\RSPA222.bs""
> Creating temporary file "C:\DOCUME~1\batman\LOCALS~1\Temp\RSPA225.bs" with contents
> [
> /OUT:"$(BUILDDIR)\8s\lib\libstd8s.lib" /nologo /NODEFAULTLIB:"libcpmt.lib"
> $(BUILDDIR)\8s\src/assert.obj
> $(BUILDDIR)\8s\src\atomic.obj
> $(BUILDDIR)\8s\src/bitset.obj
> $(BUILDDIR)\8s\src/catalog.obj
> ...
> $(BUILDDIR)\8s\src/version.obj
> $(BUILDDIR)\8s\src/wcodecvt.obj
> $(BUILDDIR)\8s\src/wctype.obj
> ]
> Creating command line "xilib.exe "@C:\DOCUME~1\batman\LOCALS~1\Temp\RSPA225.bs""
> -------

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.