On Thu, Aug 16, 2018 at 9:37 AM, Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote: > On Thu, Aug 16, 2018 at 02:14:41PM +1000, Amit Saha wrote: >> Hi Igor, >> >> On Fri, Aug 10, 2018 at 4:33 PM Igor Gnatenko < >> ignatenkobrain@xxxxxxxxxxxxxxxxx> wrote: >> >> > Hello everyone, >> > >> > 0.27.x is released long time ago, but I never got time for updating it. It >> > obviously involves SONAME change. >> > >> > The good thing about this release is that it breaks only things in runtime >> > and only one function changed signature (for building) which nobody uses >> > anyway. >> > >> > I'm going to update library as soon as I get time (possibly on this >> > weekend if no all dependent packages build fine). I will handle all >> > rebuilds myself, just sending a notice. >> > >> > List of affected packages is below. >> > Maintainers by package: >> > R-git2r qulogic >> > geany-plugins dmaphy ohaessler pingou >> > ghc-bdcs-api clumens >> > ghc-gi-ggit dshea >> > git-evtag ignatenkobrain walters >> > gitg ankursinha ignatenkobrain nacho pwalter >> > julia nalimilan >> > kf5-ktexteditor dvratil jgrulich rdieter than >> > libgit2-glib ignatenkobrain kalev nacho pwalter >> > python-pygit2 pwalter >> > rubygem-rugged ignatenkobrain ktdreyer tdawson >> > rust-exa ignatenkobrain >> > rust-pretty-git-prompt ignatenkobrain ttomecek >> > subsurface pingou >> > >> > Packages by maintainer: >> > ankursinha gitg >> > clumens ghc-bdcs-api >> > dmaphy geany-plugins >> > dshea ghc-gi-ggit >> > dvratil kf5-ktexteditor >> > ignatenkobrain git-evtag gitg libgit2-glib rubygem-rugged rust-exa >> > rust-pretty-git-prompt >> > jgrulich kf5-ktexteditor >> > kalev libgit2-glib >> > ktdreyer rubygem-rugged >> > nacho gitg libgit2-glib >> > nalimilan julia >> > ohaessler geany-plugins >> > pingou geany-plugins subsurface >> > pwalter gitg libgit2-glib python-pygit2 >> > qulogic R-git2r >> > rdieter kf5-ktexteditor >> > tdawson rubygem-rugged >> > than kf5-ktexteditor >> > ttomecek rust-pretty-git-prompt >> > walters git-evtag >> > >> >> Thanks for your work. Just noticed that julia hasn't been built >> succesfully (https://koji.fedoraproject.org/koji/packageinfo?packageID=19172) >> . Seems to have failed with: "cc1plus: error: unrecognized command line >> option '-mcet'" >> >> This is currently an issue in Fedora Scientific building. What would be the >> path forward here? > > Drop '-mcet'? It's a bit hard to find docs for it, but [1] says: > """-mcet -fcf-protection enables support for the Control-Flow > -Enforcement > Technology (CET) feature in future Intel CPUs. This > -involves the > generation of additional NOPs, which are ignored by the current > CPUs. It is recommended that you enable this flag now, to detect any > issues caused by them (e.g., interactions with dynamic > instrumentation frameworks, or performance issues).""" > > It sounds like it's not something that is particularly needed at this > time. > > The build log also has a lot of: > /usr/include/features.h:381:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp] > # warning _FORTIFY_SOURCE requires compiling with optimization (-O) > ^~~~~~~ > This sounds like the package is not being built with the distro flags. A lot of the scientific stacks appear to do as they please here (they might have an exception, I'm not sure), but they have a tendency to use very x86 specific ones, in most cases if they used the distro ones the code would actually build/run across mult arch platforms. After getting yelled at for trying to fix it I moved on with life. Peter _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/NUSOEE6TSJXKZS3PBPX6JOED65YHKZV5/
