[MacPorts] #36223: xraylib: needs to enforce use of MacPorts python

[MacPorts]

#36223: xraylib: needs to enforce use of MacPorts python
-------------------------------+--------------------------------
  Reporter:  david.w.watson@…  |      Owner:  macports-tickets@…
      Type:  defect            |     Status:  new
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.1.2
Resolution:                    |   Keywords:
      Port:  xraylib           |
-------------------------------+--------------------------------

Comment (by Tom.Schoonjans@…):

 Replying to [comment:6 david.w.watson@…]:
 > Replying to [comment:4 Tom.Schoonjans@…]:
 > > Replying to [comment:2 david.w.watson@…]:
 > > > Replying to [comment:1 Tom.Schoonjans@…]:
 > > > > Hello David,
 > > > >
 > > > >
 > > > > I've added an option to xraylib that allows the python bindings to
 be installed within the native site-packages folder of the selected
 python-interpreter, in order to avoid having to use the PYTHONPATH
 environment variable. This option is activated in the port file and
 therefore leads to your warning since you appear to be using the python
 interpreter that came with Mac OS X.
 > > > >
 > > > > I will add the destroot.violate_mtree setting to the port file
 which should take care of this warning.
 > > > >
 > > > > Cheers,
 > > > >
 > > > > Tom
 > > >
 > > >
 > > > Actually, if I do "which python" I get:
 > > >
 > > >
 /opt/macports/Library/Frameworks/Python.framework/Versions/2.7/bin/python
 > > >
 > > > so I don't know why its looking at /Library/Python
 > > >
 > > > Dave
 > >
 > > That's unexpected... I cannot reproduce that behavior on Mountain
 Lion. Unfortunately I do not have access to Snow Leopard.
 > >
 > > Would it be possible to compile xraylib yourself and send me the
 config.log file? Make sure to use the --enable-python-integration option
 to configure.
 > >
 > > I would be very grateful!
 > >
 > > Best,
 > >
 > > Tom
 >
 > Attached is config.log. The package failed to build, though, with a
 >
 > {{{
 > Making all in java
 > swig -I../include -includeall -java -o xraylib_wrap.c ../src/xraylib.i
 > :3: Error: Unable to find 'java.swg'
 > ../src/xraylib.i:15: Error: Unable to find 'typemaps.i'
 > }}}
 >
 > error. But that's not relevant at this point.



 Based on your config.log it looks definitely due to your PATH variable as
 pointed out by Ryan already. In fact, if you would have installed xraylib
 this way it would not have put the python bindings in /Library/Python but
 in the correct folder of macport's python...

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