Hello community,

here is the log from the commit of package hxtools for openSUSE:Factory checked 
in at 2014-04-13 13:15:01
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/hxtools (Old)
 and      /work/SRC/openSUSE:Factory/.hxtools.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "hxtools"

Changes:
--------
--- /work/SRC/openSUSE:Factory/hxtools/hxtools.changes  2014-04-02 
17:22:54.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.hxtools.new/hxtools.changes     2014-04-13 
13:15:02.000000000 +0200
@@ -1,0 +2,6 @@
+Thu Apr  3 11:21:18 UTC 2014 - [email protected]
+
+- add remove-conflicting-types.diff, fixes build 
+  failure on aarch64
+
+-------------------------------------------------------------------

New:
----
  remove-conflicting-types.diff

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ hxtools.spec ++++++
--- /var/tmp/diff_new_pack.QSNN3S/_old  2014-04-13 13:15:03.000000000 +0200
+++ /var/tmp/diff_new_pack.QSNN3S/_new  2014-04-13 13:15:03.000000000 +0200
@@ -27,6 +27,7 @@
 Source:         http://jftp.inai.de/hxtools/%name-%version.tar.xz
 Source2:        http://jftp.inai.de/hxtools/%name-%version.tar.asc
 Source3:        %name.keyring
+Patch0:         remove-conflicting-types.diff
 # This package has a "Upstream First" policy for patches.
 # See https://en.opensuse.org/openSUSE:Packaging_Patches_guidelines
 BuildRequires:  fdupes
@@ -162,6 +163,7 @@
 
 %prep
 %setup -q
+%patch0
 
 %build
 %configure


++++++ remove-conflicting-types.diff ++++++
--- sadmin/xfs_irecover.c
+++ sadmin/xfs_irecover.c
@@ -42,12 +42,7 @@
 #include <libHX/proc.h>
 #include <libHX/string.h>
 #include <arpa/inet.h>
-
-typedef int8_t __s8;
-typedef uint8_t __u8;
-typedef uint16_t __be16;
-typedef uint32_t __be32;
-typedef uint64_t __be64;
+#include <linux/types.h>
 
 struct work_info {
        char *device;
-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to