boost debug and python variants do work together

[paul@…]

Hi I think as a result of ticket #23667 I think that a conflict was put on the various python variants and the debug variant - I needed both so I tried modifying the port and removing the conflict and for boost 1.44 on snowleopard they did work together, so I suggest removing the conflict

[adfernandes (Andrew Fernandes)]

Ugh... I was hoping never to hear someone say that they needed the debugging version of the library. There have been large changes to the build system since 1.44.0 and I was hoping I could remove the debugging variant for 1.45.0. Oh well. I guess I'll keep it.

The problem, which may have gone away, is that mpi is built differently if python is enabled, and the bjam was getting confused as to the names of targets when it was compiling. They may have fixed that, I haven't tested it yet. Also, the boost-python and mpi-python modules would have to be changed to allow installation of the debugging versions.

It's a mess, really - but I'm going to try (in the next week or two) to upgrade the current Portfile to 1.45.0, and we'll see if the build problem goes away. I'm not sure how to handle the install, though, since both debug and release modules will have the same name.

[adfernandes (Andrew Fernandes)]

Committed in r73885. Note that I personally cannot get the python/openmpi variants to build together due to ^%$#%#%$#% ^{bjam, but I disabled the conflict for your benfit. The debugging variant must be specifically enabled, so your milage may vary.}