FYI: elk developers have been informed about the upcoming libxc bugfix release, and elk is tracked here https://bugzilla.redhat.com/show_bug.cgi?id=1831479
GPAW is tracked here https://bugzilla.redhat.com/show_bug.cgi?id=1830675
I've orphaned exciting, since there was not much collaboration from the developers.
GPAW is tracked here https://bugzilla.redhat.com/show_bug.cgi?id=1830675
I've orphaned exciting, since there was not much collaboration from the developers.
On Fri, May 15, 2020 at 11:44 AM Susi Lehtola <jussilehtola@xxxxxxxxxxxxxxxxx> wrote:
On Fri, 15 May 2020 12:15:05 +0300
Susi Lehtola <jussilehtola@xxxxxxxxxxxxxxxxx> wrote:
> Hello,
>
>
> unfortunately there's going to be *another* soname bump to libxc.
> Libxc 5 replaced the ancient "Fortran '90" interface with the Fortran
> 2003 version based on iso_c_binding. However, this included
> *renaming* the Fortran 2003 module and functions, which is obviously
> inconvenient for downstream projects and has caused a lot of hassle.
>
> This change is reverted in the upcoming libxc release, resulting in
> another soname bump, but a more backwards compatible API... It appears
> that the Fortran codes elk and exciting have not yet been compiled
> against libxc 5; the next release will be easier to compile against.
Nevermind, there's not going to be a soname bump; a copy of the
erroneously renamed library will also be shipped in the next release...
the main point being that libxcf03 will be there as well and stay there.
--
Susi Lehtola
Fedora Project Contributor
jussilehtola@xxxxxxxxxxxxxxxxx
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
