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

Question about compiling boost.1.31.0 on Solaris
by Wenning Qiu 06 May '04

06 May '04

I was trying to build the regex library from boost.1.31.0 on a Solaris 7 box using STLport.4.6.2. I have a couple of STLport versions installed in /opt. Here's how I built: o cd boost_1_31_0/libs/regex/build o /export/home/qiuw01/research/boost-jam-3.1.9/bin.solaris/bjam "-sTOOLS=sunpro-stlport" -sSTLPORT_PATH=/opt I was expecting STLport.4.6.2 to be used. However when I used ldd on the generated .so library, it shows a dependency on an old version of STLport in /usr/lib qiuw01$ ldd libboost_regex-sw-p-1_31.so librt.so.1 => /usr/lib/librt.so.1 libstlport_sunpro.so.4.5 => /usr/lib/libstlport_sunpro.so.4.5 libaio.so.1 => /usr/lib/libaio.so.1 libc.so.1 => /usr/lib/libc.so.1 libdl.so.1 => /usr/lib/libdl.so.1 /usr/platform/SUNW,Ultra-4/lib/libc_psr.so.1 <ethos:~/research/boost_1_31_0/bin/boost/libs/regex/build/libboost_regex.so/ sunpro-stlport/release> This doesn't seem to be right. Any comments? Thanks, Wenning Qiu

1 0

boost::any and arithmetic ?
by Mailing List 06 May '04

06 May '04

Greetings all, as I'm new to this list, I'll keep my query short. It was suggested to me to use boost::any to store numeric values of whatever type (int, float, double, etc) so that I could use one std::list to store multiple values. I've looked through the header (any.hpp) and I admit it's a little hard for me to follow. I'm not what you'd call a superprogrammer... yet. :) I understand how to store a value in the boost::any object, but I'm not clear on how one would get that value back later (for display on screen, etc). What I'd really like to do is similar to one of the examples: --- snip --- struct property { property(); property(const std::string &, const boost::any &); std::string name; boost::any value; }; typedef std::list<property> properties; --- snip --- But I want to be able to do arithmetic with the resultant object(s): property T; property V; property Z; T [+-*/] Z; T = V [+-*/] Z T + [int,float,etc]; And so on. However, I want to make sure that the normal arithmetic type conversions (type promotions) take place (i.e. int + float returns a temporary object of type float). Example: boost::any value1; boost::any value2; boost::any value3; value1 = 127.915; value2 = 17; value3 = value1.getwhatevervalue() + value2.getwhatevervalue(); cout << value3.getwhatevervalue() << endl; value3 = value2.getwhatevervalue() + value1.getwhatevervalue(); cout << value3.getwhatevervalue() << endl; Both should return a temporary float with a value of 144.915. since I don't know how to get the value from boost::any, I just used getwhatevervalue() as an example. Sincerely, GRE

2 2

Posix extended regexp
by Manish Madan 05 May '04

05 May '04

