- Boost-users - lists.boost.org

Re: [Boost-users] [File System] unresolved symbol unsigned int boost::filesystem::detail::not_found_error after upgrade from boost 1_34_0 to 1_34_1
by Bill McLean 12 Dec '07

12 Dec '07

Oops. The below is no longer a problem. In order to resolve the problem, I reinstalled boost from Boost Consulting and had it install all the libraries. One I dropped my belief that I had done everything correctly and I redid the installation was I able to resolve the problem. Bill McLean -----Original Message----- From: Bill McLean [mailto:bill@mcleansoftware.com] Sent: Wednesday, December 12, 2007 11:55 AM To: 'boost-users(a)lists.boost.org' Subject: [File System] unresolved symbol unsigned int boost::filesystem::detail::not_found_error after upgrade from boost 1_34_0 to 1_34_1 After upgrading from Boost 1.34.0 to 1.34.1, I get the Visual Studio 2005 error and building my project: Error 805 error LNK2001: unresolved external symbol "unsigned int boost::filesystem::detail::not_found_error" (?not_found_error@detail@filesystem@boost@@3IA) FolderProcessing.obj I have isolated the error to the declaration: boost::filesystem::directory_iterator it(folder); Using boost 1_34_0 the above declaration worked and with 1_34_0 it fails. I have copied the installed boost 1.34.1 (from Boost Consulting) C:\Program Files\boost\boost_1_34_1 to my project folder C:\projects\ardev\CurrentDev\ExternalLibs\boost where I copied the new boost 1_34_1 release over top the 1_34_0 release. All references to 1_34_0 libraries have been changed to 1_34_1 libraries: ... boost_signals-vc80-mt-gd-1_34_1.lib boost_thread-vc80-mt-gd-1_34_1.lib boost_filesystem-vc80-mt-gd-1_34_1.lib

1 0

Re: [Boost-users] build boost.python tutorial "hello world" without bjam
by damny＠web.de 12 Dec '07

12 Dec '07

hi. in result of your post, i changed my original bat like this: // --- snip ----------------------------------------------------------------------------- SET DIR_MINGW=c:\development_compiler\mingw\ SET DIR_BOOST=c:\development_compiler\_boost\ SET DIR_PYTHN=c:\development_compiler\python25\ SET DIR_PRJCT=%~dp0 SET NME_PRJCT=hello SET CC=c:\development_compiler\mingw\bin\g++.exe SET LD=c:\development_compiler\mingw\bin\ld.exe SET INCL=-I%DIR_BOOST%include\boost-1_34_1 -I%DIR_PYTHN%include -I%DIR_MINGW%include SET LIBS=-L%DIR_BOOST%lib -L%DIR_PYTHN%libs -L%DIR_MINGW%lib %CC% -O0 -shared %INCL% %DIR_PRJCT%%NME_PRJCT%.cpp ^ %LIBS% %DIR_BOOST%lib\boost_python-mgw34-1_34_1.a -lpython25 ^ -o %NME_PRJCT%.pyd // --- snip ----------------------------------------------------------------------------- in association with "boost_python-mgw34-1_34_1.dll" the "hello world" demo works *YeahHa*. but is there a possibility to avoid the necessity of using the dll? :o) daniel > -----Ursprüngliche Nachricht----- > Von: boost-users(a)lists.boost.org > Gesendet: 05.12.07 15:37:35 > An: boost-users(a)lists.boost.org > Betreff: Re: [Boost-users] build boost.python tutorial "hello world" without bjam > > damny(a)web.de wrote: > > > thanks for your replay, > > > > but nothing happens when i reorder the compile command. > > like before, the same error messages appear. > > > > are there any other ideas? i'm at a loss. > > OK, the only other thing I can offer is the output if the commands invoked > by bjam when building this tutorial example: > > ---%<--- > C:\src\boost\BOOST_~3\libs\python\example\tutorial>bjam -d+2 --toolset=gcc > Building Boost.Regex with the optional Unicode/ICU support disabled. > Please refer to the Boost.Regex documentation for more information > (don't panic: this is a strictly optional feature). > gcc.compile.c++ bin\gcc-mingw-3.4.2\debug\hello.o > > "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -g > -I"..\..\..\.." -I"C:\Python25\Include" -c -o > "bin\gcc-mingw-3.4.2\debug\hello.o" "hello.cpp" > > gcc.link.dll bin\gcc-mingw-3.4.2\debug\hello.a > bin\gcc-mingw-3.4.2\debug\hello.pyd > > "g++" -L"C:\Python25\libs" -Wl,-R -Wl,"C:\Python25" -Wl,-R > -Wl,"C:\Python25\libs" "-Wl,--out-implib,bin\gcc-mingw-3.4.2\debug\hello.a" > -o "bin\gcc-mingw-3.4 > .2\debug\hello.pyd" -shared -Wl,--start-group > "bin\gcc-mingw-3.4.2\debug\hello.o" > "..\..\..\..\bin.v2\libs\python\build\gcc-mingw-3.4.2\debug\boost_python-mgw3 > 4-d-1_34_1.a" -lpython25 -Wl,--end-group -g > > Creating library file: bin\gcc-mingw-3.4.2\debug\hello.a > --->%--- > > Here you can see the exact command used to compile and link the tutorial > example in boost 1.34.1. > > Maybe this gets you started. > > HTH, Markus > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=000000000066

