#13458 closed Bugs (worksforme)
'cl' is not recognized as an internal or external command, operable program or batch file. Failed to build Boost.Jam build engine. Please consult bjam.log for furter diagnostics.
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | None |
| Version: | Boost 1.41.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
'cl' is not recognized as an internal or external command, operable program or batch file.
Failed to build Boost.Jam build engine. Please consult bjam.log for furter diagnostics.
Change History (4)
comment:1 by , 5 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
comment:2 by , 5 years ago
FWIW, something similar happened to me as well, when I tried to run b2.exe from a VS Command Prompt: I could run cl.exe from the command line, but b2 was not able to invoke it.
The actual source of the problem was that b2 was an old version of a b2_vcvarsall.bat file that was still in my temp directory and was loading an environment referring to a version of VS that was not available anymore.
Removing that files fixed the issue for me.
comment:3 by , 5 years ago
I would also suggest looking for a user-config.jam file and see if the location of the compiler was overridden.
comment:4 by , 4 years ago
We had similar problem on Windows and modern boost version (i.e. 1.65) - clearing b2_* files from %temp% helped. Without this page we wouldn't be able to compile it. Thanks for helping, and I think such problem should be fixed in so well known (and one of most used) software.
Try running b2.exe from inside a Visual Studio command prompt.