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

Building regex - VC6 SP5 + stlport
by boolean_dream 14 May '02

14 May '02

Hey all, In the past I've had no problems building with this combo, but recently did a system reinstall and got the latest versions and am having trouble. Using: - Boost 1.27.0 - VC6 with SP5 - STLport 4.5.3 STLport is in the INCLUDE and LIB variables as instructed and to complie I just type nmake vc6-stlport.mak from libs\regex\build. After a lot of sutff compling fine I get the below error... I was actually able to fix it by adding in some ifdefs in regex.hpp, but that caused some other problems - clearly I'm doing something wrong. Any ideas? Many thanks. cl /nologo /MTd /W3 /Gm /EHa /Zi /Od /I..\..\..\ /DWIN32 /D_MT /D_DE BUG /D_MBCS /D_LIB /YX /FD /GZ /c -Fpvc6-stlport/vc6-stlport- re300dm/vc6-stlport- re300dm.pch -Fo./vc6-stlport/vc6-stlport-re300dm/ -Fdvc6-stlport/vc6- stlport-re3 00dm.pdb ../src/cregex.cpp cregex.cpp ..\..\..\boost/regex.hpp(402) : error C2011: 'regex_iterator_traits<char *>' : ' struct' type redefinition ..\..\..\boost/regex.hpp(404) : error C2011: 'regex_iterator_traits<char const * >' : 'struct' type redefinition ..\..\..\boost/regex.hpp(407) : error C2011: 'regex_iterator_traits<unsigned sho rt *>' : 'struct' type redefinition ..\..\..\boost/regex.hpp(409) : error C2011: 'regex_iterator_traits<unsigned sho rt const *>' : 'struct' type redefinition NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop.

2 1

boost::shared_ptr<const T>
by Andrew R. Thomas-Cramer 13 May '02

13 May '02

Is it legal to construct a boost::shared_ptr<const T> from a raw T*? On MSVC6, it produces errors when class T has an implicit destructor, but compiles without error otherwise. ----------------------------------------------------------------------- Andrew R. Thomas-Cramer Work: artc(a)prism-cs.com http://www.prism-cs.com/ Home: artc(a)execpc.com http://www.execpc.com/~artc/ ----------------------------------------------------------------------- [Non-text portions of this message have been removed]

2 3

Re: building Boost using Jam
by jd.schmidt＠juno.com 13 May '02

13 May '02

OK, so I invoked Jam from my Boost root directory using: c:\boost_1_27_0\boost-build\jam -sBOOST_ROOT=. -sTOOLS="msvc" Now Jam is actually doing something, but I'm still getting messages like: The system cannot find the specified path. C:\Program is not recongnized as an internal or external command, operable program or batch file Also, I get a lot of messages like: ...found 1606 targets... ...updating 381 targets... [many other messages] ...failed msvc-C++-action [many other messages] ...failed updating 168 targets... ...skipped 202 targets... ...updated 11 targets... Obviously some things are happening, but I get the idea that it didn't work 100%. Do you have any advice? ________________________________________________________________ GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/web/.

5 4

Re: new boost.jam prebuilt's are available
by Jon Scobie 13 May '02

13 May '02

Toon, got jam to build from the latest CVS thanks but the libraries just refuse to build with vacpp. I started fixing some of the headers but have become stumped at these :- (this is just an excerpt) "./boost/regex.hpp", line 529.13: 1540-1628 (S) Every template parameter for a c onstructor template must be used in the parameter list of the constructor. "./boost/regex/detail/instances.hpp", line 104.10: 1540-0120 (S) The out of line member definition "boost::reg_expression<char,boost::regex_traits<char>,boost:: detail::allocator<char> >" of an explicit specialization should not use a templa te prefix. "./boost/regex/detail/instances.hpp", line 105.10: 1540-0120 (S) The out of line member definition "boost::reg_expression<char,boost::regex_traits<char>,boost:: detail::allocator<char> >" of an explicit specialization should not use a templa te prefix. "./boost/regex/detail/instances.hpp", line 106.10: 1540-0120 (S) The out of line member definition "boost::reg_expression<char,boost::regex_traits<char>,boost:: detail::allocator<char> >" of an explicit specialization should not use a templa te prefix. "./boost/regex/detail/instances.hpp", line 107.10: 1540-0120 (S) The out of line member definition "boost::reg_expression<char,boost::regex_traits<char>,boost:: detail::allocator<char> >" of an explicit specialization should not use a templa te prefix. Is boost completely broken on AIX vacpp v5.0.2? Jon. --- Toon Knapen <toon.knapen(a)si-lab.com> wrote: > You can find the new links in the CVS on the RC_1_28_0 branch. The difference > > is that this time, they point to a bjam.gz (remark the leading `b`) instead > of jam.gz. > __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com

2 1

Boost 1.27.0 on AIX 4.3.3
by scobiej 13 May '02

13 May '02

Hi, I've looked at all the documentation I can find on building boost on AIX for vacpp. However, I just can't get it to build! I'm using the prebuilt jam executable (not the one I built myself as it doesn't work - yacc stack overflow problems) and this is what I get :- bash-2.01$ jam -sBOOST_ROOT=. -sTOOLS="vacpp" status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:205: in link-fail status/Jamfile:237: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:205: in link-fail status/Jamfile:238: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:293: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:294: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:295: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:296: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:297: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:298: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:299: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:205: in link-fail status/Jamfile:300: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:197: in run-fail status/Jamfile:305: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:332: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:347: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:348: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:368: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope Unable to load Boost.Build, it seems that the build system files were located, but the build system is not defined. Attempted to use, as the bootstrap, this file: ./tools/build/boost-build.jam. This means that even though that file was loaded it either failed to directly load the build system files, or it failed to specify where to find and load the files by calling the 'build-system [path] ;' rule. Please consult the documentation at 'http://www.boost.org'. bash-2.01$ Any help would be appreciated! Thanks, Jon.

4 3

Boost.Thread (VC specific)
by judoka1981 13 May '02

13 May '02

Hi, would there be any problem in generating a .pdb file for libboost_thread? I'm using Boost 1.27.0 and VC.NET. Also, would it be possible to switch on generation of debug information for release builds as well? Regards // Johan

5 11

RE: [Boost-Users] Re: building Boost using Jam
by Tom Matelich 10 May '02

10 May '02

>Don't know which version of boost jam you are using, the version I'm >using does not support windows long file names with spaces so >virtually all targets fail due to bad include paths, and I decided >not to hack my VC installation just to let JAM build. So use the short names. It's a bit of pain to track them down, but they don't have any spaces.

3 2

RE: [Boost-Users] Re: building Boost using Jam
by Tom Matelich 10 May '02

10 May '02

For cvs, I use WinCVS. Best gui I've seen. www.cvsgui.org -----Original Message----- From: dmarsh26us [mailto:david.marsh10@ntlworld.com] Sent: Friday, May 10, 2002 9:57 AM To: Boost-Users(a)yahoogroups.com Subject: [Boost-Users] Re: building Boost using Jam Any general tips on general open source use, would be good also if you have a moment. For example are there better enviroments for a Win 2k setup? Should I use GCC instead? Where can I get a Win 2k version of cvs for source forge? The boost site is a bit light on help for us newbies! Have 6 years C++ but mainly on windows ;)

1 0

prebuild jam-exec's
by Toon Knapen 10 May '02

10 May '02

As previously only posted to the boost-ml (and not the boost-users-ml), the current prebuild jam-execs are not compatible with old revisions of boost nor can they compile the current CVS due to many usefull updates in boost.jam which will ease building boost in the future. There has been a lot of hard work done by David, Rene and Vladimir to have a stable boost.build for building the upcoming Version_1_28 of boost. On monday, updates of the prebuild exec's will be made available through the boost website. Until then, you can compile your own jam executable by just doing a`make YYACC=` in the tools/build/jam_src subdirectory of boost.

1 0

Smart pointers and overloading
by artc_prismcs 10 May '02

10 May '02

The marked call in the code below requires implicit conversion between compatible shared pointer types. At least two compilers (MSVC6 and Sun Workshop6) consider the marked call ambiguous. Remove the second overloaded() function, and the marked call is compiled without error. Replace all the shared pointers by raw, and all three calls to the overloaded methods would be resolved correctly. Is this a shortcoming of the compilers, boost::shared_ptr or the language? #include <boost/shared_ptr.hpp> class MyType { }; class DerivedType : public MyType { }; class OtherType {}; void overloaded( const boost::shared_ptr<MyType> & p ) {} void overloaded( const boost::shared_ptr<OtherType> & p ) {} int main() { boost::shared_ptr<MyType> pm( new MyType() ); boost::shared_ptr<DerivedType> pd( new DerivedType() ); boost::shared_ptr<OtherType> po( new OtherType() ); overloaded( pm ); overloaded( pd ); // Compilers complain of ambiguous call to overloaded function. overloaded( po ); return 0; }

2 1