[MacPorts] #36733: boost @1.51.0_1+no_single+no_static+universal filesystem tut3.cpp compile fail

[MacPorts]

#36733: boost @1.51.0_1+no_single+no_static+universal filesystem tut3.cpp compile
fail
----------------------------+---------------------------
  Reporter:  danielmlord@…  |      Owner:  adfernandes@…
      Type:  defect         |     Status:  closed
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.1.2
Resolution:  wontfix        |   Keywords:
      Port:  boost          |
----------------------------+---------------------------
Changes (by adfernandes@…):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Hmm... this rings a bell, but I can't seem to find it online.

 I remember that boost had some sort of problem building 32-bit executables
 on 64-bit platforms; I think this might even be an old macports bug
 report.

 I '''do''' know that you absolutely, positively cannot mix gcc and clang
 builds of boost. Completely different compiler options get set. (Basically
 using different compilers causes different defines to be used, and
 different linker flags.)

 I also do know that only one or two boost releases ago there were problems
 with building for iOS with clang, especially with regard to visibility.
 Yes, boost sets visibility of symbols differently depending on the
 compiler.

 When people complain, they just say "use jam to build your project".

 In fact, with a private boost build I've been using, I seem to recall that
 `${SRC}/tools/build/v2/tools/darwin.jam` makes `-arch` compiler flag
 assumptions (usually incorrectly).

 I hope this helps. :-(

-- 
Ticket URL: <https://trac.macports.org/ticket/36733#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS