Conversation
antocuni
left a comment
There was a problem hiding this comment.
thank your for investigating this.
So, from what I understand the problem is that libraries installed in a conda env are not automatically visible to the compiler, so we need to pass the right flags to locate it.
That's fine but it seems a more general fix for all conda-managed libraries, so probably we need to do it unconditionally, not only for gc.h.
But now my question is different: why does it work at all in linux then?
It's totally possible that it works by chance on my machine, and it picks up the system-installed libgc.
|
Did you try with Pixi (also conda based), which should officially be supported? Note that we have in pyproject.toml [tool.pixi.activation.env]
# to be able to link libgc (bdw-gc)
C_INCLUDE_PATH = "$PIXI_PROJECT_ROOT/.pixi/envs/default/include:$C_INCLUDE_PATH"
LIBRARY_PATH = "$PIXI_PROJECT_ROOT/.pixi/envs/default/lib:$LIBRARY_PATH"
# only useful for macOS
DYLD_LIBRARY_PATH = "$PIXI_PROJECT_ROOT/.pixi/envs/default/lib:$DYLD_LIBRARY_PATH" |
|
(for reference, Kaustubh is an Anaconda colleague and we hit this problem when I was trying to onboard him).
@paugier that was also my first reaction: we test pixi, why it doesn't work? What I haven't understood is whether this is a mac-specific problem, or it's also a linux problem which for some reason it's not triggered. |
When trying to install
spyusingcondaonmacOS. I ran into problems withbwd-gcbecause the path forbwd-gclives in thecondaenvironment socccouldn't findgc.h(nor-lgcat link time).Steps I followed (in
spyroot directory):Hence I had to use the following fix so that
bwd-gccould be detected. If it seems useful please do consider adding this fix tospy.