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

/usr/include/boost/mpl/if.hpp:75: internal compiler error: Segmentation fault
by Nils Wagner 26 Aug '04

26 Aug '04

Dear experts, I am going to install VPython http://www.vpython.org/linux_download.html on SuSE 9.1 which makes use of the boost library. However I got a segmentation fault. /usr/include/boost/mpl/if.hpp:75: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.suse.de/feedback> for instructions. Preprocessed source stored into /tmp/ccrXaXyw.out file, please attach this to your bugreport. Any pointer would be appreciated. Nils

2 2

Boost Build, custom-built targets
by John Meinel 26 Aug '04

26 Aug '04

Hello all- I'm currently using Boost Build v1 for some of my projects. I must say, it's significantly better than Makefiles. Overall, I'm quite pleased, though it took a little while to learn. I haven't been able to figure out one thing, though. How to generate custom built targets. Basically, I want to auto-generate a C++ source file so that I can keep track of version information. I have a python script that determines the version information from various sources (such as the revision control system [arch]), and I would like it to be run before my library is built. If I was using a makefile I would do something like this: .PHONY: version.cpp version.cpp: generate_version.py version ./generate_version.py This would cause version.cpp to be generated fresh each time the build process was called. However, I don't really need the ".PHONY", it would be okay if it was only created whenever one of the other files changed. I'm sure it's possible to do this with bjam, I just haven't figured out how to do customized stuff like this yet. Thanks, John =:-> PS> Is there a better mailing list for this?

2 1

RE: [Boost-users] Re: Guidelines for effective exception usage
by Ben Hutchings 25 Aug '04

25 Aug '04

Peter Dimov <pdimov(a)mmltd.net> wrote: > Ben Hutchings wrote: > > Peter Dimov <pdimov(a)mmltd.net> wrote: > >> Victor A. Wagner Jr. wrote: > >>> > >>> OK, blunt point. > >>> the standard is (insert favorite expletive or "in error") if it > >>> allows use of std::runtime_error to terminate the program due to > >>> low memory situations (run out of memory (due to copying) during > >>> stack unwinding). > >> > >> It does not allow such a thing. > > > > This is an known and unresolved issue: > > http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html#254 > > "The copy constructors of all exception-derived classes already have > a no throw spec. Reference 18.6.1, 19.1 and 15.4/13." "As they stand, the copy constructors might fail via a call to unexpected. I think what is intended here is that the copy constructors can't fail." (Is it really necessary for us to quote the referenced text at each other? This is silly.)

3 2

RE: [Boost-users] Re: Guidelines for effective exception usage
by Ben Hutchings 25 Aug '04

25 Aug '04

Peter Dimov <pdimov(a)mmltd.net> wrote: > Victor A. Wagner Jr. wrote: > > > > OK, blunt point. > > the standard is (insert favorite expletive or "in error") if it > > allows use of std::runtime_error to terminate the program due to low > > memory situations (run out of memory (due to copying) during stack > > unwinding). > > It does not allow such a thing. This is an known and unresolved issue: <http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html#254>

2 1

Update: exception class that
by Stephen torri 25 Aug '04

25 Aug '04

I thought I would share what I am using for exceptions given the excellent advice from everyone responding to my initial email. There is no usages of any memory allocation or std::string like variables. If there are any 'oops' or 'gotchas' please let me know. My plan is to use a command flag for taking into a value. The value will determine what debug messages are reported at the cause of the problem. The message will be displayed via std::cerr. Stephen ---------------- Header ---------------- #ifndef IO_EXCEPTION_H_ #define IO_EXCEPTION_H_ #include <exception> #include <inttypes.h> namespace kurt { /*! * \class IOException * \brief Rather than inheriting from ifstream this class delegates * any required functionality to it. * \date 2003 * \author Stephen Torri */ class IO_Exception : public virtual std::exception { public: IO_Exception (uint32_t message_id); /*! * \brief Destructor */ virtual ~IO_Exception (void) throw(){} /*! * \brief Return the extra message accompanying the exception. */ const char* what (void) const throw(); /*! * \brief Return tne name of the exception */ const char* name (void) const throw(); enum { CANNOT_OPEN, INPUT_CORRUPTED, INVALID_IO_OP, READ_ERROR, UNSUPPORTED_OP, WRITE_ERROR, }; private: static const char* m_exception_name; static const char* m_messages[]; uint32_t m_id; }; } /* namespace kurt */ ------------- Source ------------- #include "IOException.hpp" namespace kurt { const char* IO_Exception::m_exception_name = "IO_Exception"; const char* IO_Exception::m_messages [] = { "I/O Error: cannot open", // CANNOT_OPEN "Input data is corrupted", // INPUT_CORRUPTED "Invalid i/o operation attempted", // INVALID_IO_OP "Error reading input", // READ_ERROR "Unsupported I/O operation", // UNSUPPORTED_OP "Error writing output", // WRITE_ERROR }; IO_Exception::IO_Exception (uint32_t message_id) : std::exception(), m_id(message_id) {} const char* IO_Exception::what (void) const throw() { return m_messages[m_id]; } const char* IO_Exception::name (void) const throw() { return m_exception_name; } } /* namespace kurt */ #endif /* IO_EXCEPTION_H_ */ -- Email: storri(a)torri.org

1 0

MPL vector size limit
by Arkadiy Vertleyb 25 Aug '04

25 Aug '04

Hi, Can BOOST_MPL_LIMIT_VECTOR_SIZE be increased beyond 50, and if yes, what is involved in this? Thanks, Arkadiy

2 2

licenses...
by MarC 24 Aug '04

24 Aug '04

Hi I subscribed to this list to find out if I can publish one program containig "Boost Filesystem Library" under the GPL2. I saw that Boost license is even more flexible than the GPL2 but I'm not sure if I can release a program containing Boost with GPL2... anybody knows? where should I ask to answer my question? my case is that I'm developping a stand-alone console program which I want to integrate in other GPL licensed projects of web developpment like quanta.sourceforge.net or screem.sourceforge.net. I don't mind about modifying the licene of my program to adapt it to the special license of "Boost Filesystem Library" but I think it's inaffordable to modify all licenses of big projects like quanta or screem... so I'm a little bit confused. any idea? thanks in advance!

4 4

boost.graph build problem in latest anonomous CVS update.
by Jeff Holle 24 Aug '04

24 Aug '04

