You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For now, we have worked around this by setting CC=gcc during configure stage.
But I have a suggestion when building with icc to consider using -static-intel flag. This causes Intel libraries to be linked in statically and avoids issue of not being able to link with libabt.so without either using the Intel compiler or at least having the Intel compiler libraries in the library search path.
The text was updated successfully, but these errors were encountered:
For now, the workaround is ./configure --prefix=[...] CC="icc -static-intel"; it can remove all Intel dependency from libabt.so as far as I checked with icc17.
I personally think that -static-intel can be a default behavior. As far as I tested, they don't produce link-time errors when I try to link multiple libraries compiled with -static-intel etc. I cannot assure that this modification causes any side effects, though.
If no one points out side effects and you think ./configure CC="icc -static-intel" is too hacky, we can add this flag by default when icc is used.
For now, we have worked around this by setting CC=gcc during configure stage.
But I have a suggestion when building with icc to consider using -static-intel flag. This causes Intel libraries to be linked in statically and avoids issue of not being able to link with libabt.so without either using the Intel compiler or at least having the Intel compiler libraries in the library search path.
The text was updated successfully, but these errors were encountered: