-
Notifications
You must be signed in to change notification settings - Fork 718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TensorFlow-2.3.1-fosscuda-2020a-Python-3.8.2.eb fails to build (apparent compilation error) #12330
Comments
Has anyone been able the check/reproduce this? Would like to know if it is the easyconfig or my installation. |
I did not come across this problem building on centos7. I looked in your build logs for any low hanging fruit, like it picking up something from /usr/ when it shouldn't. But I can't see anything hinting to that. The actual error you are getting here is a straight up compilation problem; GCC isn't figuring out the function prototype for Quite bizarre. tensorflow/tensorflow#41061 seems to indicate a problem with a to new numpy (no idea how the hell that can affect this code though.. bizarre). |
That helps, since I did have a numpy version newer than the one in the SciPy-bundle dependency. Why did I have that? Because I cannot build SciPy-bundle due to the issue in #11093 So I need to install the packages in SciPy-bundle manually with pip, and comment out the SciPy-bundle dependency in easyconfigs. I downgraded the numpy to 1.18.3 as per the SciPy-bundle easyconfig and it looks like I am by the above error. But now I hit a new one:
Build log attached below... |
@Flamefire Any ideas about this |
I've seen this. It is the |
Numpy changed its API somewhere for the 1.19 version and yes the ICU error shows that it is not picking up the correct ICU -> Rebuild it and it should work. |
This worked, thanks very much for the tip. |
Cannot build TensorFlow-2.3.1-fosscuda-2020a-Python-3.8.2. Below is the error as far as I can tell. I am attaching the gzipped log file. This is on CentOS 8.3.
easybuild-TensorFlow-2.3.1-20210302.194515.yQwRu.log.gz
The text was updated successfully, but these errors were encountered: