Opened 11 years ago
Last modified 10 years ago
#6350 new Bugs
MINGW Build missing mingw.jam
Reported by: | anonymous | Owned by: | Vladimir Prus |
---|---|---|---|
Milestone: | Boost 1.49.0 | Component: | build |
Version: | Boost 1.48.0 | Severity: | Problem |
Keywords: | mingw build bootstrap | Cc: |
Description
If I try to build boost on Windows7 with mingw-shell:
./bootstrap.sh --toolset=mingw
then b2 and bjam will be build successfully, but the call
./b2
fails with
mingw.jam: No such file or directory d:/extswrc/boost/tools/build/v2/build\toolset.jam:38: in toolset.using rule mingw.init unknown in module toolset. Windows, these are static d:/extswrc/boost/tools/build/v2/build\project.jam:888: in using project-config.jam:12: in modules.loadsing shared runtime. On Linux, these d:/extswrc/boost/tools/build/v2\build-system.jam:257: in load-config d:/extswrc/boost/tools/build/v2\build-system.jam:423: in load-configuration-files d:/extswrc/boost/tools/build/v2\build-system.jam:555: in load d:\extswrc\boost\tools\build\v2/kernel\modules.jam:283: in import d:\extswrc\boost\tools\build\v2\kernel\bootstrap.jam:142: in boost-build d:\extswrc\boost\boost-build.jam:17: in module scopeg
if I copy the gcc.jam to mingw.jam and rename gcc into mingw in mingw.jam then I can build boost with b2. So I would suggest to add a mingw.jam file to tools/build/v2/tools.
Attachments (2)
Change History (5)
by , 11 years ago
comment:3 by , 10 years ago
I am afraid this is wrong approach -- gcc.jam should handle gcc on all platforms, including windows.
The right way would be to make either make "boostrap.sh --toolset=mingw" select "gcc" and Boost.Build toolset or just make "bootstrap.sh --toolset=gcc" work.
Note:
See TracTickets
for help on using tickets.
mingw jam file