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

error with gcc10 #3

Closed
GengSS opened this issue Jan 1, 2021 · 5 comments
Closed

error with gcc10 #3

GengSS opened this issue Jan 1, 2021 · 5 comments
Labels
invalid This doesn't seem right

Comments

@GengSS
Copy link

GengSS commented Jan 1, 2021

Dear Cp2k/libint developers,

It seems there is a bug with gcc10 in the source of old libint.
evaleev/libint#173

The bug has been fixed in the source code of libint, but not updated with the CP2K configured tarballs yet,
Please let me know if there is a workaround for it.

Thank you very much

Best,
Geng

@fxcoudert
Copy link

This is preventing cp2k from being updated in Homebrew: Homebrew/homebrew-core#68951

@dev-zero
Copy link
Contributor

As documented in the referenced issue evaleev/libint#173 this is not a bug in libint but a regression in gcc-10.1 and gcc-10.2. The patch I wrote was accepted for gcc-10.3 and trunk. Please update your compilers.

@dev-zero dev-zero added the invalid This doesn't seem right label Jan 23, 2021
@dev-zero
Copy link
Contributor

the respective gcc issue can be found here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95889

@fxcoudert
Copy link

The patch I wrote was accepted for gcc-10.3 and trunk. Please update your compilers

I know, but gcc 10.3 is not released and will not be released for several months (nor GCC 11). Given that a workaround seems possible (later versions of libint don't have the issue), I was hoping this could be included.

@dev-zero
Copy link
Contributor

Homebrew provides a compiler. A compiler with a regression. A regression which was fixed at upstream. You could fix that in Homebrew. Whether or not newer versions of libint give consistent results across all platforms was not verified and hence we don't support that. Since we have a rather large amount of dependencies by now to verify we can not support all pre-releases (and a beta is a pre-release) of any dependency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

3 participants