Skip to content
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

Compilation tools in sympy.utilities do not handle nonstandard libgfortran location #15671

Open
asmeurer opened this issue Dec 19, 2018 · 1 comment

Comments

@asmeurer
Copy link
Member

See #15385 (comment). The failures in Azure pipelines are like

2018-12-12T21:47:31.7271950Z ________________ sympy/codegen/tests/test_fnodes.py:test_bind_C ________________
2018-12-12T21:47:31.7271999Z Traceback (most recent call last):
2018-12-12T21:47:31.7272272Z   File "/usr/envs/optional-dependencies/lib/python2.7/site-packages/sympy-1.4.dev0-py2.7.egg/sympy/codegen/tests/test_fnodes.py", line 185, in test_bind_C
2018-12-12T21:47:31.7272319Z     if not has_fortran():
2018-12-12T21:47:31.7272578Z   File "/usr/envs/optional-dependencies/lib/python2.7/site-packages/sympy-1.4.dev0-py2.7.egg/sympy/utilities/_compilation/availability.py", line 24, in has_fortran
2018-12-12T21:47:31.7272647Z     raise ValueError("Failed to compile test program:\n%s\n%s\n" % (stdout, stderr))
2018-12-12T21:47:31.7272686Z ValueError: Failed to compile test program:
@moorepants
Copy link
Member

If core libs aren't in standard locations, shouldn't it be up to the user to set environment variables to ensure they are found? I don't think sympy should be responsible for finding the libs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants