Closed pdimov closed 8 months ago
As reported in https://github.com/boostorg/url/issues/779, the gcc.archive action creates response files in which the paths use backslashes as the separator, which the MinGW ar misinterprets as escapes.
gcc.archive
ar
The fix is to change the :E part of this line
:E
https://github.com/bfgroup/b2/blob/5dca2965cb083060137498d6581fcbfb9522cfbc/src/tools/gcc.jam#L1094
from :E="$(>)" to :E="$(>:T)".
:E="$(>)"
:E="$(>:T)"
(I see that this has been reported before as https://github.com/bfgroup/b2/issues/342.)
As reported in https://github.com/boostorg/url/issues/779, the
gcc.archiveaction creates response files in which the paths use backslashes as the separator, which the MinGWarmisinterprets as escapes.The fix is to change the
:Epart of this linehttps://github.com/bfgroup/b2/blob/5dca2965cb083060137498d6581fcbfb9522cfbc/src/tools/gcc.jam#L1094
from
:E="$(>)"to:E="$(>:T)".(I see that this has been reported before as https://github.com/bfgroup/b2/issues/342.)