Hi, Frankly I do not know who supports Boost.Build, but how long it'll stay broken? I can't say when it started, but ever since I started working on Boost.Test changes I experience constant problems. I can't believe I am the only one. 1. When you take boost trunk and go into Boost.Test build or test directory and try building using any toolset it immediately fails with: ..\..\..\libs\test\build\Jamfile.v2:110: in modules.load rule boost-install unknown in module Jamfile</.../trunk/libs/test/build>. .../trunk/tools/build/v2/build\project.jam:314: in load-jamfile .../trunk/tools/build/v2/build\project.jam:62: in project.load .../trunk/tools/build/v2/build\project.jam:766: in project.use .../trunk/tools/build/v2/build\project.jam:89: in load-used-projects .../trunk/tools/build/v2/build\project.jam:73: in load .../trunk/tools/build/v2/build\project.jam:115: in load-parent .../trunk/tools/build/v2/build\project.jam:464: in initialize .../trunk/tools/build/v2/build\project.jam:309: in load-jamfile .../trunk/tools/build/v2/build\project.jam:62: in load .../trunk/tools/build/v2/build\project.jam:115: in load-parent .../trunk/tools/build/v2/build\project.jam:464: in initialize .../trunk/tools/build/v2/build\project.jam:309: in load-jamfile .../trunk/tools/build/v2/build\project.jam:62: in load .../trunk/tools/build/v2/build\project.jam:168: in project.find .../trunk/tools/build/v2\build-system.jam:570: in load .../trunk\tools\build\v2/kernel\modules.jam:283: in import .../trunk\tools\build\v2\kernel\bootstrap.jam:142: in boost-build .../trunk\boost-build.jam:17: in module scope 2. Once I remove boost-install from Boost.Test Jamfile, I get bun of errors like this: ..\..\..\libs\test\src\compiler_log_formatter.cpp(16) : fatal error C1083: Cannot open include file: 'boost/test/impl/compiler_log_formatter.ipp': No such file or directory Essentially boost home directory is missing from include path. How come? 3. Once I add "<include>../../.." into requirements section I can build with msvc toolsets. Now I am trying to use gcc toolset on Windows. I have latest cygwin installation and I am getting these errors (lots of them): gcc.compile.c++ ..\..\..\libs\test\build\bin\gcc\debug\link-static\compiler_log_formatter.o "g++" ... # compilation line here Access is denied. Apparently g++ is not an executable anymore with cygwin. I am able to workaround this by adding using gcc : 4.5.3 : g++-4.exe ; into user-config.jam, but why Boost.Build can't figure this out and do I need to support this file now myself? 4. After the fix I am able to build dll based tests, but when I attempt to use static library version of Boost.Test I am getting: gcc.archive ..\..\..\libs\test\build\bin\gcc-4.5.3\ debug\link-static\libboost_unit_test_framework.a "/usr/i686-pc-cygwin/bin/ar.exe" rc .... # list of object files here "/usr/i686-pc-cygwin/bin/ranlib.exe" ... # lib here The system cannot find the path specified. The system cannot find the path specified. This one I do not know how to fix. So the situation is that I cannot test any static library based unit tests (as a side note, this inability was the cause of crashes which interrupted trunk testing month ago). I addition whenever I want to check in my local changes to Jamfile (excluding hacks which I actually do not want to check in) it is rather annoying process. Any help would be appreciated, Gennadiy
AMDG On 11/07/2011 02:52 AM, Gennadiy Rozental wrote:
Frankly I do not know who supports Boost.Build, but how long it'll stay broken? I can't say when it started, but ever since I started working on Boost.Test changes I experience constant problems. I can't believe I am the only one.
1. When you take boost trunk and go into Boost.Test build or test directory and try building using any toolset it immediately fails with:
..\..\..\libs\test\build\Jamfile.v2:110: in modules.load rule boost-install unknown in module Jamfile</.../trunk/libs/test/build>.
<snip>
This error is specific to Boost.Test, and only occurs when you run bjam in the Boost.Test subdirectories. I have a fix, but I need to make sure that it doesn't break anything else before I commit it, since it changes the loading of Jamfiles.
2. Once I remove boost-install from Boost.Test Jamfile, I get bun of errors like this:
..\..\..\libs\test\src\compiler_log_formatter.cpp(16) : fatal error C1083: Cannot open include file: 'boost/test/impl/compiler_log_formatter.ipp': No such file or directory
Essentially boost home directory is missing from include path. How come?
It's the same problem as (1).
<snip> Apparently g++ is not an executable anymore with cygwin. I am able to workaround this by adding
using gcc : 4.5.3 : g++-4.exe ;
into user-config.jam, but why Boost.Build can't figure this out and do I need to support this file now myself?
I don't think there's much in the way of testing on Cygwin now. It should be easy to add the name g++-4 into the mix that Boost.Build searches for.
4. After the fix I am able to build dll based tests, but when I attempt to use static library version of Boost.Test I am getting:
gcc.archive ..\..\..\libs\test\build\bin\gcc-4.5.3\ debug\link-static\libboost_unit_test_framework.a
"/usr/i686-pc-cygwin/bin/ar.exe" rc .... # list of object files here "/usr/i686-pc-cygwin/bin/ranlib.exe" ... # lib here
The system cannot find the path specified. The system cannot find the path specified.
Do these two executables exist?
This one I do not know how to fix. So the situation is that I cannot test any static library based unit tests (as a side note, this inability was the cause of crashes which interrupted trunk testing month ago). I addition whenever I want to check in my local changes to Jamfile (excluding hacks which I actually do not want to check in) it is rather annoying process.
In Christ, Steven Watanabe
Steven Watanabe <watanabesj <at> gmail.com> writes:
On 11/07/2011 02:52 AM, Gennadiy Rozental wrote:
..\..\..\libs\test\build\Jamfile.v2:110: in modules.load rule boost-install unknown in module Jamfile</.../trunk/libs/test/build>.
This error is specific to Boost.Test, and only occurs when you run bjam in the Boost.Test subdirectories.
How come. What so specific about my Jamfiles?
I have a fix, but I need to make sure that it doesn't break anything else before I commit it, since it changes the loading of Jamfiles.
DO you mean changes in Boost.Build?
I don't think there's much in the way of testing on Cygwin now. It should be easy to add the name g++-4 into the mix that Boost.Build searches for.
Name g++ exists in a path. It's just a cygwin symlink. it needs to be made aaware about correct name to use instead (depending on which version of gcc is installed. Interestingly it does not work even if I start bjam from cygwin's bash shell (Usually I use shell in Far Manager, which is essentially a Windows shell)
gcc.archive ..\..\..\libs\test\build\bin\gcc-4.5.3\ debug\link-static\libboost_unit_test_framework.a
"/usr/i686-pc-cygwin/bin/ar.exe" rc .... # list of object files here "/usr/i686-pc-cygwin/bin/ranlib.exe" ... # lib here
The system cannot find the path specified. The system cannot find the path specified.
Do these two executables exist?
They do, but the same way as with g++ they are symbolic links. Gennadiy
AMDG On 11/07/2011 10:08 AM, Gennadiy Rozental wrote:
Steven Watanabe <watanabesj <at> gmail.com> writes:
On 11/07/2011 02:52 AM, Gennadiy Rozental wrote:
..\..\..\libs\test\build\Jamfile.v2:110: in modules.load rule boost-install unknown in module Jamfile</.../trunk/libs/test/build>.
This error is specific to Boost.Test, and only occurs when you run bjam in the Boost.Test subdirectories.
How come. What so specific about my Jamfiles?
You have a Jamfile in libs/test. This shouldn't cause a problem, but it does.
I have a fix, but I need to make sure that it doesn't break anything else before I commit it, since it changes the loading of Jamfiles.
DO you mean changes in Boost.Build?
Yes.
I don't think there's much in the way of testing on Cygwin now. It should be easy to add the name g++-4 into the mix that Boost.Build searches for.
Name g++ exists in a path. It's just a cygwin symlink. it needs to be made aaware about correct name to use instead (depending on which version of gcc is installed.
Interestingly it does not work even if I start bjam from cygwin's bash shell (Usually I use shell in Far Manager, which is essentially a Windows shell)
Aha. It doesn't matter what shell you run bjam from. You apparently compiled as a Windows executable, so it can't execute cygwin symlinks. You can try whether a cygwin build of bjam works.
gcc.archive ..\..\..\libs\test\build\bin\gcc-4.5.3\ debug\link-static\libboost_unit_test_framework.a
"/usr/i686-pc-cygwin/bin/ar.exe" rc .... # list of object files here "/usr/i686-pc-cygwin/bin/ranlib.exe" ... # lib here
The system cannot find the path specified. The system cannot find the path specified.
Do these two executables exist?
They do, but the same way as with g++ they are symbolic links.
In Christ, Steven Watanabe
Gennadiy Rozental wrote:
Hi,
Frankly I do not know who supports Boost.Build, but how long it'll stay broken? I can't say when it started, but ever since I started working on Boost.Test changes I experience constant problems. I can't believe I am the only one.
Did you file any issues in Trac for this one? It is obviously hard to fix a problem unless it is reported and Trac is the canonical place to report problems. Thanks, -- Vladimir Prus CodeSourcery / Mentor Graphics +7 (812) 677-68-40
participants (3)
-
Gennadiy Rozental -
Steven Watanabe -
Vladimir Prus