Re: [Boost-build] BJam error: "Duplicate name of actual target" with MPI Python bindings

Subject: Re: [Boost-build] BJam error: "Duplicate name of actual target" with MPI Python bindings
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-12-10 01:41:49

On Wednesday 09 December 2009 04:04:22 Jarno wrote:

> Hi,
> 
> I'm trying to build Boost 1.41.0 with MPI on Windows XP x64:
> 
> C:\lib\boost_1_41_0>bjam --toolset=msvc-9.0 --builddir=x64-build 
> --stagedir=x64 address-model=64 variant=debug,release link=static 
> runtime-link=shared threading=multi stage --with-mpi 
> -sICU_PATH="c:\lib\icu\icu-x64"
> 
> C:/lib/boost_1_41_0/tools/build/v2/build\virtual-target.jam:1066: in 
> virtual-target.register-actual-name from module virtual-target
> error: Duplicate name of actual target: <px64\lib>mpi.pyd
> error: previous virtual target { 
> common%common.copy-mpi.pyd.PYTHON_EXTENSION { 
> msvc%msvc.link.dll-mpi.pyd.PYTHON_EXTENSION { 

> It seems that bjam tries to write both debug and release versions of 
> mpi.pyd to the same file. If I call bjam with either variant=release or 
> variant=debug only, compilation runs without problems.
> 
> How can I make both release and debug builds with MPI Python bindings 
> enabled?

At present -- you cannot. Maintainers of MPI did not tell me how they
want to deal with this situation -- and in particular, whether more
than one variant of extension should reasonably be built, and if so,
whether it should use fancy naming, or use different directories, or
what. What do you actually expect to happen?

- Volodya