scipy-0.11.0 not compiling

[logical_guy]

Well, I've been trying since last night to compile scipy-0.11.0 and it always fails at this part:

[m_lan]

Maybe try installing via pip? (http://pypi.python.org/pypi/pip)
I think Python Package Index has newer versions, for example it has matplotlib 1.2.x which is compatible with python3.

Another suggestion is to upgrade gcc to 4.6.3. I dont know if this would help, but i have this version installed and scipy works fine.

[logical_guy]

Thanks for your reply.

I want to avoid unmasking if I can, so I'll think about the gcc-4.6.3 bit.

About pip, I'll do some research on it as well and see what it's about. Hopefully then I'll have a better idea of the best way forward.

[verchiel]

I am facing the same issue, and I might add that GCC 4.6.3 returns with the same errors.

I have now successfully compiled SciPy running pip. Just don't forget to have swig installed as it is needed. So thanks to m_lan so far!

I originally wanted to compile SAGE though, and as it depends on SciPy it still wants to install it from the ebuild. Can pip also tell emerge that is has installed a certain package? I could not find any information on this, unfortunately. Masking the package would not help.

[defensor]

Same problem here. I really don't know what the problem is.

[pneula]

Just the same here, very annoying. Pip made it for me too.

I guess this is related to Python 2 vs 3 issues. I also got matplotlib working by installing it with pip even though I couldn't import it from a succesful portage installation.

[logical_guy]

So does pip use different compiler options to portage for python?

[dark_dimius]

fixed compiling by running
FFLAGS="-O2 -fPIC -march=native" python setup.py build
in build dir

[defensor]

Is there a way to use that trick by using portage?

[verchiel]

Well I even tried adding -fPIC to both CFLAGS and FFLAGS in my global make.conf with no success... I read about it solving several compiling issues though.

Did you successfully compile using emerge then, dark_dimius?

edit: more information on the -fPIC CFLAG can be found here: http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=3#doc_chap6
as well is here: http://devmanual.gentoo.org/archs/amd64/index.html
and even in more detail: http://www.gentoo.org/proj/en/hardened/pic-internals.xml

Neither of these could help me solve the issue though... I still have no clue what to do to pass the parameter for the library build. :/

[verchiel]

SOLVED:

Have a look at http://sergiosdj.wordpress.com/2008/06/24/how-to-personalize-a-packages-cflags-in-gentoo/

To summarize the solution:
You need to set the FFLAGS for the specific ebuild. In your /etc/portage/, you will find env/. There you create the directory sci-libs/ and a file scipy inside of it (in general: /etc/portage/env/<category>/<package>). There just add the -fPIC to FFLAGS:

[VoidMage]

This problem is being handled here.
As it's an eclass problem, any workarounds might break other things, once this gets fixed.

[verchiel]

Thank you VoidMage, I added a link to this thread to the bug report.

My workaround should not result in breakage. You may easily remove it any time you recompile SciPy.