Doug Gregor <[EMAIL PROTECTED]> writes: > On Jul 5, 2004, at 6:13 PM, David Abrahams wrote: >> Well y'know I have bash, but the script specifies sh. > > The next version will specify bash. Have /bin/sh really be bash always > gets me.
Not every system has bash, though :( >> ...found 59 targets... >> ...updating 2 targets... >> xslt-xsltproc >> ../../../../bin.v2/tools/build/v2/doc/gcc-3.2/debug/userman.docbook >> src/userman.xml:3: warning: failed to load external entity >> "http://www.boost.org/tools/boostbook/dtd/boostbook.dtd"; >> "http://www.boost.org/tools/boostbook/dtd/boostbook.dtd";> >> > > "rm catalog.xml" and then bjam --v2 again. This is the everlasting > catalog.xml issue, for which we haven't found a suitable solution in > Jam; IFUSED would have worked, but see Hah! It worked! Thanks. Here's another problem: One of the files I'm working on contains: <para><emphasis role="bold">N.B.</emphasis> When <command>bjam</command> is invokedfrom anywhere in the Boost directory tree <emphasis>other than</emphasis> the Boost.Build root and its subdirectories, <ulink url="../../tools/build">Boost.Build v1</ulink> is used by default. To overide the default and use Boost.Build v2, you have to add the <option>--v2</option> command line option to all <command>bjam</command> invocations.</para> The problem is that it can be built both from $BOOST_ROOT/doc and from $BOOST_ROOT/tools/build/v2/doc. The ulink can only be right in one of those places. Solutions? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
