[MacPorts] #46202: Undefined symbols for architecture x86_64 on Yosemite

MacPorts noreply at macports.org
Thu Dec 11 02:49:28 PST 2014


#46202: Undefined symbols for architecture x86_64 on Yosemite
-------------------------+--------------------------------
  Reporter:  nmsnoopy@…  |      Owner:  macports-tickets@…
      Type:  defect      |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.3.3
Resolution:  invalid     |   Keywords:
      Port:  log4cpp     |
-------------------------+--------------------------------
Changes (by ryandesign@…):

 * status:  new => closed
 * cc: ryandesign@… (added)
 * resolution:   => invalid
 * keywords:  linker =>
 * priority:  High => Normal


Comment:

 Assuming that "`g++`" is a symlink to g++ from a MacPorts gcc port, for
 example created by using "`sudo port select`" to select a MacPorts gcc, or
 created manually, then this failure is expected.

 Like most ports, log4cpp is built using the system compiler. As of Lion,
 that's clang. That means it's using the system C++ library, which as of
 Mavericks is libc++.

 g++ from gcc48, and g++ from any FSF gcc port in MacPorts, uses the
 libstdc++ library from gcc.

 You cannot mix the two libraries in the same process and be able to pass
 objects back and forth between them. See wiki:FAQ#libcpp

 If you need more information about this situation you can write to the
 macports-users mailing list but it's not exactly a bug and it's not
 something we're likely to be able to fix.

 The solution is to use clang++ instead of g++.

-- 
Ticket URL: <https://trac.macports.org/ticket/46202#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list