boost @1.65.1 +no_single+python36: link=shared together with runtime-link=static is not allowed

[slarew]

Building boost 1.65.1 without no_static fails for me. The (attached) log output says

error: link=shared together with runtime-link=static is not allowed
error: such property combination is either impossible 
error: or too dangerious to be of any use

[slarew]

build log

[Schamschula (Marius Schamschula)]

I also ran into this this morning. I just ran sudo port clean boost to remove the bad build and than ran sudo port install boost. This installed the default variant which does not have this issue. You may want to choose a different variant, but don't deselect no_static.

[ryandesign (Ryan Carsten Schmidt)]

Not sure what's going on. Michael?

Really, these no_single and no_static variants should be reimplemented as subports, I just haven't taken the time to figure out all the consequences of doing that. If we do that, this problem should go away.

[michaelld (Michael Dickens)]

Maybe a change in boost that disallows building both static and shared libraries? I haven't poked around Boost in a while. Not sure what the right thing here is, except maybe forcing no_static since, well, why build static anyway?

[ryandesign (Ryan Carsten Schmidt)]

We were not previously using runtime_link, only link. You added runtime_link in #50671 so maybe that's related.

librets requires boost's no_static variant, though it's the only port I can find that does so. Maybe that can be fixed.

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

In 8fb55a480670eb5bd69b89849f77235535e7dc81/macports-ports:

boost: avoid static versions of C & C++ runtimes

See ​http://www.boost.org/build/doc/html/bbv2/overview/invocation.html
No revbump because the port either builds correctly or not at all.
Fixes #55291

[michaelld (Michael Dickens)]

Good catch! Thx!