Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ar response files under MinGW contain paths with backslashes, which fails #352

Closed
pdimov opened this issue Dec 18, 2023 · 0 comments
Closed
Labels
bug Something isn't working

Comments

@pdimov
Copy link
Contributor

pdimov commented Dec 18, 2023

As reported in boostorg/url#779, the gcc.archive action creates response files in which the paths use backslashes as the separator, which the MinGW ar misinterprets as escapes.

The fix is to change the :E part of this line

"$(.AR)" $(AROPTIONS) $(.ARFLAGS) "$(<)" @($(<[-1]:T).rsp:O=FC:<=@":>=":E="$(>)")

from :E="$(>)" to :E="$(>:T)".

(I see that this has been reported before as #342.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant