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

ISO C++ does not support `long long'
by Joshua Moore-Oliva 11 Dec '03

11 Dec '03

When compiling programs that use boost, I get multiple warnings along these lines.. /home/josh/boost/type_traits/is_convertible.hpp:274: warning: ISO C++ does not support `long long' /home/josh/boost/type_traits/is_convertible.hpp:274: warning: ISO C++ does not support `long long' In file included from /home/josh/boost/iterator_adaptors.hpp:125, from /home/josh/boost/token_iterator.hpp:15, from /home/josh/boost/tokenizer.hpp:21, Am I doing something wrong? do I need to #define something? Using FreeBSD 4.9, gcc 3.2.3. Thanks, Joshua Moore-Oliva

3 3

filesystem::copy_file throws -- but why?
by Scott Meyers 11 Dec '03

11 Dec '03

I'm trying to use copy_file to, well, copy a file to a backup file (signified by adding ".bak" to the file's name). Here's what I'm doing, chopped way down: int processFile(const fs::path& fileName) { fs::path copyFileName(fileName.native_file_string() + ".bak"); fs::copy_file(fileName, copyFileName); } This throws an exception: boost::filesystem::path: invalid name "D:\Temp\CDFix\INDEX.HTM.bak" in path: "D:\Temp\CDFix \INDEX.HTM.bak" I don't see what's invalid about this name. From what I can tell, I'm fulfilling copy_file's preconditions and not falling into one of the cases where it's supposed to throw. What am I doing wrong? Thanks, Scott

1 0

RE: [Boost-users] Re: Re: Need linking help for boost::filesystem
by Ben Hutchings 10 Dec '03

10 Dec '03

Scott Meyers <Usenet(a)aristeia.com> wrote: > > Try a slight variation: > > > > cl /TP /W4 /WL /GX /GR -ID:\C++\Boost\Current simple_ls.cpp > > %BOOST_FILESYSTEM_LIB% > > Alas, that doesn't help. I still get multiply defined symbols. > This is with 1.30.2. It looks like your program and the filesystem library are built against different versions of the C/C++ run-time library. Under the control of #pragma directives, Visual C++ compiler can insert references into object files that tell the linker which libraries to link with. In this case the linker tries to link with both run-time libraries and finds conflicting definitions. Check that you're linking with the right build of the filesystem library. > Is there any reason to expect that the > problem will magically go away if the get the CVS version? Perhaps. The Boost headers are now using the abovementioned pragma to (hopefully) select the right library to link with. Ben.

2 1

Need linking help for boost::filesystem
by Witz 10 Dec '03

10 Dec '03

I had the same problem on VC7.1 - multiply defined symbols and thought i was just being dumb - with Scott having the same problem, maybe i wasn't :) I got round it by including the source files in the project i was working on - not the solution i'd have liked but it has the benefit of working and allowing me to get on with doing my 'proper' coding. So, are we going to be seeing 'Effective Boost' in the near future then Scott? :) Ian Whittley

2 1

RE: [Boost-users] Re: newbie question: graph library with gcc 3.2.1
by Vikram Anantha 09 Dec '03

09 Dec '03

Answered my own question. I replaced libbgl-viz with bgl-viz in lib/graph/example/Jamfile. I seem to be getting a little further. I'll get back with the other harder questions. Didn't want to waste people's time with questions I can answer myself :) Thanks Vik -----Original Message----- From: Vikram Anantha Sent: Tuesday, December 09, 2003 9:56 AM To: Boost Users mailing list Subject: RE: [Boost-users] Re: newbie question: graph library with gcc 3.2.1 I am using the released version 1.30.2. I had to make a change to the lib/graph/Jamfile.v2 as detailed in this email http://aspn.activestate.com/ASPN/Mail/Message/boost/1802962 in order to make the graph library compile. If at all possible, I would like to not use the current snaphot on CVS and make small local changes based on the released version. If possible, could somebody give me a little diff on the jamfile or something like that. Also, Volodya, Do your changes fix the problem with the graph examples failing or do they fix the warnings in the graph library? Thanks Vik -----Original Message----- From: Vladimir Prus [mailto:ghost@cs.msu.su] Sent: Monday, December 08, 2003 10:13 PM To: boost-users(a)lists.boost.org Subject: [Boost-users] Re: newbie question: graph library with gcc 3.2.1 Hi Vikram, > I tried building the graph library and the graph examples with bjam. I > am using gcc 3.2.1 on Solaris 2.8. > > The library seemed to build successfully but did have warnings. The > examples failed to build complaining that it could not find the > dependent graph library which seems to be a problem with my > LD_LIBRARY_PATH or something like that. The build outputs for both > cases are given below. I did not do any customizing for either of > these builds. My cmd line was bjam "-sTOOLS=gcc" > > Any help is appreciated. Thanks in advance What version of Boost are you using? If it's CVS version, then you might try to run "cvs up" now and try again. I've fixed some typos which were causing the above error. - Volodya _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

RE: [Boost-users] Re: newbie question: graph library with gcc 3.2.1
by Vikram Anantha 09 Dec '03

09 Dec '03

I am using the released version 1.30.2. I had to make a change to the lib/graph/Jamfile.v2 as detailed in this email http://aspn.activestate.com/ASPN/Mail/Message/boost/1802962 in order to make the graph library compile. If at all possible, I would like to not use the current snaphot on CVS and make small local changes based on the released version. If possible, could somebody give me a little diff on the jamfile or something like that. Also, Volodya, Do your changes fix the problem with the graph examples failing or do they fix the warnings in the graph library? Thanks Vik -----Original Message----- From: Vladimir Prus [mailto:ghost@cs.msu.su] Sent: Monday, December 08, 2003 10:13 PM To: boost-users(a)lists.boost.org Subject: [Boost-users] Re: newbie question: graph library with gcc 3.2.1 Hi Vikram, > I tried building the graph library and the graph examples with bjam. I > am using gcc 3.2.1 on Solaris 2.8. > > The library seemed to build successfully but did have warnings. The > examples failed to build complaining that it could not find the > dependent graph library which seems to be a problem with my > LD_LIBRARY_PATH or something like that. The build outputs for both > cases are given below. I did not do any customizing for either of > these builds. My cmd line was bjam "-sTOOLS=gcc" > > Any help is appreciated. Thanks in advance What version of Boost are you using? If it's CVS version, then you might try to run "cvs up" now and try again. I've fixed some typos which were causing the above error. - Volodya _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

newbie question: graph library with gcc 3.2.1
by Vikram Anantha 09 Dec '03

09 Dec '03

I tried building the graph library and the graph examples with bjam. I am using gcc 3.2.1 on Solaris 2.8. The library seemed to build successfully but did have warnings. The examples failed to build complaining that it could not find the dependent graph library which seems to be a problem with my LD_LIBRARY_PATH or something like that. The build outputs for both cases are given below. I did not do any customizing for either of these builds. My cmd line was bjam "-sTOOLS=gcc" Any help is appreciated. Thanks in advance Vik Anantha <GRAPH EXAMPLES BEGIN> unknown dependent target <libs!graph!build>liblibbgl-viz.a </GRAPH EXAMPLES END> <BGL BUILD BEGIN> ...patience... ...found 437 targets... ...updating 11 targets... MkDir1 ../../../libs/graph/build/bin MkDir1 ../../../libs/graph/build/bin/libbgl-viz.a MkDir1 ../../../libs/graph/build/bin/libbgl-viz.a/gcc MkDir1 ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug MkDir1 ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on MkDir1 ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic gcc-C++-action ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/graphviz_graph_lex.o lex.yy.c:1169: warning: `void yyunput(int, char*)' defined but not used gcc-C++-action ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/graphviz_digraph_lex.o lex.yy.c:1169: warning: `void yyunput(int, char*)' defined but not used gcc-C++-action ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/graphviz_graph_parser.o graphviz_parser.y: In function `void boost::read_graphviz(const std::string&, boost::GraphvizGraph&)': graphviz_parser.y:492: warning: unused variable `void*in' graphviz_parser.y: In function `void boost::read_graphviz(FILE*, boost::GraphvizGraph&)': graphviz_parser.y:497: warning: unused variable `void*in' /home/installs/boost-1.30.2/boost/tuple/detail/tuple_basic.hpp: At top level: graphviz_parser.y:81: warning: `const std::string& graphviz::get_graph_name(const graphviz::Subgraph&)' defined but not used gcc-C++-action ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/graphviz_digraph_parser.o graphviz_parser.y: In function `void boost::read_graphviz(const std::string&, boost::GraphvizDigraph&)': graphviz_parser.y:492: warning: unused variable `void*in' graphviz_parser.y: In function `void boost::read_graphviz(FILE*, boost::GraphvizDigraph&)': graphviz_parser.y:497: warning: unused variable `void*in' /home/installs/boost-1.30.2/boost/tuple/detail/tuple_basic.hpp: At top level: graphviz_parser.y:81: warning: `const std::string& graphviz::get_graph_name(const graphviz::Subgraph&)' defined but not used gcc-Archive-action ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/libbgl-viz.a ar: creating ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/libbgl-viz.a ...updated 11 targets... </BGL BUILD END>

2 1

link fail against boost_filesystem on FreeBSD 5 with gcc 3.3.3
by Ying-Chieh Liao 04 Dec '03

04 Dec '03

It's my first time using boost I'm using boost 1.30.2 with FreeBSD 5, where gcc version is 3.3.3 following is my code, quite simple <code> #include <boost/filesystem/operations.hpp> #include <boost/filesystem/fstream.hpp> #include <string> #include <iostream> namespace fs = boost::filesystem; const std::string LogFileName = "ggyy"; int main(void) { fs::ifstream LogFile(LogFileName); return 0; } </code> it compiles well, but failed on linking : <error> g++ -L/usr/local/lib -lboost_filesystem -o LogParser LogParser.o LogParser.o: In function `main': LogParser.o(.text+0x27): undefined reference to `boost::filesystem::path::path(std::string const&)' LogParser.o(.text+0x51): undefined reference to `boost::filesystem::path::native_file_string() const' *** Error code 1 </error> My boost is built from the ports system, and I'm sure I have libboost_filesystem.a and other related boost libraries TEST [/usr/local/lib] -ijliao- ls -al *boost* -r--r--r-- 1 root wheel 4058 Dec 1 11:51 libboost_date_time.a -r-xr-xr-x 1 root wheel 4524 Dec 1 11:51 libboost_date_time.so -r--r--r-- 1 root wheel 66680 Dec 1 11:51 libboost_filesystem.a -r--r--r-- 1 root wheel 23888 Dec 1 11:51 libboost_prg_exec_monitor.a -r-xr-xr-x 1 root wheel 15524 Dec 1 11:51 libboost_prg_exec_monitor.so -r--r--r-- 1 root wheel 524054 Dec 1 11:51 libboost_regex.a -r-xr-xr-x 1 root wheel 352124 Dec 1 11:51 libboost_regex.so -r--r--r-- 1 root wheel 3861324 Dec 1 11:51 libboost_regex_debug.a -r-xr-xr-x 1 root wheel 496028 Dec 1 11:51 libboost_regex_debug.so -r--r--r-- 1 root wheel 167428 Dec 1 11:51 libboost_signals.a -r-xr-xr-x 1 root wheel 82980 Dec 1 11:51 libboost_signals.so -r--r--r-- 1 root wheel 192482 Dec 1 11:51 libboost_test_exec_monitor.a -r-xr-xr-x 1 root wheel 106912 Dec 1 11:51 libboost_test_exec_monitor.so -r-xr-xr-x 1 root wheel 31636 Dec 1 11:51 libboost_thread.so -r-xr-xr-x 1 root wheel 53920 Dec 1 11:51 libboost_threadd.so -r--r--r-- 1 root wheel 185892 Dec 1 11:51 libboost_unit_test_framework.a -r-xr-xr-x 1 root wheel 103008 Dec 1 11:51 libboost_unit_test_framework.so so... could someone tell me how to solve this problem ? -- KISS : Keep It Simple, Stupid.

1 1

Re: regex static lib for x86 emulator
by Reuti_Raman_Babu＠sdc.canon.co.in 03 Dec '03

03 Dec '03

