Hi,
Ok, now I succeeded to add the "-DMPICH_SKIP_MPICXX" with this command line :
b2 toolset=gcc --j4 --layout=system release --prefix=C:\librairies\boost-1.53.0 --user-config=user-config.jam cxxflags=- DMPICH_SKIP_MPICXX install
But, there is still an error (different than the previous one) :
gcc.link.dll bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\libmpi.dll.a
bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\skeleton_and_content.o:skeleton_and_content.cpp:(.text+0x718): undefined reference to `_imp___ZN5boost3mpi6python6detail24skeleton_proxy_base_typeE'
collect2.exe: error: ld returned 1 exit status
"g++" -L"C:\Python273\libs" -L"C:\librairies\MPICH2-3.0.2\lib" -Wl,-R -Wl,"C:\Python273\libs" "-Wl,--out-implib,bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\libmpi.dll.a" -o "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\mpi.pyd" -shared -Wl,--start-group "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\collectives.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\py_communicator.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\datatypes.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\documentation.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\py_environment.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\py_nonblocking.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\py_exception.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\module.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\py_request.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\skeleton_and_content.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\status.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\python\py_timer.o" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\libboost_mpi_python.dll.a" "bin.v2\libs\python\build\gcc-mingw-4.7.2\release\threading-multi\libboost_python.dll.a" "bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\libboost_mpi.dll.a" "bin.v2\libs\serialization\build\gcc-mingw-4.7.2\release\threading-multi\libboost_serialization.dll.a" -Wl,-Bstatic -lmpi -Wl,-Bdynamic -lpython27 -Wl,--end-group -mthreads
...failed gcc.link.dll bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\libmpi.dll.a bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\mpi.pyd...
...removing bin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi\libmpi.dll.a
...skipped pC:\librairies\boost-1.53.0\libmpi.pyd for lack of
Hi,
Sorry for my late reply I was away.
Are you sure those flags are getting through to your compiler?
No the flag "-DMPICH_SKIP_MPICXX" doesn't appear in the in the compilation lines.
Could you please try to build Boost with that flag? I think it would likely work around the problem.
Also, is there some #define of UNSIGNED_SHORT anywhere in your MinGW header directory?
I don't know, how I can check that ? because I have a lot of headers in the MinGW header directory.
I couldn't find anything about it online. Using the #define that excludes mpicxx.h would likely fix the issue, though. -- Jeremiah Willcock
-----Message d'origine----- De : Boost-users [mailto:boost-users-bounces@lists.boost.org] De la part de Jeremiah Willcock Envoyé : jeudi 7 mars 2013 00:24 À : boost-users@lists.boost.org Objet : Re: [Boost-users] Compiled Boost with MPI
On Wed, 6 Mar 2013, julien.plu@redaction-developpez.com wrote:
Hi,
Thanks for your answer.
I have the same problem than the person on the trac with his code and If I add "--compileflags=-DMPICH_SKIP_MPICXX" or "--linkflags=-DMPICH_SKIP_MPICXX " to the boost compile command line I have exactly the same error.
Are you sure those flags are getting through to your compiler? The "mpicxx.h" file should not be included at all if that macro is defined. Also, is there some #define of UNSIGNED_SHORT anywhere in your MinGW header directory?
-- Jeremiah Willcock
-----Message d'origine----- De : Boost-users [mailto:boost-users-bounces@lists.boost.org] De la part de Jeremiah Willcock Envoyé : mardi 5 mars 2013 23:41 À : boost-users@lists.boost.org Objet : Re: [Boost-users] Compiled Boost with MPI
On Tue, 5 Mar 2013, julien.plu@redaction-developpez.com wrote:
Hi,
For my project I saw today that I needed MPI too. So I installed MPICH2 and Changed my « user-config.jam » file like that :
import toolset : using ;
using python : 2.7 : "C:/Python273" : "C:/Python273/include" : "C:/Python273/libs" ;
using mpi : :
<find-static-library>mpi
<library-path>"C:/librairies/MPICH2-3.0.2/lib"
<include>"C:/librairies/MPICH2-3.0.2/include"
:
"\"C:\\librairies\\MPICH2-3.0.2\\bin\\mpiexec\""
;
So I compile Boost with this command line : b2 toolset=gcc --j4 --layout=system release --prefix=C:\librairies\boost-1.53.0 --user-config=user-config.jam install
And the error is in the out.txt file in attachment.
Anyone know whatʼs happenned ?
It looks like mpicxx.h is having problems. Try to download http://www.usqcd.org/fnal/example/cpi.c, rename it to a .cpp file, and try to compile it with mpic++. If you get similar errors, it is a bug in MPICH and you should report it there (you might be hitting http://trac.mpich.org/projects/mpich/ticket/1582 which mentions the same line number as in your error messages). If that ends up being the problem, adding -DMPICH_SKIP_MPICXX to your compile flags might act as a workaround. If you do hit the existing bug, you might want to post a comment on that bug saying that it breaks compiling Boost.MPI with MPICH 3.0.2.
-- Jeremiah Willcock
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users