Re: problems build root on OSX against non-system python version

Hi,

On 14 Sep 2011, at 4:09pm, <wlavrijsen_at_lbl.gov> <wlavrijsen_at_lbl.gov> wrote:

> Chris,
>
> so I had a chance to look at my own MacPorts installation and I find that the
> paths that you provided to configure:
>
> ./configure
> --with-python-incdir=/opt/local/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6
> --with-python-libdir=/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/config --enable-python

What I can say... works for me (I'm currently using 2.7 on Lion, but those worked fine for me on SL).

>
> don't work for my MacPorts (no linkable library is found). I need:
>
> ./configure
> --with-python-incdir=/opt/local/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6
> --with-python-libdir=/opt/local/Library/Frameworks/Python.framework/Versions/2.6 --enable-python
>
> and then both the header (Python.h) and library (Python) are found and p2.6
> is selected as required.

OK, I'll look into that one.

>
> I also note that my MacPorts really does not have a "python" symlink or
> executable. Meaning, if anyone where to do:
>
> $ python
> >>> import ROOT
>
> with the MacPorts build of ROOT, it won't work, which is going to end up
> being confusing, I'll bet (see the large number of posts on the ROOT forum
> whenever non-system pythons are used on the Mac).

Did you run

> sudo port select python python26

to pick your default python version ? For me (with 27). I then get

Last login: Wed Sep 14 14:36:47 on ttys000 Chris-Jones-Macbook-Pro ~ > sudo port select python python27 Password:
Selecting 'python27' for 'python' succeeded. 'python27' is now active. Chris-Jones-Macbook-Pro ~ > which python /opt/local/bin/python
Chris-Jones-Macbook-Pro ~ > python
Python 2.7.2 (default, Aug 29 2011, 15:26:16) [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import ROOT
>>>

i.e. it all works just fine.

Anyway… This has got me thinking and I need to investigate a bit what happens inside the build with and without 'port select' having been run, as this could be part of the issue….

thanks

Chris

>
> Best regards,
> Wim
> --
> WLavrijsen_at_lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
>