Hello community,

here is the log from the commit of package nfs-utils for openSUSE:Factory
checked in at Sun Oct 2 10:21:10 CEST 2011.



--------
--- openSUSE:Factory/nfs-utils/nfs-utils.changes        2011-09-26 
10:35:49.000000000 +0200
+++ /mounts/work_src_done/STABLE/nfs-utils/nfs-utils.changes    2011-10-01 
17:25:59.000000000 +0200
@@ -1,0 +2,6 @@
+Sat Oct  1 15:24:33 UTC 2011 - [email protected]
+
+- Fix build in arm, portability bug, applications MUST
+  use sysconf(_SC_PAGESIZE) instead of constant PAGE_SIZE
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


New:
----
  nfs-utils-page_size.patch

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

Other differences:
------------------
++++++ nfs-utils.spec ++++++
--- /var/tmp/diff_new_pack.ZTKK6d/_old  2011-10-02 10:21:06.000000000 +0200
+++ /var/tmp/diff_new_pack.ZTKK6d/_new  2011-10-02 10:21:06.000000000 +0200
@@ -54,6 +54,7 @@
 Source13:       nfs-utils.rpmlintrc
 Patch0:         nfs-utils-1.0.7-bind-syntax.patch
 Patch1:         warn-nfs-udp.patch
+Patch2:         nfs-utils-page_size.patch
 Suggests:       python-base
 
 %description
@@ -133,6 +134,7 @@
 %setup -q -n nfs-utils-%{version} -a 1
 %patch0 -p1
 %patch1 -p1
+%patch2
 cp %{S:6} .
 
 %build


++++++ nfs-utils-page_size.patch ++++++
--- utils/blkmapd/device-process.c.orig
+++ utils/blkmapd/device-process.c
@@ -296,7 +296,7 @@ decode_blk_volume(uint32_t **pp, uint32_
                off_t stripe_unit = vol->param.bv_stripe_unit;
                /* Check limitations imposed by device-mapper */
                if ((stripe_unit & (stripe_unit - 1)) != 0
-                   || stripe_unit < (off_t) (PAGE_SIZE >> 9))
+                   || stripe_unit < (off_t) (sysconf(_SC_PAGESIZE) >> 9))
                        return -EIO;
                BLK_READBUF(p, end, 4);
                READ32(vol->bv_vol_n);
continue with "q"...



Remember to have fun...

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to