On Tue, 12 Mar 2013, Julien Plu wrote:Can you maybe try using define=MPICH_SKIP_MPICXX instead of cxxflags? See http://www.boost.org/boost-build2/doc/html/bbv2/overview/invocation.html#bbv2.overview.invocation.properties for the full list; I don't see an easy way to add flags without overriding the existing ones (you might want to ask on the Boost.Build list about that). At least some of the current flags come from libs/mpi/build/Jamfile.v2.
Hi,
I re-build everything from the beginning 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
After many minutes, the compilation stop with exactly the same error :-(
What are the -D options that are missing ?
-- Jeremiah Willcock
2013/3/11 Jeremiah Willcock <jewillco@osl.iu.edu>
On Sun, 10 Mar 2013, julien.plu@redaction-developpez.com wrote:
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\lib>mpi.pyd for lack of <pbin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi>mpi.pyd...
...skipped <pC:\librairies\boost-1.53.0\lib>libmpi.dll.a for lack of <pbin.v2\libs\mpi\build\gcc-mingw-4.7.2\release\threading-multi>libmpi.dll.a...
Anyone know what's happen now ?
Can you please make sure that your new compile flag hasn't overridden the ones that are already there (defined by libs/mpi/build/Jamfile.v2)? In particular,
your linker error seems like you might be missing several -D options that are put in during normal builds of these libraries.
-- 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