https://bugzilla.redhat.com/show_bug.cgi?id=1350257 --- Comment #24 from Antonio Trande <anto.trande@xxxxxxxxx> --- (In reply to Dave Love from comment #23) > (In reply to Antonio Trande from comment #22) > > > I don't think the /usr/share/petsc*/conf directories should be in the > > > main packages (or even in the -devel ones?) > > > > > > > Do you think that modules and conf are useless? > > I'd like to avoid the module, but th file that is used lives in > /etc/modulefiles. > The other files there don't seem to be connected with running the library. > How are they used? > > > > > > I still don't understand the SETOPT_FLAGS thing, which definitely > > > isn't necessary, and why flags are set separately (and differently?) > > > at compile- and run-time. None of that seems to be necessary. > > > > > > > Configure does not like -D_FORTIFY_SOURCE flag. I set SETOPT_FLAGS in order > > to indulge a specific test. > > Only Make flags are effectively used for building. > > What are the actual errors you get, and how does it help to define an > invalid macro name (which I'd expect to give an error)? I said those bits > don't seem to be necessary because I'd removed them and built the package OK > for epel and fedora. The error does not appear anymore ... Probably it was caused by a bad configuration. SPEC: http://copr-dist-git.fedorainfracloud.org/cgit/sagitter/petsc/petsc.git/plain/petsc.spec?id=68d5a2fc3455718701b624ad8eed2a66cb1812b4 SRPM: https://copr-be.cloud.fedoraproject.org/results/sagitter/petsc/fedora-rawhide-x86_64/00450395-petsc/petsc-3.7.2-12.fc26.src.rpm -- 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@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/package-review@xxxxxxxxxxxxxxxxxxxxxxx