-
Notifications
You must be signed in to change notification settings - Fork 58
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
Boost.Build needs to upstream a mingw-w64 patch for Boost.URL #95
Comments
I think, this cannot be avoided really. It's just a list of object modules to link, and it has most of them... |
Perhaps - but somehow, every other Boost library hasn't triggered this problem. |
That's because of the |
I suppose that's fair, so Boost.Build should be fixed - either the command-line length hack, or a true fix to avoid backslash escaping. |
boost-fix-raw_maxline.patch works around #95.
This is boostorg/url#779 and bfgroup/b2#352, which is fixed with bfgroup/b2@2474be5. |
Thank you!! 😻 |
boost-fix-raw_maxline.patch works around StephanTLavavej#95.
The msys2/MINGW-packages project has a patch: https://github.com/msys2/MINGW-packages/blob/ca4e304acefff6f0e145a14c6419d3fd78bcfa2e/mingw-w64-boost/0012-allow-longer-path-on-mingw-w64.patch @AndrewSav brought this to my attention in #90 (comment) and explained:
This should be upstreamed to Boost.Build, which will allow it to handle Boost.URL on mingw-w64. The patch's content looks reasonable to me - it discards the pre-XP codepaths (Boost.Build really doesn't need to worry about someone attempting to build Boost on such incredibly ancient systems), then it allows toolsets targeting Windows (as this is execnt.cpp) that aren't imitating MSVC (i.e. that aren't defining
_MSC_VER
) to use longer command lines. This seems like a reasonable heuristic to distinguish "mingw-w64 via MSYS2" from "MSVC via cmd".Alternatively, something in Boost.Build could be fixed to properly handle backslashes when using response files on MSYS2.
Alternatively, Boost.URL could be changed to avoid constructing such horrifically long command lines (in 1.84.0, it is the only Boost library to be affected by this problem).
The text was updated successfully, but these errors were encountered: