Boost C++ Libraries: Ticket #4607: Build errors when Python installation is explicitly specified

attachment set

Katie Chan — Sun, 29 Aug 2010 00:32:32 GMT

attachment → python.log

Build log

Sun, 29 Aug 2010 09:28:55 GMT

Are you using a 64bit version of Python? If so, the problem might be that you only have a 64bit version of python.lib, which 32bit libs can't link with.

You can get similar problems if you try to build a 64bit version of Boost and only have a 32bit version of Python installed.

Katie Chan — Mon, 30 Aug 2010 00:32:53 GMT

Yeah, that appears to be the problem. However, a problem that arise now is if I explicitly specified a location for Python installation (because we now have multiple Python installations), then I can't do a `bjam --build-type=complete -j2 stage' to build everything with a single command.

An error of "error: link=shared together with runtime-link=static is not allowed" pops up that doesn't otherwise arise if Python is not explicitly specified.

owner, component changed

Dave Abrahams — Mon, 30 Aug 2010 18:32:13 GMT

owner changed from Dave Abrahams to Vladimir Prus
component Python → build

I think this should be considered a Boost.Build problem; if you disagree, Volodya, let's discuss it.

Vladimir Prus — Wed, 01 Sep 2010 09:04:33 GMT

Could you please attach your user-config.jam, so that I can know exactly how you configure 32-bit Python?

Thanks, Volodya

Katie Chan — Wed, 01 Sep 2010 11:24:42 GMT

Well it's usually in site-config.jam rather than user-config.jam, but the effect is the same.

# user-config.jam
using mpi ;

# site-config.jam
using python : 2.7 : C:/Python27-x86 ;
using msvc : 10.0 : cl.exe : <compileflags>-D_SECURE_SCL=0 <compileflags>-D_CRT_NONSTDC_NO_DEPRECATE <compileflags>-D_CRT_SECURE_NO_WARNINGS <compileflags>-D_SCL_SECURE_NO_WARNINGS ;

Vladimir Prus — Wed, 01 Sep 2010 11:57:35 GMT

Thanks. Can you then run bjam with a couple of extra options:

--with-python --debug-building

and attach the complete output as well?

attachment set

Katie Chan — Wed, 01 Sep 2010 13:11:35 GMT

attachment → build-log.7z

Debugging build log

summary changed

Katie Chan — Wed, 01 Sep 2010 13:16:49 GMT

summary 32-bits target build errors with MSVC under Windows x64 → Build errors when Python installation is explicitly specified

Well, the program doesn't occur when building python. It turns out to happens when specifying python installation explicitly when building mpi. The attached zip file contain explicit-mpi.log where python was specified explicitly, and implicit-mpi.log where it wasn't.

attachment set

anonymous — Wed, 01 Sep 2010 13:53:38 GMT

attachment → mpi.diff

Possible fix

Vladimir Prus — Wed, 01 Sep 2010 13:54:23 GMT

Could you try the attached patch?

attachment set

Katie Chan — Wed, 01 Sep 2010 16:22:00 GMT

attachment → fix1-build.log

Katie Chan — Wed, 01 Sep 2010 16:22:30 GMT

Nope, doesn't work.

Vladimir Prus — Mon, 27 Sep 2010 16:34:02 GMT

Are you sure you get exactly the same error? For me, if I apply the patch I get a different error -- specifically that Python's extension to support MPI (called mpi.so on my system) is being installed to stage/mpi.so twice -- once as release version and another as debug. That issue is relatively long-standing -- maintained of Boost.MPI have not, to my knowledge, decided whether only one variant should be installed, or whether some of the variants should be renamed.

However, before we go there, can you confirm that the original error is gone, and you get a different one? If possible, please attach the text of the new message.

Vladimir Prus — Mon, 27 Sep 2010 16:35:48 GMT

I have checked in the fix I've attached before in r65639.