I've just refreshed my boost via CVS and ran into a build problem with gcc v3.4.1. Initially, seems like everything failed on my system. However, I discovered that there is now a configure option :-) . After installing user.hpp where it does some good stuff, the bjam of the root of boost succeeded. However, in running bjam in $ROOT_BOOST/libs/graph/build. This Jamfile is configured to build both release and debug version of bgl-viz. It fails with similiar problems that I was getting elsewhere before I ran configure. An example of the problems is: boost/config/stdlib/libstdcpp3.hpp:33: error: expected unqualified-id before '<<' token boost/config/stdlib/libstdcpp3.hpp:33: error: expected `,' or `;' before '<<' token

4 4

can the boost multi-array be easily extended to std::map's?
by Steven L. Scott 24 Aug '04

24 Aug '04

I'm working on an application (a data analysis system built in C++) for which it would be helpful to have nested (multidimensional) containers other than ordinary arrays. I have defined a generic 'data' class which I like to store in std::vector<data *>'s. For a very simple example, a 'data' might be a double representing a student's score on an exam, or in more complex settings it might be some sort of spatial map, or a multidimensional set of records for a medical patient. I am interested in structures where 'data' is nested across multiple levels. For example, test scores are nested within students, students nested within teachers, nested within school districts, etc. For a single layer of nesting a std::map<std::string, std::vector<data *> > seems to be an ideal way to store such data, largely because text strings can be used to identify subjects: dat["johnny"] // returns a std::vector of pointers to johnny's test scores. This is often the way that data are stored in files to be analyzed. I'm looking for some sort of C++ container that is more convenient for multiply nested data than std::map<std::string, std::map<std::string .... , std::vector<data *> > > ... >, but which will allow me to write expressions like: dat["LAUSD"]["Central High"]["Ms. Jones' Class"]["Johnny"] // same vector as above. Can something like the Boost multi-array package be extended to handle this?

2 1

problems compiling example files
by MarC 24 Aug '04

24 Aug '04

I suppose, it's a begginer's linux problem but I didn't found the answer neither in the documentation nor in the internet forums... After installing boost on my system (see how at the end of this email), I wanted to compile simple_ls.cpp, the filesystem example. everything works when creating the .o but when linking a lot of undefined references arised. What have I done wrong? g++ -c simple_ls.cpp [marc@localhost ls]$ g++ -c simple_ls.cpp [marc@localhost ls]$ ls ls/ simple_ls.cpp* simple_ls.o [marc@localhost ls]$ g++ simple simple_ls.cpp simple_ls.o [marc@localhost ls]$ g++ simple_ls.cpp -o simple_ls /tmp/ccjMYBxo.o(.text+0x19): In function `main': : undefined reference to `boost::filesystem::initial_path()' /tmp/ccjMYBxo.o(.text+0x44): In function `main': : undefined reference to `boost::filesystem::native(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /tmp/ccjMYBxo.o(.text+0x55): In function `main': : undefined reference to `boost::filesystem::path::path[in-charge](char const*, bool (*)(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&))' /tmp/ccjMYBxo.o(.text+0x64): In function `main': : undefined reference to `boost::filesystem::system_complete(boost::filesystem::path const&)' /tmp/ccjMYBxo.o(.text+0x119): In function `main': : undefined reference to `boost::filesystem::exists(boost::filesystem::path const&)' /tmp/ccjMYBxo.o(.text+0x13c): In function `main': : undefined reference to `boost::filesystem::path::native_file_string() const' /tmp/ccjMYBxo.o(.text+0x1bf): In function `main': : undefined reference to `boost::filesystem::is_directory(boost::filesystem::path const&)' /tmp/ccjMYBxo.o(.text+0x1e2): In function `main': : undefined reference to `boost::filesystem::path::native_directory_string() const' /tmp/ccjMYBxo.o(.text+0x291): In function `main': : undefined reference to `boost::filesystem::is_directory(boost::filesystem::path const&)' /tmp/ccjMYBxo.o(.text+0x2ca): In function `main': : undefined reference to `boost::filesystem::path::leaf() const' /tmp/ccjMYBxo.o(.text+0x351): In function `main': : undefined reference to `boost::filesystem::path::leaf() const' /tmp/ccjMYBxo.o(.text+0x418): In function `main': : undefined reference to `boost::filesystem::path::leaf() const' /tmp/ccjMYBxo.o(.text+0x586): In function `main': : undefined reference to `boost::filesystem::path::native_file_string() const' /tmp/ccjMYBxo.o(.gnu.linkonce.t._ZN5boost10filesystem18directory_iteratorC1ERKNS0_4pathE+0x2d): In function `boost::filesystem::directory_iterator::directory_iterator[in-charge](boost::filesystem::path const&)': : undefined reference to `boost::filesystem::detail::dir_itr_init(boost::shared_ptr<boost::filesystem::detail::dir_itr_imp>&, boost::filesystem::path const&)' /tmp/ccjMYBxo.o(.gnu.linkonce.t._ZNK5boost10filesystem18directory_iterator11dereferenceEv+0xd): In function `boost::filesystem::directory_iterator::dereference() const': : undefined reference to `boost::filesystem::detail::dir_itr_dereference(boost::shared_ptr<boost::filesystem::detail::dir_itr_imp> const&)' /tmp/ccjMYBxo.o(.gnu.linkonce.t._ZN5boost10filesystem18directory_iterator9incrementEv+0xd): In function `boost::filesystem::directory_iterator::increment()': : undefined reference to `boost::filesystem::detail::dir_itr_increment(boost::shared_ptr<boost::filesystem::detail::dir_itr_imp>&)' collect2: ld returned 1 exit status thank you in advance again. PS: my system is: [marc@localhost html]$ g++ -v Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.2/specs Configured with: ../configure --prefix=/usr --libdir=/usr/lib --with-slibdir=/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --enable-long-long --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++,ada,f77,objc,java,pascal --host=i586-mandrake-linux-gnu --with-system-zlib Thread model: posix gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk) And i've installed boost using these packages: Nombre: libboost1 Versión: 1.31.0-5mdk ‎/usr/lib/libboost_date_time.so.1 ‎/usr/lib/libboost_date_time.so.1.31.0 ‎/usr/lib/libboost_filesystem.so.1 ‎/usr/lib/libboost_filesystem.so.1.31.0 ‎/usr/lib/libboost_prg_exec_monitor.so.1 ‎/usr/lib/libboost_prg_exec_monitor.so.1.31.0 ‎/usr/lib/libboost_python.so.1 ‎/usr/lib/libboost_python.so.1.31.0 ‎/usr/lib/libboost_regex.so.1 ‎/usr/lib/libboost_regex.so.1.31.0 ‎/usr/lib/libboost_signals.so.1 ‎/usr/lib/libboost_signals.so.1.31.0 ‎/usr/lib/libboost_test_exec_monitor.so.1 ‎/usr/lib/libboost_test_exec_monitor.so.1.31.0 ‎/usr/lib/libboost_thread.so.1 ‎/usr/lib/libboost_thread.so.1.31.0 ‎/usr/lib/libboost_unit_test_framework.so.1 ‎/usr/lib/libboost_unit_test_framework.so.1.31.0 ‎/usr/share/doc/libboost1-1.31.0 ‎/usr/share/doc/libboost1-1.31.0/LICENSE_1_0.txt Nombre: libboost1-devel Versión: 1.31.0-5mdk Archivos: ‎/usr/include/boost ‎/usr/include/boost/aligned_storage.hpp ‎/usr/include/boost/any.hpp ‎/usr/include/boost/array.hpp ‎/usr/include/boost/assert.hpp ‎/usr/include/boost/bind ‎/usr/include/boost/bind.hpp ‎/usr/include/boost/bind/apply.hpp ‎/usr/include/boost/bind/arg.hpp ‎/usr/include/boost/bind/bind_cc.hpp ‎/usr/include/boost/bind/bind_mf_cc.hpp ‎/usr/include/boost/bind/bind_template.hpp ‎/usr/include/boost/bind/make_adaptable.hpp ‎/usr/include/boost/bind/mem_fn_cc.hpp ‎/usr/include/boost/bind/mem_fn_template.hpp ‎/usr/include/boost/bind/mem_fn_vw.hpp ‎/usr/include/boost/bind/placeholders.hpp ‎/usr/include/boost/bind/protect.hpp ‎/usr/include/boost/blank.hpp ‎/usr/include/boost/blank_fwd.hpp ‎/usr/include/boost/call_traits.hpp ... /usr/lib/libboost_date_time.so ‎/usr/lib/libboost_filesystem.so ‎/usr/lib/libboost_prg_exec_monitor.so ‎/usr/lib/libboost_python.so ‎/usr/lib/libboost_regex.so ‎/usr/lib/libboost_signals.so ‎/usr/lib/libboost_test_exec_monitor.so ‎/usr/lib/libboost_thread.so ‎/usr/lib/libboost_unit_test_framework.so ‎/usr/share/doc/libboost1-devel-1.31.0 ‎/usr/share/doc/libboost1-devel-1.31.0/README ‎/usr/share/doc/libboost1-devel-1.31.0/boost.css ‎/usr/share/doc/libboost1-devel-1.31.0/c++boost.gif Nombre: libboost1-static-devel Versión: 1.31.0-5mdk ‎/usr/lib/libboost_date_time.a ‎/usr/lib/libboost_filesystem.a ‎/usr/lib/libboost_prg_exec_monitor.a ‎/usr/lib/libboost_python.a ‎/usr/lib/libboost_regex.a ‎/usr/lib/libboost_signals.a ‎/usr/lib/libboost_test_exec_monitor.a ‎/usr/lib/libboost_unit_test_framework.a

3 2