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

MacPorts noreply at macports.org
Sun Nov 25 22:08:47 PST 2012


#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  |
------------------------------------+--------------------------------

Comment (by ryandesign@…):

 Replying to [comment:2 egall@…]:
 > > 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.
 >
 > I often use the -f flag so that's probably what happened. Anyway I
 deactivated glib2-devel per your instructions and this error still
 happens.

 You'll need to deactivate glib2-devel and glib2, then reactivate glib2.
 Otherwise we don't know whether the active files were put there by glib2
 or glib2-devel.

 Please don't get in the habit of using the -f flag. Use it only in very
 limited circumstances where you understand all the side effects. If you're
 unsure of the side effects, feel free to ask on the mailing list.

 > > 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.
 >
 > I had installed python 2.7 with the installer from the
 [http://python.org/download/ Python website] before I installed MacPorts.
 Coincidentally that's also where all my easy_install eggs and stuff end
 up. I'd rather keep it there so when easy_install-ing stuff, it doesn't
 get in my MacPorts prefix.

 It will probably interfere with MacPorts, so we would really appreciate it
 if you removed it, or else don't be surprised when MacPorts things start
 breaking or installing files in the wrong location.

 I don't write python code myself and I'm not familiar with easy_install,
 but you should be able to use MacPorts python and install any python
 modules you need using the corresponding ports. If a port doesn't exist
 for a module you need, it could be an opportunity for you to write a port
 for it, or else file a port request ticket and perhaps someone else can
 help do so.

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


More information about the macports-tickets mailing list