Update recipes for better portability

[astrojuanlu]

@stuarteberg Made some recommendations here: ContinuumIO/anaconda-issues#483 (comment)

I have a problem with the first rule though:

In meta.yaml, always include gcc as a build dependency, never a run dependency.

The fact is that instant is a just-in-time compiler, so I actually need gcc as a run dependency. Should I add libgcc too then?

[stuarteberg]

I didn't realize that your package was a JIT. Perhaps the rules I listed were worded too strongly.

Should I add libgcc too then?

No, the gcc package is a superset of the libgcc package. If you have it as a run dependency, there's no benefit to also including libgcc.

[astrojuanlu]

No, the gcc package is a superset of the libgcc package. If you have it as a run dependency, there's no benefit to also including libgcc.

Got it, thanks. Let's see if I can provide at least an almost-portable version of the packages.

[astrojuanlu]

I found something stunning: using

CC=${PREFIX}/bin/gcc
CXX=${PREFIX}/bin/g++

leads to CHOLMOD related errors, whereas

CC=${PREFIX}/bin/cc
CXX=${PREFIX}/bin/c++

have no side effects. cc is identical to gcc and c++ is identical to g++. I will need another day to find the will to debug this, but so far it works.

[astrojuanlu]

I'm closing this issue because I managed to compile the packages but I'll have to bring back VTK support at some point. Thanks for your help!