#4743 closed Bugs (invalid)
bjam endless command loop (windows)
| Reported by: | anonymous | Owned by: | Bryce Adelstein Lelbach |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | Building Boost |
| Version: | Boost.Jam 3.1.18 | Severity: | Cosmetic |
| Keywords: | Cc: |
Description
In my ignorance I created a python.bat file with bjam commands to build Boost.Python in the main boost folder. This file then seemed to be executed by any bjam command, even --clean. As it contained the build commands an endless command loop was created rendering my PC quite unusable very fast. Renaming the .bat fixed the issue, but I don't know if this behaviour is desired. It cause quite a bit of trouble for me.
Change History (5)
comment:1 by , 12 years ago
| Owner: | set to |
|---|
comment:2 by , 12 years ago
The configuration for Boost.Python invokes the Python interpreter. If running "python" doesn't do this, it's bound to cause trouble.
comment:3 by , 12 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Right -- it does not seem we can do anything if 'python' does not work.
comment:4 by , 10 years ago
Too bad this was closed without at least detecting the absense of python during the compilation phase.
Compiling on an old laptop I expected it to take awhile..... by the 2nd day and bjam target #1200 I realized it was looping.
Apparently a few subtle "python not found" errors at the BEGINNING of the output was all I had to go on.
My god simply check for python and if it's not there abort or display some kind of error message! My machine just sat at 100% CPU for 2 days wasting all kinds of energy for no reason at all.
comment:5 by , 10 years ago
The problem in the original report was not absense of Python. It was script called python.bat that runs bjam. This is hardly a situation we can easily detect.
If you situation is different, could you file a separate issue?
Please provide a test case/patch, if possible. Without that, it'll be hard for us to verify this...