Hello, I'm new to boost and I had one question. I'm trying to match strings against regular expressions that are expected to be posix extended regular expressions. But for some reason, the modifier ^ doesn't seem to be working. For example, when I try to match "Manish" against "^[mM]anish.*", I am returned false. What am I doing wrong? Here's my short matching function: bool MatchRegExp(const std::string& matchThis, const std::string& againstThis) { try { const boost::regex e(againstThis);//, boost::regex_constants::icase); return boost::regex_match(matchThis, e, boost::regex_constants::extended); } catch(boost::bad_expression be) { return false; } } thanks Manish

2 1

boost 1.30 / date_time / link problem with VC7
by Dan Dimerman 05 May '04

05 May '04

Hello, I'm having the following problem when linking a MSWindows MFC application with the static library libboost_date_time.lib using DevStudio .Net 7.0. The output looks like this: ------ Build started: Project: Main, Configuration: Debug Win32 ------ Linking... MSVCRTD.lib(ti_inst.obj) : error LNK2005: "private: __thiscall type_info::type_info(class type_info const &)" (??0type_info@@AAE@ABV0@@Z) already defined in libcmtd.lib(typinfo.obj) MSVCRTD.lib(ti_inst.obj) : error LNK2005: "private: class type_info & __thiscall type_info::operator=(class type_info const &)" (??4type_info@@AAEAAV0@ABV0@@Z) already defined in libcmtd.lib(typinfo.obj) LINK : warning LNK4098: defaultlib 'MSVCRTD' conflicts with use of other libs; use /NODEFAULTLIB:library Debug/Main.exe : fatal error LNK1169: one or more multiply defined symbols found I am working with the "Multi-threaded Debug (/MTd)" version of libraries. Tried using alternatives, but I got errors elsewhere and the errors above persisted. >From boost, I am using the library built at "My Documents\Visual Studio Projects\boost\libs\date_time\build\bin\libboost_date_time.lib\vc7\debug\run time-link-dynamic" Any help will be greatly appreciated... -- Dan Dimerman --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.677 / Virus Database: 439 - Release Date: 04-May-04

2 1

boost 1.31 compile problems
by Dave Thorn 05 May '04

05 May '04

After installing boost and trying to compile a project I found I was missing some files. The end of the installation shows: ...failed updating 24 targets... ...skipped 48 targets... ...updated 625 targets... Errors below. I'm running Debian woody, using gcc 2.95.4. Some of the errors: cp: cannot stat `bin/boost/libs/test/build/libboost_test_exec_monitor.so/gcc/debug/shared-linkable-true/threading-multi/libboost_test_exec_monitor-gcc-mt-d-1_31.so.1.31.0': No such file or directory gcc-C++-action bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc/release/threading-multi/test_tools.o /usr/local/src/boost_1_31_0/libs/test/build/../src/test_tools.cpp: In method `void boost::test_toolbox::detail::print_log_value<char>::operator ()(ostream &, char)': /usr/local/src/boost_1_31_0/libs/test/build/../src/test_tools.cpp:194: parse error before `(' /usr/local/src/boost_1_31_0/libs/test/build/../src/test_tools.cpp:205: confused by earlier errors, bailing out ...skipped <@boost!lib>libboost_unit_test_framework-gcc-mt-1_31.a for lack of <@boost!libs!test!build/libboost_unit_test_framework.a/gcc/release/threading-multi>libboost_unit_test_framework-gcc-mt-1_31.a... ...skipped <@boost!lib>libboost_test_exec_monitor-gcc-d.so for lack of <@boost!lib>libboost_test_exec_monitor-gcc-d-1_31.so.1.31.0... ...skipped <@boost!lib>libboost_test_exec_monitor-gcc-mt-d.so for lack of <@boost!lib>libboost_test_exec_monitor-gcc-mt-d-1_31.so.1.31.0... ...skipped <@boost!lib>libboost_test_exec_monitor-gcc.so for lack of <@boost!lib>libboost_test_exec_monitor-gcc-1_31.so.1.31.0... ...skipped <@boost!lib>libboost_test_exec_monitor-gcc-mt.so for lack of <@boost!lib>libboost_test_exec_monitor-gcc-mt-1_31.so.1.31.0... ...skipped <@boost!lib>libboost_unit_test_framework-gcc-d.so for lack of <@boost!lib>libboost_unit_test_framework-gcc-d-1_31.so.1.31.0... ...skipped <@boost!lib>libboost_unit_test_framework-gcc-mt-d.so for lack of <@boost!lib>libboost_unit_test_framework-gcc-mt-d-1_31.so.1.31.0... ...skipped <@boost!lib>libboost_unit_test_framework-gcc.so for lack of <@boost!lib>libboost_unit_test_framework-gcc-1_31.so.1.31.0... ...skipped <@boost!lib>libboost_unit_test_framework-gcc-mt.so for lack of <@boost!lib>libboost_unit_test_framework-gcc-mt-1_31.so.1.31.0... ...skipped <@boost!lib>libboost_test_exec_monitor-gcc-d.a for lack of <@boost!lib>libboost_test_exec_monitor-gcc-d-1_31.a... ...skipped <@boost!lib>libboost_test_exec_monitor-gcc-mt-d.a for lack of <@boost!lib>libboost_test_exec_monitor-gcc-mt-d-1_31.a... ...skipped <@boost!lib>libboost_test_exec_monitor-gcc.a for lack of <@boost!lib>libboost_test_exec_monitor-gcc-1_31.a... ...skipped <@boost!lib>libboost_test_exec_monitor-gcc-mt.a for lack of <@boost!lib>libboost_test_exec_monitor-gcc-mt-1_31.a... ...skipped <@boost!lib>libboost_unit_test_framework-gcc-d.a for lack of <@boost!lib>libboost_unit_test_framework-gcc-d-1_31.a... ...skipped <@boost!lib>libboost_unit_test_framework-gcc-mt-d.a for lack of <@boost!lib>libboost_unit_test_framework-gcc-mt-d-1_31.a... ...skipped <@boost!lib>libboost_unit_test_framework-gcc.a for lack of <@boost!lib>libboost_unit_test_framework-gcc-1_31.a... ...skipped <@boost!lib>libboost_unit_test_framework-gcc-mt.a for lack of <@boost!lib>libboost_unit_test_framework-gcc-mt-1_31.a... -- dave thorn

3 4

Boost license and Open Source
by eze.boost.org.users＠secureit.mailshell.com 04 May '04

04 May '04

Hi. I'm thinking of starting an open source project, and I'm seriously considering using Boost. I've read many messages regarding the practical aspects of using boost with other projects (particularly open source). However, I have found nothing useful regarding the legal aspect of using Boost for an open source project. As I'm considering licensing my project under the GPL, I'm concerned about the GPL "friendlyness" towards Boost. Besides the technical aspect of it, what is the best way to structure the project, to license the project, etc. in order to satisfy GPL and Boost licenses? Any help would be much appreciated. Best regards, Ezequiel "This communication is intended solely for the addressee and is confidential and not for third party unauthorised distribution."

4 3

CVS instructions at http://www.boost.org/more/getting_started.html#CVS don't work.
by Aaron W. LaFramboise 04 May '04

04 May '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I tried to get a copy of Boost CVS using the instructions at http://www.boost.org/more/getting_started.html#CVS, but I got this error: ~ $ cvs -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost login ~ Logging in to :pserver:anonymous@cvs.boost.sourceforge.net:2401/cvsroot/boost ~ CVS password: ~ cvs [login aborted]: connect to cvs.boost.sourceforge.net(66.35.250.209):2401 failed: Connection timed out However, when I use the SF CVS instructions at http://sourceforge.net/cvs/?group_id=7586, I have no problems. It recommends the following line instead. cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost login The difference seems to be cvs.boost.sourceforge.net versus cvs.sourceforge.net. Is this a temporary technical problem? Or should the instructions on the getting_started.html be updated? Thanks, Aaron W. LaFramboise OpenPGP fingerprint: CFB4 D883 17ED E9BE 6F16 1BF7 969F E586 75AC 33C4 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAlnS+lp/lhnWsM8QRAv6OAKCXKS7Kcd5JubzUQqQIk8eIbhlisgCghpyR FptrqZlFgVC8tGRxmLz6Cic= =zRlP -----END PGP SIGNATURE-----

3 2

regex_search (v4) raises exception for wregex
by Adam Molnar 03 May '04

03 May '04

hi! the following pattern (35 matching token, and at least one more) with this simple expression ("[_]+$") throws "memory exhausted" when using wchar_t strings. the same works with char strings even triple sized. matching doesnt throw, if we use "^[_]+$", "[_]{1,}$", "[_][_]*$" etc. so this is a bug. it seems the expression-string is short enough to cause some problem, but i was unable to track down the error. wchar_t * wp = L"___________________________________x"; wregex wre(L"[_]+$"); try { regex_search(wp, wre); } catch (bad_expression & e) { cout << e.what() << endl; } another issue: i think, "(one|two|three|)" style alternation (notice the empty string on the right) should be accepted and handled as "(one|two|three)?" now it throws bad_expression

4 4

Problem 2 with Boost 1.31.0 Regex for tru64cxx65
by Richard Hadsell 03 May '04

03 May '04

Having persuaded everything to compile in the 1.31.0 Regex library, it runs into another problem in building the .a archive libraries: tru64cxx65-Archive-action bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/libboost_regex-tru-1_31.a /bin/sh: /bin/ar: arg list too long rm -f bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/libboost_regex-tru-1_31.a ar r bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/libboost_regex-tru-1_31.a bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/c_regex_traits.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/c_regex_traits_common.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/cpp_regex_traits.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/cregex.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/fileiter.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/posix_api.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/regex.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/regex_debug.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/regex_synch.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/w32_regex_traits.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/wide_posix_api.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/instances.o bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/winstances.o "bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release"/cxx_repository/* ...failed tru64cxx65-Archive-action bin/boost/libs/regex/build/libboost_regex.a/tru64cxx65/release/libboost_regex-tru-1_31.a... The problem is due to the number of instantiations in the template repository and the lengths of their names. There are 492 instantiations, and many of them have 90-character file names, which looks like the compiler's maximum allowed. I solved the problem in previous versions of boost by breaking up the build into separate steps. This was the way I modified the make file: AR:= ar -cq IIDIR:= $(LIBDIR)/cxx_repository $(DIRNAME)/lib$(LIBNAME).a : $(ALL_O) @echo "*** creating lib$(LIBNAME).a" rm -f $@ $(AR) $@ $^ @echo "*** adding template instantiations" $(AR) $@ $(IIDIR)/[_A-Z]* $(AR) $@ $(IIDIR)/[a-z]* It builds the library from just the object files and then adds the instantiations in two steps. (Apparently, adding all of them exceeded the same shell arg list limit.) How can I do something equivalent with bjam to build the library? -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601

6 16

regex patches available
by John Maddock 03 May '04

03 May '04

All users of Boost.Regex-1.31.1 should be aware that there are now a set of patches available for this release - see https://sourceforge.net/project/showfiles.php?group_id=7586 for downloads. Issues fixed include: POSIX style regular expressions not behaving correctly with regex_grep. Non-greedy repeats not backtracking correctly in some cases. Backreferences cause some repeat operators to behave incorrectly. Some wide character expressions weren't getting correctly optimised, leading to thrown exceptions in trivial cases. Misc. compiler compatibility fixes. Regards, John Maddock

1 0