On 08/17/2015 12:42 AM, Matěj Cepl wrote:
> I didn’t build it, it was downloaded from the official EPEL repo.
Sorry, my mistake, I thought you were experimenting with the build
process for it as well.
> Why in the world, we define that __soversion macro? I have never
> in my life with SPEC files (that’s eight plus years) saw such
> gymnastics with SOVERSION and it seems suspicious.
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:
--- biblesync.spec 2015-08-17 08:42:33.742845215 -0400
+++ odd-biblesync.spec 2015-08-17 08:44:53.511697188 -0400
@@ -0,0 +1,2 @@
+%define __soversion 1.1
+
@@ -3 +5 @@
-Release: 1bsp%{?dist}
+Release: 3%{?dist}
@@ -8 +10 @@
-URL: https://github.com/karlkleinpaste/biblesync
+URL: http://www.xiphos.org
@@ -39,0 +42,2 @@
+export CFLAGS="$CFLAGS -fPIC"
+export CXXFLAGS="$CXXFLAGS -fPIC"
@@ -42 +46 @@
-%cmake -DLIBDIR=%{_libdir} .. -DCMAKE_SHARED_LINKER_FLAGS="-Wl,--as-needed"
+%cmake -DLIBDIR=%{_libdir} ..
-DCMAKE_SHARED_LINKER_FLAGS="-Wl,--as-needed"
-DBIBLESYNC_SOVERSION=%{__soversion}
@@ -58 +62 @@
-%{_libdir}/libbiblesync.so.%{version}
+%{_libdir}/libbiblesync.so.%{__soversion}
My package is fine:
$ rpm -ql biblesync.x86_64
/usr/lib64/libbiblesync.so.1.1.2
/usr/share/doc/biblesync
/usr/share/doc/biblesync/LICENSE
--karl
_______________________________________________
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
