https://bugzilla.redhat.com/show_bug.cgi?id=1357724
--- Comment #8 from Matt Chan <talc...@gmail.com> --- (In reply to Susi Lehtola from comment #7) > But that's not possible: you're using a version 2.8.6 tarball, while you > specify version 1.8.6 in the specfile (and work around the discrepancy > between your numbering and the tarball by specifying version 2.8.6 in the > %setup). The github tag is for 2.8.6, which is why the tarball shows up as that. The version in the documentation etc is 1.8.6. I can ask Qiming to retag it? The the tag/version should be fixed in a future release though. > > Ideally, you should be able to build everything against libcint, which is > cross-platform. Installing pyscf would then pull the necessary integrals > library through the soname requires. > > Because both qcint and libcint provide libcint.so(), either of them can > satisfy the library requires from pyscf, and you can switch from one to the > other just by installing the package you want: qcint or libcint. > > Libcint should, however, be the default package to be installed, because > qcint doesn't work on all x86_64 machines. I'm not sure how dnf does its > dependency resolvement, but if it's the same as with yum then the package > with the shortest name will be picked, and that'd be qcint. Hmm so you're saying I should change libcint to build on x86_64 as well, then list it in the pyscf BuildRequires? Alternatively I could do something similar to what Igor suggested? But those few users without SSE3 would have segfaults I think. %ifarch x86_64 BuildRequires: qcint-devel %else BuildRequires: libcint-devel %endif -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/package-review@lists.fedoraproject.org
