Re: Meaning of gcc-mingw toolset
Steven Watanabe via Boost-build <[email protected]> Sun, 19 Apr 2020 05:10:46 -0600
| Newsgroups | gmane.comp.lib.boost.build |
|---|---|
| Organization | Providere Consulting, Inc. |
| Message-ID | <[email protected]> |
AMDG On 4/16/20 9:19 AM, [email protected] wrote: > >> On 4/15/20 4:45 AM, Edward Diener via Boost-build wrote: >>> In the multiprecision testing jamfile there is a line which has the >>> requirement: >>> >>> <toolset>gcc-mingw:<cxxflags>-Wa,-mbig-obj >>> >>> <snip> >> What is the path component for the toolset? It should be gcc-mingw-nnn. I meant the name used in the target path: .../bin.v2/.../gcc-nnn/... >> Otherwise the detection for mingw isn't working. >> Also, I recall that there used to be problems if you have both mingw and non- >> mingw versions of gcc. I don't remember whether that was ever fixed. > > Sadly I can't get this to work. Perhaps I have misunderstood what you suggested. > My suggestion was out-dated. There is no longer a mingw feature. Embarrassingly enough, I was the one who removed it. Instead, use <toolset>gcc-10.0.1,<target-os>windows:<cxxflags>.... I thought I PRed all the uses of mingw before I made the changes in Boost.Build, but I must have missed this one. > [ run floating_point_examples.cpp no_eh_eg_support : : : <toolset>gcc-mingw-10.0.1:<cxxflags>\"-Wa,-mbig-obj\" ] # See note above. > In Christ, Steven Watanabe _______________________________________________ Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build