2 1

identification of thread
by Igor 12 Dec '07

12 Dec '07

Hi, Could you please explain for beginner in thread-related business, how the thread is identified from itself? Can the program, that it the given thread, obtain its own number or an index of itself? I assume that there should be some enumeration such as numbering the main program by 0, next child thread by 1, etc.? And, in particular, is this number available from boost thread library? THanks in advance Igor

4 3

iterator_range compile problem
by Olivier Tournaire 12 Dec '07

12 Dec '07

Hi all, I am having problem while compiling this code : typedef std::pair<double,double> t_pair; typedef std::vector< t_pair > t_vector; typedef t_vector::iterator t_iterator; typedef iterator_range< t_iterator > histogram_type; // syntax error : missing ';' before '<' Do you have any issue ? Regards Olivier -- Le temps des cerises reviendra. Dans l'immédiat, c'est le temps des noyaux. Courage.

2 2

boost::random issue with icc on Windows
by Geoff Wedig 12 Dec '07

12 Dec '07

Hello, We are experiencing a problem with boost::random using icc on Windows under optimization. If we compile with the -O1 option, we get correct behavior. Compiling with -O2 or no -O option gives us a string of zeros. We have compiled a small test case which shows this problem: #include "boost/function.hpp" #include "boost/random.hpp" #include <iostream> #include <iomanip> using namespace std; typedef boost::lagged_fibonacci607 RGType; typedef boost::uniform_smallint<> DistType; typedef boost::variate_generator<RGType, DistType> GeneratorType; int main() { DistType mainDist(0,10000); RGType mainEng((boost::uint32_t) 12); GeneratorType mainGen(mainEng, mainDist); for(size_t i = 0; i != 10; ++i) cout << mainGen() << ", "; cout << endl; } To date, I've done a lot of hunting trying different compiler options to attack this problem. The compiler option which seems to have the most consistent effect, in that adding it makes the program work, whereas removing it makes it not is -Qunroll0. I am guessing something in the optimization is causing the generator not to initialize properly, but I do not, at present, know how to solve it. Has anyone else seen this, or have any ideas what might be going wrong? I appreciate any ideas. Thanks, Geoff Wedig Digital Domain

3 4

Constant floats
by Robert Dailey 12 Dec '07

12 Dec '07

Is there a way I can define constant floats within class scope like you can with integral values? I was hoping boost could help in this area. For example: struct default_alpha { static const float value = 1.0f; }; The above is not legal, of course. Anyone? Thanks.

6 12

[File System] unresolved symbol unsigned int boost::filesystem::detail::not_found_error after upgrade from boost 1_34_0 to 1_34_1
by Bill McLean 12 Dec '07

12 Dec '07

After upgrading from Boost 1.34.0 to 1.34.1, I get the Visual Studio 2005 error and building my project: Error 805 error LNK2001: unresolved external symbol "unsigned int boost::filesystem::detail::not_found_error" (?not_found_error@detail@filesystem@boost@@3IA) FolderProcessing.obj I have isolated the error to the declaration: boost::filesystem::directory_iterator it(folder); Using boost 1_34_0 the above declaration worked and with 1_34_0 it fails. I have copied the installed boost 1.34.1 (from Boost Consulting) C:\Program Files\boost\boost_1_34_1 to my project folder C:\projects\ardev\CurrentDev\ExternalLibs\boost where I copied the new boost 1_34_1 release over top the 1_34_0 release. All references to 1_34_0 libraries have been changed to 1_34_1 libraries: ... boost_signals-vc80-mt-gd-1_34_1.lib boost_thread-vc80-mt-gd-1_34_1.lib boost_filesystem-vc80-mt-gd-1_34_1.lib

1 0

[program_options] std::wstring ??
by Robert Bielik 12 Dec '07

12 Dec '07

I've tried using the std::wstring with program options, couldn't make it work, only with std::string. Any workarounds? TIA /R

2 4

[review] Gentle reminder - Fast track formal review of Boost.Functional/Factory will begin December 17
by John Torjo 12 Dec '07

12 Dec '07

Hi all, This is a gentle reminder of the Boost.Functional/Factory review, about to start next Monday. Factories are callback mechanisms for constructors, so we provide two function objects, boost::value_factory and boost::factory, that encasulate object construction through direct application of the constructor or operator new, respectively. These templates make other facilities that operate on function objects (such as standard algorithms, Boost.Bind, Boost.Function, or Fusion functional adapters) applicable to constructors. Get it from here: http://www.boost-consulting.com/vault/index.php?action=downloadfile&filenam… Best, John -- http://John.Torjo.com -- C++ expert ... call me only if you want things done right

1 0

Supporting Visual Studio 6 in boost
by Mathieu Malaterre 12 Dec '07

12 Dec '07

Hi there, This is not exactly a user question, but I was wondering if a couple of boost developers could comment on the support of VS6 in boost. How much time consuming is it ? Are there plan to actually drop it at some point ? Were there cases where you had to provide a duplicate implementation (partial specialization, template template parameter, SFINAE...) with slight modifications, therefore making the boost code more difficult to maintain ? How much did this compiler impact the design of boost API / internals ? Thanks for comments, -- Mathieu Ps: I know there are other buggy compilers out there that are also 'supported', feel free to also add comment for another difficult to support compiler.

3 2