May 2010 - Boost-users - lists.preview.boost.org

Auto dispatch metaprogramming tricks
by Alexander Lamaison 24 May '10

24 May '10

I would like to dispatch messages to a class based simply on the *presence* of a message handler method. Currently, the classes maintain an MPL vector of the messages they handle and must implement a on(message<MESSAGE_ID>) method for each one. The dispatcher uses this compile-time list to build the dispatching code. This means the information is maintained twice and may fall out of sync (e.g. adding the handler but forgetting to update the message vector. Are there any template metaprogramming tricks I can employ to dispatch the message to a handler method if it exists and the default handler otherwise? All this information is available at compile time. The question is are templates are powerful enough to make use of it? Many thanks. Alex

7 18

boost::reg_expression and basic_regex
by Senthil Nathan 24 May '10

24 May '10

Hi, I have been using the regular expressions with the older version of boost::regex, But with the latest version I'm getting the below error. I understand reg_expression is deprecated and need to use basic_regex. But even with that, its the same error. Any ideas on this, would be more useful. typedef boost::reg_expression<char, boost::c_regex_traits<char>, ntl::list_alloc<char> > Exp_type; ../../../include/expr/ExprEngine.h:38: error: wrong number of template arguments (3, should be 2) ../../../include/boost/regex/v4/basic_regex.hpp:597: error: provided for 'template<class charT, class traits> class boost::reg_expression' Thanks rsennat

2 1

Help on creating a custom InputIterator for boost graph adjacency_list()
by Cedric Laczny 24 May '10

24 May '10

Hi, I have a graph with quite some information stored in its vertices and edges. Now I would like to perform some analyses on the general overall topology of the graph. Therefore I don't need this "big graph" but only a graph that has the same number of nodes and matching edges to the "big graph". To this end, I wanted to use the adjacency_list() constructor together with an EdgeIterator that models the InputIterator so the routines of the boost-graph library would take care of creating the new "simple graph", which indeed would be a nice solution. However, I just don't get it how to program an EdgeIterator with the following constraints (taken from http://www.boost.org/doc/libs/1_43_0/libs/graph/doc/adjacency_list.html) The EdgeIterator must be a model of InputIterator. The value type of the EdgeIterator must be a std::pair, where the type in the pair is an integer type. Here's what I experimented with so far: <--- Code ---> template< class EdgeIterator, class Edge > class MyEdgeIterator// : public input_iterator< std::pair<int, int> > { public: MyEdgeIterator() {}; MyEdgeIterator(EdgeIterator& rhs) : actual_edge_it_(rhs) {}; MyEdgeIterator(const MyEdgeIterator& to_copy) {}; bool operator==(const MyEdgeIterator& to_compare) { return actual_edge_it_ == to_compare.actual_edge_it_; } bool operator!=(const MyEdgeIterator& to_compare) { return !(*this == to_compare); } Edge operator*() const { return *actual_edge_it_; } const MyEdgeIterator* operator->() const; MyEdgeIterator& operator ++() { ++actual_edge_it_; return *this; } MyEdgeIterator operator ++(int) { MyEdgeIterator<EdgeIterator, Edge> tmp = *this; ++*this; return tmp; } private: EdgeIterator& actual_edge_it_; } <--- Code-End ---> Especially, I'm having trouble with the fact that the EdgeIterator must return a pair of the vertex indices that the actual edge "points to". I think that this must include something like get(vertex_index_t, adjacency_list(...), source(*EdgeIterator, adjacency_list(...)). But this would mean that e.g. MyEdgeIterator would additionally need the vertex- property map of vetex indices. This seems a bit too much information packed into this one, small iterator. Thank you. Best regards, Cedric

3 6

[BGL] What's the problem when the dijkstra_shortest_paths is used with stanford_graph
by smallpang smallpang 24 May '10

24 May '10

dear everyone I want to construct multicast tree base on the network topology generated by the stanford graph. The source code below can run without error, and have the right output: *The file is open! m:28 n:10 * But when I add the algrithom dijkstra_shortest_paths. The error messages show as below: *Description Resource Path Location Type no matching function for call to ‘num_vertices(Graph* const&)’ MulticastTree2 line 190, external location: /usr/include/boost/graph/dijkstra_shortest_paths.hpp C/C++ Problem Description Resource Path Location Type no matching function for call to ‘out_edges(Vertex*&, Graph* const&)’ MulticastTree2 line 76, external location: /usr/include/boost/graph/breadth_first_search.hpp C/C++ Problem Description Resource Path Location Type no matching function for call to ‘vertices(Graph* const&)’ MulticastTree2 line 375, external location: /usr/include/boost/graph/dijkstra_shortest_paths.hpp C/C++ Problem* I find the num_vertices\out_edges\vertices are redefined in the stanford_graph.hpp. So I change the order of the include files as below: *#include <boost/graph/stanford_graph.hpp> #include <boost/graph/dijkstra_shortest_paths.hpp>* The errors above disappear, and New errors come up: *Description Resource Path Location Type ‘g’ was not declared in this scope MulticastTree2 line 408, external location: /usr/include/boost/graph/named_function_params.hpp C/C++ Problem Description Resource Path Location Type ‘t’ was not declared in this scope MulticastTree2 line 408, external location: /usr/include/boost/graph/named_function_params.hpp C/C++ Problem Description Resource Path Location Type ‘u’ was not declared in this scope MulticastTree2 line 463, external location: /usr/include/boost/pending/relaxed_heap.hpp C/C++ Problem Description Resource Path Location Type expected ‘,’ or ‘...’ before ‘.’ token MulticastTree2 line 402, external location: /usr/include/boost/graph/named_function_params.hpp C/C++ Problem Description Resource Path Location Type expected initializer before ‘.’ token MulticastTree2 line 462, external location: /usr/include/boost/pending/relaxed_heap.hpp C/C++ Problem* It's confusing for me, can you tell me what's the problem is and any way i can try to solve the problems above. Thank you. source code: *#include <boost/config.hpp> #include <iostream> #include <string> #include <fstream> #include <boost/graph/graph_traits.hpp> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/dijkstra_shortest_paths.hpp> #include <boost/graph/stanford_graph.hpp> using namespace boost; int main(int argc, char *argv[]) { Graph* inputG; char *in_filename = "r10-0.gb"; inputG = restore_graph(in_filename); if (inputG){ std::cout << "The file is open!" << "\n"; std::cout << "m:" << inputG->m << "\n"; std::cout << "n:" << inputG->n << "\n"; } else return 0; graph_traits<Graph*>::vertex_descriptor s = *boost::vertices(inputG).first; typedef property_map<Graph*, z_property<long> >::type Distance; Distance d = get(z_property<long>(), inputG); typedef property_map<Graph*, w_property<Vertex*> >::type Parent; Parent p = get(w_property<Vertex*>(), inputG); // dijkstra_shortest_paths(inputG, s, // predecessor_map(get(w_property<Vertex*>(), inputG)). // distance_map(get(z_property<long>(), inputG)). // weight_map(get(edge_length_t(), inputG)) // ); gb_recycle(inputG); return 1; }*

2 2

'Undefined symbols' error when building Mira Groupware on Mac OS X
by Max Bossino 23 May '10

23 May '10

Hi all, I'm having some trouble compiling an app (Mira Groupware of http://miragroupware.org) which uses the Boost 1.42 libraries, on Mac OS X. It's exiting during the 'make' stage with an error about 'Undefined symbols'. I would really appreciate it if someone could offer a helping hand! Judging by the output of CMake, the Boost files are installed and can be found (I've cropped the output to highlight the bit about Boost): ----- MBP:build Max$ cmake ./ -- The C compiler identification is GNU -- The CXX compiler identification is GNU [...] -- Boost version: 1.42.0 -- Found the following Boost libraries: -- thread -- signals -- system -- filesystem ** Mira found Boost version 104200 [...] -- Configuring done -- Generating done -- Build files have been written to: /Users/Max/Documents/Projects/Mira/Branches/build ----- However, this is what happens while trying to 'make' the Server: ----- MBP:mirs Max$ make [ 6%] Built target mira Scanning dependencies of target Files-utility [ 13%] Building CXX object CMakeFiles/Files-utility.dir/src/utilities/files/files.cpp.o [ 20%] Building CXX object CMakeFiles/Files-utility.dir/src/utilities/files/FileUtility.cpp.o [ 26%] Building CXX object CMakeFiles/Files-utility.dir/src/utilities/files/FileServer.cpp.o [ 33%] Building CXX object CMakeFiles/Files-utility.dir/src/utilities/files/FileConnection.cpp.o Linking CXX shared library bin/libFiles-utility.dylib Undefined symbols: "boost::filesystem::detail::remove_api(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)", referenced from: bool boost::filesystem::detail::remove_aux<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >(boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> const&, boost::filesystem::file_status)in FileUtility.cpp.o "boost::system::get_system_category()", referenced from: boost::asio::error::get_system_category() in files.cpp.o boost::system::error_code::error_code()in files.cpp.o __static_initialization_and_destruction_0(int, int)in files.cpp.o __static_initialization_and_destruction_0(int, int)in files.cpp.o boost::system::error_code::error_code()in FileUtility.cpp.o __static_initialization_and_destruction_0(int, int)in FileUtility.cpp.o __static_initialization_and_destruction_0(int, int)in FileUtility.cpp.o boost::asio::error::get_system_category() in FileServer.cpp.o boost::system::error_code::error_code()in FileServer.cpp.o __static_initialization_and_destruction_0(int, int)in FileServer.cpp.o __static_initialization_and_destruction_0(int, int)in FileServer.cpp.o boost::asio::error::get_system_category() in FileConnection.cpp.o boost::system::error_code::error_code()in FileConnection.cpp.o __static_initialization_and_destruction_0(int, int)in FileConnection.cpp.o __static_initialization_and_destruction_0(int, int)in FileConnection.cpp.o "typeinfo for boost::detail::thread_data_base", referenced from: typeinfo for boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileServer>, boost::_bi::list1<boost::_bi::value<FileServer*> > > >in files.cpp.o typeinfo for boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileConnection>, boost::_bi::list1<boost::_bi::value<FileConnection*> > > >in FileServer.cpp.o "boost::thread::start_thread()", referenced from: boost::thread::thread<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileServer>, boost::_bi::list1<boost::_bi::value<FileServer*> > > >(boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileServer>, boost::_bi::list1<boost::_bi::value<FileServer*> > >, boost::disable_if<boost::is_convertible<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileServer>, boost::_bi::list1<boost::_bi::value<FileServer*> > >&, boost::detail::thread_move_t<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileServer>, boost::_bi::list1<boost::_bi::value<FileServer*> > > > >, boost::thread::dummy*>::type)in files.cpp.o boost::thread::thread<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileConnection>, boost::_bi::list1<boost::_bi::value<FileConnection*> > > >(boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileConnection>, boost::_bi::list1<boost::_bi::value<FileConnection*> > >, boost::disable_if<boost::is_convertible<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileConnection>, boost::_bi::list1<boost::_bi::value<FileConnection*> > >&, boost::detail::thread_move_t<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileConnection>, boost::_bi::list1<boost::_bi::value<FileConnection*> > > > >, boost::thread::dummy*>::type)in FileServer.cpp.o "boost::filesystem::detail::not_found_error()", referenced from: boost::filesystem::basic_directory_iterator<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >::m_init(boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> const&)in FileUtility.cpp.o "boost::filesystem::detail::symlink_status_api(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, boost::system::error_code&)", referenced from: boost::enable_if<boost::filesystem::is_basic_path<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >, boost::filesystem::file_status>::type boost::filesystem::symlink_status<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >(boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> const&, boost::system::error_code&)in FileUtility.cpp.o "boost::detail::thread_data_base::~thread_data_base()", referenced from: boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileServer>, boost::_bi::list1<boost::_bi::value<FileServer*> > > >::~thread_data()in files.cpp.o boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileServer>, boost::_bi::list1<boost::_bi::value<FileServer*> > > >::~thread_data()in files.cpp.o boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileConnection>, boost::_bi::list1<boost::_bi::value<FileConnection*> > > >::~thread_data()in FileServer.cpp.o boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, FileConnection>, boost::_bi::list1<boost::_bi::value<FileConnection*> > > >::~thread_data()in FileServer.cpp.o "vtable for boost::detail::thread_data_base", referenced from: boost::detail::thread_data_base::thread_data_base()in files.cpp.o boost::detail::thread_data_base::thread_data_base()in FileServer.cpp.o "boost::thread::~thread()", referenced from: _initialize in files.cpp.o FileServer::run() in FileServer.cpp.o "boost::filesystem::detail::dir_itr_first(void*&, void*&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> >&, boost::filesystem::file_status&, boost::filesystem::file_status&)", referenced from: boost::filesystem::basic_directory_iterator<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >::m_init(boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> const&)in FileUtility.cpp.o "boost::filesystem::detail::file_size_api(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)", referenced from: boost::enable_if<boost::filesystem::is_basic_path<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >, unsigned long>::type boost::filesystem::file_size<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >(boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> const&)in FileConnection.cpp.o "boost::filesystem::detail::dir_itr_increment(void*&, void*&, std::basic_string<char, std::char_traits<char>, std::allocator<char> >&, boost::filesystem::file_status&, boost::filesystem::file_status&)", referenced from: boost::filesystem::basic_directory_iterator<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >::increment()in FileUtility.cpp.o "boost::filesystem::detail::create_directory_api(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)", referenced from: boost::enable_if<boost::filesystem::is_basic_path<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >, bool>::type boost::filesystem::create_directory<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >(boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> const&)in FileUtility.cpp.o "boost::system::get_generic_category()", referenced from: __static_initialization_and_destruction_0(int, int)in files.cpp.o __static_initialization_and_destruction_0(int, int)in files.cpp.o __static_initialization_and_destruction_0(int, int)in files.cpp.o __static_initialization_and_destruction_0(int, int)in FileUtility.cpp.o __static_initialization_and_destruction_0(int, int)in FileUtility.cpp.o __static_initialization_and_destruction_0(int, int)in FileUtility.cpp.o __static_initialization_and_destruction_0(int, int)in FileServer.cpp.o __static_initialization_and_destruction_0(int, int)in FileServer.cpp.o __static_initialization_and_destruction_0(int, int)in FileServer.cpp.o __static_initialization_and_destruction_0(int, int)in FileConnection.cpp.o __static_initialization_and_destruction_0(int, int)in FileConnection.cpp.o __static_initialization_and_destruction_0(int, int)in FileConnection.cpp.o "boost::filesystem::detail::status_api(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, boost::system::error_code&)", referenced from: boost::enable_if<boost::filesystem::is_basic_path<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >, bool>::type boost::filesystem::exists<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >(boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> const&)in FileUtility.cpp.o "boost::filesystem::detail::dir_itr_close(void*&, void*&)", referenced from: boost::filesystem::detail::dir_itr_imp<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >::~dir_itr_imp()in FileUtility.cpp.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [bin/libFiles-utility.dylib] Error 1 make[1]: *** [CMakeFiles/Files-utility.dir/all] Error 2 make: *** [all] Error 2 ----- The Client exits with a similar error during the build process. Would anyone know why this issue is occurring, and how I could fix it? Thank you in advance. Regards, Max Bossino Project Manager http://miragroupware.org

2 8

[ASIO] async_read buffer: starting byte null
by Matty Spatty 23 May '10

23 May '10

Hello, I have encountered a problem with some code that I cannot get my head around, I have spent quite a while looking for solutions but nothing has come up. When the client sends the first packet it is read fine but the header(first 8 bytes) for the second packet ALWAYS goes wrong, the first byte in the buffer is always null and the rest of the packet is pushed down the char array, e.g. I have done plenty of checks on the data the client sends: Client sends 00080002 Header reads _0008000 Client sends 0008TEST Header reads _0008TES (with _ as null) CODE: This is the first call to async_read, called when the client has connected ----------------- void CClient::start() { Log(MSG_INFO, "[%i] Connected", socket_.native()); boost::asio::async_read(socket_, boost::asio::buffer(packet_.buffer(), CPacket::headerSize), boost::bind(&CClient::recvHeader, shared_from_this(), boost::asio::placeholders::error) ); } The rest of the async_read's are called here ----------------- void CClient::recvMessage(const boost::system::error_code& error) { if (!error && handleMessage()) { packet_.reset(); boost::asio::async_read(socket_, boost::asio::buffer(packet_.buffer(), CPacket::headerSize), boost::bind(&CClient::recvHeader, shared_from_this(), boost::asio::placeholders::error) ); } else { disconnect(); } } Thanks in adavnce, Matty. P.S. I am very inexperienced with boost and not great at C++ so if you see anything I could improve, feedback would be appreciated.

2 4

Building Boost MPI, but no .lib are being built at all. Do you know what is going on?
by iono sphere 23 May '10

23 May '10

I am trying to run a program with Boost MPI, but the thing is I don't have the .lib. So I try to create one by following the instruction at http://www.boost.org/doc/libs/1_43_0/doc/html/mpi/getting_started.html#mpi.… The instruction says "For many users using LAM/MPI, MPICH, or OpenMPI, configuration is almost automatic", I got myself OpenMPI in C:\, but I didn't do anything more with it. Do we need to do anything with it? I also got myself MPICH2 in Program Files, and didn't do anything more with it as well. At this point of the instruction is where I am quite unsure about what exactly do we have to do. Beside that, another statement from the instruction: "If you don't already have a file user-config.jam in your home directory, copy tools/build/v2/user-config.jam there." Well, I simply do what it says. I got myself "user-config.jam" in C:\boost_1_43_0> along with "using mpi ;" into the file. Next, this is what I've done: bjam --with-mpi C:\boost_1_43_0>bjam --with-mpi WARNING: No python installation configured and autoconfiguration failed. See http://www.boost.org/libs/python/doc/building.html for configuration instructions or pass --without-python to suppress this message and silently skip all Boost.Python targets Building the Boost C++ Libraries. warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. warning: Unable to construct ./stage-unversioned warning: Unable to construct ./stage-unversioned Component configuration: - date_time : not building - filesystem : not building - graph : not building - graph_parallel : not building - iostreams : not building - math : not building - mpi : building - program_options : not building - python : not building - random : not building - regex : not building - serialization : not building - signals : not building - system : not building - test : not building - thread : not building - wave : not building ...found 1 target... The Boost C++ Libraries were successfully built! The following directory should be added to compiler include paths: C:\boost_1_43_0 The following directory should be added to linker library paths: C:\boost_1_43_0\stage\lib C:\boost_1_43_0> I see that there are many libs in C:\boost_1_43_0\stage\lib, but I see no trace of libboost_mpi-vc100-mt-1_43.lib or libboost_mpi-vc100-mt-gd-1_43.lib at all. These are the libraries required for linking in mpi applications. What could possibly gone wrong when libraries are not being built?

2 1

ASIO HTTP Server 3 Example: sharing stack data between threads
by Aaron Riekenberg 23 May '10

23 May '10

I was reading through the ASIO HTTP Server 3 example (http://tinyurl.com/35hwtd5) that uses a thread pool to call io_service::run. In both posix_main.cpp and win_main.cpp an http::server3::server object is created on the stack in main(). server has a boost::asio::io_service member (io_service_). main calls server::run, which creates a pool of threads that each call io_service_.run. So at this point the io_service_ object is within main's stack is being shared by multiple threads. Am I missing something or is this a bad thing to do and encourage others to copy? Seems like a simple fix would be to allocate the server object in main on the heap. Thanks, Aaron Riekenberg

2 1

How to deduce (possibly void) return type of member function?
by Terry Golubiewski 23 May '10

23 May '10

If I have a class... struct X { int f(double x); void f(int y); }; ... and a template Y that wants to deduce the return-type of some member functions of T... template<class T> struct Y { typedef typename what_goes_here<T>::type f_double_return_type; typedef typename what_goes here<T>::type f_int_return_type; }; I"ve tried using... typedef BOOST_TYPEOF_TPL(static_cast<X*>(0)->f(double(0))) f_double_type; // this works ... but ... typedef BOOST_TYPEOF_TPL(static_cast<X*>(0)->f(int(0)) f_int_type; // does not work for "void" Of course, I wouldn't know which one returns "void" or not ahead of time. terry

2 5

[profile_templates] Unable to run the template profiler
by Nathan Crookston 22 May '10

22 May '10

All, A template metaprogram I've written consumes too much memory when compiling on VC8. To debug this, I'm trying to use Steven Watanabe's template profiler. Unfortunately, I've been unable to run it successfully on my code. After some casting about I found [1] which resolved some initial problems, it seems. As a sanity check, I tried the following: ncrookston: ~/boost/tools/profile_templates/test $ bjam toolset=msvc error: Unable to find file or target named error: '/boost//regex' error: referred from project at error: '../src I'm definitely not a bjam/boost-build expert. Does anyone have suggestions on how I can fix this? My platform: XP 32-bit using VIsual Studio 2005 (VC8) Thanks, Nate [1] <http://lists.boost.org/Archives/boost/2009/05/152016.php>

3 3