I am receiving the following on a Solaris system when using: jam -sBOOST_ROOT=. -sTOOLS=gcc status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:368: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope {...above repeated many times...} Unable to load Boost.Build, it seems that the build system files were located, but the build system is not defined. Attempted to use, as the bootstrap, this file: ./tools/build/boost-build.jam. This means that even though that file was loaded it either failed to directly load the build system files, or it failed to specify where to find and load the files by calling the 'build-system [path] ;' rule. Please consult the documentation at 'http://www.boost.org'. What am I doing wrong? Any help is appreciated.
"cs_jritchie"
I am receiving the following on a Solaris system when using:
jam -sBOOST_ROOT=. -sTOOLS=gcc
status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:368: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope
{...above repeated many times...}
Unable to load Boost.Build, it seems that the build system files were located, but the build system is not defined. Attempted to use, as the bootstrap, this file: ./tools/build/boost-build.jam. This means that even though that file was loaded it either failed to directly load the build system files, or it failed to specify where to find and load the files by calling the 'build-system [path] ;' rule. Please consult the documentation at 'http://www.boost.org'.
What am I doing wrong? Any help is appreciated.
[please post any follow-ups to jamboost@yahoogroups.com] It looks to me as though you're trying to use a new version of Jam on an older Boost CVS state. We removed the FAIL_EXPECTED rule from the core Jam when it was proved to be unneeded, sometime after the release of 1.27. However, I can see that it might be a mistake to break backward compatibility in this way. Opinions? -Dave
--- In Boost-Users@y..., "David Abrahams"
"cs_jritchie"
wrote in message news:ab8vuh+uves@e... I am receiving the following on a Solaris system when using:
jam -sBOOST_ROOT=. -sTOOLS=gcc
status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:368: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope
{...above repeated many times...}
Unable to load Boost.Build, it seems that the build system files
located, but the build system is not defined. Attempted to use, as the bootstrap, this file: ./tools/build/boost-build.jam. This means that even though that file was loaded it either failed to directly load the build system files, or it failed to specify where to find and load the files by calling the 'build-system [path] ;' rule. Please consult the documentation at 'http://www.boost.org'.
What am I doing wrong? Any help is appreciated.
[please post any follow-ups to jamboost@y...]
It looks to me as though you're trying to use a new version of Jam on an older Boost CVS state. We removed the FAIL_EXPECTED rule from the core Jam when it was
unneeded, sometime after the release of 1.27. However, I can see
were proved to be that it
might be a mistake to break backward compatibility in this way. Opinions?
-Dave
I am new to Boost, and only downloaded Jam and Boost yesterday (Monday, May 6, 2002). Perhaps the removal of FAIL_EXPECTED wasn't complete. Here are the links to the files that I downloaded: www.boost.org/boost_all.tar.gz http://boost.sourceforge.net/jam-executables/bin.solaris/jam.gz I also tried again with 'http://boost.sourceforge.net/release/boost_1_27_0.tar.gz' and got the same results...
"cs_jritchie"
I am new to Boost, and only downloaded Jam and Boost yesterday (Monday, May 6, 2002). Perhaps the removal of FAIL_EXPECTED wasn't complete. Here are the links to the files that I downloaded:
www.boost.org/boost_all.tar.gz http://boost.sourceforge.net/jam-executables/bin.solaris/jam.gz
I also tried again with 'http://boost.sourceforge.net/release/boost_1_27_0.tar.gz' and got the same results...
Agggh, yes. This is due to the fact that we updated the jam executable on the website after FAIL_EXPECTED was removed in the CVS... So the executable you have is compatible with the current CVS state but not with the 1.27.0 release. We'll have that fixed in a week at most. In the meantime you can do one of the following: 1. Use the current CVS state of boost (recommended, though you might need step 2 as well) 2. Rebuild your jam from the sources in $(BOOST_ROOT)/tools/build/jam_src by invoking make there. Sorry for the rough start, Dave
--- In Boost-Users@y..., "David Abrahams"
"cs_jritchie"
wrote in message news:ab96ac+56ob@e... I am new to Boost, and only downloaded Jam and Boost yesterday (Monday, May 6, 2002). Perhaps the removal of FAIL_EXPECTED
wasn't
complete. Here are the links to the files that I downloaded:
www.boost.org/boost_all.tar.gz http://boost.sourceforge.net/jam-executables/bin.solaris/jam.gz
I also tried again with 'http://boost.sourceforge.net/release/boost_1_27_0.tar.gz' and got the same results...
Agggh, yes. This is due to the fact that we updated the jam executable on the website after FAIL_EXPECTED was removed in the CVS... So the executable you have is compatible with the current CVS state but not with the 1.27.0 release. We'll have that fixed in a week at most.
In the meantime you can do one of the following:
1. Use the current CVS state of boost (recommended, though you might need step 2 as well) 2. Rebuild your jam from the sources in $(BOOST_ROOT)/tools/build/jam_src by invoking make there.
Sorry for the rough start, Dave
I was able to rebuild jam from the source and then able to successfully build the Boost libraries. Thanks for the help. Jamie
participants (2)
-
cs_jritchie
-
David Abrahams