[MacPorts] #37137: gobject-introspection @1.34.1.1_0 +universal Build failure - missing symbol in Python shared object

[MacPorts]

#37137: gobject-introspection @1.34.1.1_0 +universal Build failure - missing symbol
in Python shared object
------------------------------------+--------------------------------
  Reporter:  egall@…                |      Owner:  macports-tickets@…
      Type:  defect                 |     Status:  new
  Priority:  Normal                 |  Milestone:
 Component:  ports                  |    Version:  2.1.2
Resolution:                         |   Keywords:
      Port:  gobject-introspection  |
------------------------------------+--------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)


Comment:

 Replying to [ticket:37137 egall@…]:
 > {{{
 > Local-Admins-MacBook-Pro:~ ericgallager$ port -v installed glib2
 > The following ports are currently installed:
 >   glib2 @2.34.2_0+universal (active) platform='darwin 10' archs='i386
 x86_64'
 > Local-Admins-MacBook-Pro:~ ericgallager$ port -v installed glib2-devel
 > The following ports are currently installed:
 >   glib2-devel @2.35.1_0+universal (active) platform='darwin 10'
 archs='i386 x86_64'
 > }}}

 Is this accurate? It should not be possible for you to have both glib2 and
 glib2-devel active at the same time, because they conflict with one
 another; you would have had to force the activation to make this happen.
 Please deactivate both glib2 and glib2-devel forcibly, then activate the
 one that you want, which, unless you have a specific need to test features
 of the latest development version of glib, I suggest should be glib2:

 {{{
 sudo port -f deactivate glib2 glib2-devel
 sudo port activate glib2
 }}}


 > {{{
 > Local-Admins-MacBook-Pro:~ ericgallager$ which python
 > /Library/Frameworks/Python.framework/Versions/Current/bin/python
 > }}}

 Where did /Library/Frameworks/Python.framework come from? That's not a
 location where MacPorts would normally install files, nor would Apple have
 put any files there. Having any frameworks installed in
 /Library/Frameworks can be problematic for some MacPorts ports so we
 recommend you remove them.

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