Thank for the earlier responses. It seems almost impossible to build regex lib to Pocket PC platform. I am getting following errors: regexs.lib(src.obj) : error LNK2001: unresolved external symbol "public: __cdecl boost::w32_regex_traits<unsigned short>::w32_regex_traits<unsigned short>(void)" (??0?$w32_regex_traits@G@boost@@QAA@XZ) regexs.lib(src.obj) : error LNK2019: unresolved external symbol CreateFileMappingA referenced in function "public: void __cdecl boost::re_detail::mapfile::open(char const *)" (?open@mapfile@re_detail@boost@@QAAXPBD@Z) regexs.lib(src.obj) : error LNK2019: unresolved external symbol CreateFileA referenced in function "public: void __cdecl boost::re_detail::mapfile::open(char const *)" (?open@mapfile@re_detail@boost@@QAAXPBD@Z) regexs.lib(src.obj) : error LNK2019: unresolved external symbol FindFirstFileA referenced in function "public: __cdecl boost::re_detail::file_iterator::file_iterator(char const *)" (??0file_iterator@re_detail@boost@@QAA@PBD@Z) regexs.lib(src.obj) : error LNK2019: unresolved external symbol FindNextFileA referenced in function "public: void __cdecl boost::re_detail::file_iterator::next(void)" (?next@file_iterator@re_detail@boost@@QAAXXZ) regexs.lib(src.obj) : error LNK2019: unresolved external symbol "public: static class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __fastcall boost::re_detail::w32_traits_base::error_string(unsigned int)" (?erro This error description "regexs.lib(src.obj) : error LNK2001: unresolved external symbol "public: __cdecl boost::w32_regex_traits<unsigned short>::w32_regex_traits<unsigned short>(void)" (??0?$w32_regex_traits@G@boost@@QAA@XZ)" doesn't make much sense to me. Others are not supported by Pocket PC 2003 SDK.Although unicode version of corresssponding API is supported. Please suggest any solution . Regards, Reuti "John Maddock" <john@johnmaddock To: <Reuti(a)sdc.canon.co.in> .co.uk> cc: Subject: Re: regex static lib for x86 emulator 11/20/2003 06:57 PM > I can build static library for ARM processor. > But when building for X86 emulator I am getting following error. > > LINK : fatal error LNK1104: cannot open file 'boost_regex_vc6_sss.lib' > > Please help. You shouldn't see that when building the source, only when trying to link a dll of exe that uses the lib - but in any case defining BOOST_REGEX_NO_LIB when building your code will stop the headers from looking for a lib to link to, and allow you to specify your own lib to link to. I hope that makes it clear :-) John.

2 1

bind/function/??? - accessing global function static type with runtime dll
by Jeff Flinn 01 Dec '03

01 Dec '03

I'm interfacing with several 'C' dynamic link libraries each with the same interface. The appropriate libraries get loaded/unloaded at run time. The following is an attempt create a wrapper that returns a function pointer of the proper static type as declared for the 'C' functions. //------------------------------ class DLL { HMODULE mDLLHdl; public: ~DLL(){ FreeLibrary( mDLLHdl ); } DLL( const std::string& aDLLName ) :mDLLHdl( LoadLibrary( aDLLName.c_str() ) ){} operator bool()const{ return mDLLHdl; } operator HMODULE()const{ return mDLLHdl; } template< typename TFnc > TFnc Fnc( const std::string& aName, TFnc )const { return (TFnc)GetProcAddress( mDLLHdl, aName.c_str() ); } }; //------------------------------ With: typedef int (FAR WINAPI *FARPROC)(); FARPROC GetProcAddress( HMODULE hModule, // handle to DLL module LPCSTR lpProcName // function name ); For example, it's used as follows: //------------------------------ // declared in an included header with extern "C" int DoAttach( const char* aName, int attachMode ); DLL lSomeDll( "Some.dll" ); boost::function0<int> lFnc = boost::bind( lSomeDll.Fnc( "DoAttach", DoAttach ), "Name", 123 ); //------------------------------ Which compiles fine, but results in unresolved external symbols errors during linking for 'DoAttach' in this example. I can force-link and run the resulting executable w/out problem. Is there a way to get the type of the function without the compiler needing to use the function pointer itself? Thanks, Jeff

1 0