Boost C++ Libraries: Ticket #3496: Problems in latest release changes "--without and --with options" https://svn.boost.org/trac10/ticket/3496 <p> hello </p> <p> I was using boost_1_33_1 and i upgraded the same to boost_1_40_0 version. But during compilation, i am getting the following error. </p> <p> "error: both --with-&lt;library&gt; and --without-&lt;library&gt; specified" </p> <p> in my command line i have given ./bjam -sTOOLS=vc-8_0 toolset=msvc --with-filesystem --without-python </p> <p> if i remove --without-python, it is giving warning as "No python installation configured and auto configuration failed." </p> <p> but it was working in old (boost_1_33_1) version. The reason i found is the new validation in "jamroot" file as follows. </p> <p> if $(with-parameter) &amp;&amp; $(without-parameter) { </p> <blockquote> <p> ECHO "error: both --with-&lt;library&gt; and --without-&lt;library&gt; specified" ; EXIT ; </p> </blockquote> <p> } </p> <p> can you please help me in this regard? </p> <p> Thanks in advance, Raghu </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/3496 Trac 1.4.3 Vladimir Prus Sun, 18 Oct 2009 07:26:22 GMT <link>https://svn.boost.org/trac10/ticket/3496#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/3496#comment:1</guid> <description> <p> Just ignore the warning -- it's emitted regardless of whether Python is built. There's a separate action item to suppress this warning when Python is not built. </p> <p> Does this answer your question? </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Vladimir Prus</dc:creator> <pubDate>Mon, 09 Nov 2009 08:06:04 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/3496#comment:2 https://svn.boost.org/trac10/ticket/3496#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">invalid</span> </li> </ul> <p> I am gonna assume that the problem is now solved. </p> Ticket