Hi, 2009/10/7 Christian de Bouillé <[email protected]>: >> Using Fedora 10 64 bytes and now Fedora 11 32 bytes >> using boost-jam to create bjam and paste bjam when to be used >> I see many messages about failed or skipped targets >> for compiling boost and after $RDBASE/Code >> rdbase is not created. >> >> Probably Fedora is a bad distribution to be used for RDKIT >> there is some message about gcc not compiling some files >>
More on this below, but I think some of the problems you may be having at the moment are due to the use of gcc 4.4.x; I haven't compiled the RDKit with the gcc 4.4 series butI have had some reports that there are problems. >> Which distribution do you use >> and how to to improve Fedora to do the work ? I use the code under Ubuntu (09.04 at the moment, but older versions work too) and Red Hat Enterprise Linux. As long as gcc is of a reasonable version (4.0.x, 4.1.x, 4.3.x) things should be ok. There's a list of builds that I know have worked here: http://code.google.com/p/rdkit/wiki/WorkingBuilds >> >> Into RDKIT_Q22009_1 there are folders like Code and Projects >> and not Python ??? The Python directory has been renamed to "rdkit". > > Errors I have > >> Compiling boost bjam --with-thread --with-python release install >> >> ./boost/mpl/apply.hpp:138:31: erreur: opérateur binaire manquant avant >> l'élément lexical « ( » >> >> "g++" > -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pt >> hread > -DBOOST_ALL_NO_LIB=1 -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_POSIX >> -DNDEBUG -I"." -c -o >> > "bin.v2/libs/thread/build/gcc-4.4.1/release/link-static/threading-multi/thre >> ad.o" "libs/thread/src/pthread/thread.cpp" >> >> ...failed gcc.compile.c++ >> This is a problem building the boost libraries, not building the RDKit. I can't really help you here except to say that you should probably switch to a distribution with an somewhat older version of the compiler. There is some evidence on the boost website that there are problems with gcc 4.4.x: http://www.boost.org/development/tests/release/developer/summary.html Hope this helps, -greg
