Closed msarahan closed 7 years ago
PS: for anyone playing with this, I advise you to set _OPTIMIZE=0 in build.sh, or else you'll be waiting a while on PGO.
Latest commit copies prefixed ld into $PREFIX/bin/ld and sets gcc flags to ensure that it gets used preferentially over system ld. This is necessary likely due to LTO.
This now works for me, and needs a bit of testing before uploading to defaults.
I guess I still haven't resolved the import error - so not quite ready yet.
The import error comes when that env var is set, but the root python is an older python that doesn't yet have that file. Once the root python is updated to a build that has the appropriate file, all is fine.
CC @jjhelmus @nehaljwani @mingwandroid
This doesn't quite work yet. The default one does work, and does allow things to be built with gcc. However, I saw this link error:
I have tried with gcc 4.4 in centos 6, and also with conda-forge's devtoolset2 docker image. in the docker image, I got a slightly different, but really similar error:
I have been setting _PYTHON_SYSCONFIGDATA_NAME using a variable in conda_build_config.yaml. Note that it must not be set when building python. I have:
Unfortunately, this doesn't seem to be importable. The error I see is:
I have verified that the _sysconfig_x86_64_conda_cos6_linux_gnu.py file is in the
(root)/lib/python3.6
folder, and I have also tried putting it into(root)/lib/python3.6/site-packages
, both of which are on sys.path when I activate _h_env...@jjhelmus told me that he was successful with py2.7 (his work is at https://github.com/jjhelmus/python-feedstock/tree/jjh_27_wip ) - I think I need sleep.