David Abrahams wrote:

Try building with an NT (not Cygwin) build of bjam from within a regular NT command shell.

Thanks for your reply. When I try that, I get output looking like below. It says that the /Ze and /Za command-line options are incompatible. Do you know how I can change that? C:\hack\Cygwin\home\martin\source\libs\boost_1_31_0>bjam "-sMSVC_ROOT=c:\program files\hack\microsoft visual studio\vc98" --"prefix=c:\program files\hack\" -sTOOLS=msvc --builddir=..\boost_msvc_build install --------------------------------------------------------------------- skipping Boost.Python library build due to missing or incorrect configuration couldn't find Python.h in "c:/tools/python/include" You can configure the location of your python installation by setting: PYTHON_ROOT - currently "c:/tools/python" PYTHON_VERSION - The 2-part python Major.Minor version number (e.g. "2.2", NOT "2.2.1") - currently "2.2" The following are automatically configured from PYTHON_ROOT if not otherwise set: PYTHON_LIB_PATH - path to Python library object; currently "c:/tools/python/libs" --------------------------------------------------------------------- ...found 5266 targets... ...updating 693 targets... vc-C++ bin\boost\libs\date_time\build\boost_date_time.dll\vc7.1\debug\greg_month .obj Command line error D2016 : '/Ze' and '/Za' command-line options are incompatible "cl" /Zm800 -nologo -GX -c -DBOOST_DATE_TIME_POSIX_TIME_STD_CONFIG -DBOOST _ALL_DYN_LINK=1 /Z7 /Od /Ob0 /GX /GR /MDd /Op /Zc:forScope /Zc:wchar_t -I"bin \boost\libs\date_time\build" -I"C:\HACK\Cygwin\home\martin\source\libs\boost_1_ 31_0" -I"C:\PROGRA~1\HACK\MICROS~1\VC98\include" -Fo"bin\boost\libs\date_time\ build\boost_date_time.dll\vc7.1\debug\greg_month.obj" -Tp"C:\HACK\Cygwin\home\m artin\source\libs\boost_1_31_0\libs\date_time\build\../src/gregorian/greg_month. cpp" ...failed vc-C++ bin\boost\libs\date_time\build\boost_date_time.dll\vc7.1\debug\ greg_month.obj... vc-C++ bin\boost\libs\date_time\build\boost_date_time.dll\vc7.1\debug\greg_weekd ay.obj Command line error D2016 : '/Ze' and '/Za' command-line options are incompatible

At Monday 2004-09-27 17:08, you wrote:

Martin M writes:

...

Thanks for your reply. When I try that, I get output looking like below. It says that the /Ze and /Za command-line options are incompatible. Do you know how I can change that?

<snip>

...

...found 5266 targets... ...updating 693 targets... vc-C++ bin\boost\libs\date_time\build\boost_date_time.dll\vc7.1\debug\greg_month .obj Command line error D2016 : '/Ze' and '/Za' command-line options are incompatible

"cl" /Zm800 -nologo -GX -c -DBOOST_DATE_TIME_POSIX_TIME_STD_CONFIG -DBOOST _ALL_DYN_LINK=1 /Z7 /Od /Ob0 /GX /GR /MDd /Op /Zc:forScope /Zc:wchar_t -I"bin

\boost\libs\date_time\build" -I"C:\HACK\Cygwin\home\martin\source\libs\boost_1_

...

31_0" -I"C:\PROGRA~1\HACK\MICROS~1\VC98\include" -Fo"bin\boost\libs\date_time\

build\boost_date_time.dll\vc7.1\debug\greg_month.obj" -Tp"C:\HACK\Cygwin\home\m

...

artin\source\libs\boost_1_31_0\libs\date_time\build\../src/gregorian/greg_month.

...

cpp"

I have absolutely no clue. As you can see for yourself, neither '/Ze' nor '/Za' appear in the command line. Jeff, do you have any ideas?

there is a CL environment variable that may be messing things up.

-- Dave Abrahams Boost Consulting http://www.boost-consulting.com

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

Stephen Jackson wrote:

...

Command line error D2016 : '/Ze' and '/Za' command-line options are incompatible

I have seen reports of the above error arising from confusion between compiler versions. If I am using MSVC++ 6 and try to build a 7.1 target with: bjam -sTOOLS=vc7.1 then I get exactly the same error.

I did have some odd references to MS Visual Studio .NET in the error output from bjam. That's probably what caused the error. I don't know where that came from, since I don't have .NET installed, but after a reboot and a bit of extra fiddling it all seems to work. Thank you all for your time. / martin