Matej, Are you certain that you're calling up the xiphos that came from my packages? My biblesync build script never generates a biblesync.so.1.1.2 at all, so there should be no way for the Xiphos package to be created while referencing it. If the biblesync spec file was generating a library file with 1.1.2 at the end, I would get errors during build of the biblesync packages saying that the extra file wasn't packaged into the RPM.
--Greg On Mon, Aug 17, 2015 at 12:26 PM, Matěj Cepl <mc...@cepl.eu> wrote: > On 2015-08-17, 13:00 GMT, Karl Kleinpaste wrote: >> I can't offer any guess, being not involved in Redhat repo management. >> My builds use a spec that started as mostly Greg's. Your version lacks >> Greg's -fPIC additions from several months ago (F22 got uptight about >> security in some new, weird sense, and -fPIC became a requirement; I >> understand RHEL/Centos/EPEL are behind this curve), and adds the >> soversion nonsense. Non-comment differences (-U0) between mine and that: > > Thanks, this helped. If you would be interested, see > https://bugzilla.redhat.com/show_bug.cgi?id=1254317 for more. > > Blessings, > > Matěj > > -- > http://www.ceplovi.cz/matej/, Jabber: mc...@ceplovi.cz > GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC > > How many Bavarian Illuminati does it take to screw in a light > bulb? > Three: one to screw it in, and one to confuse the issue. > > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page