[Pkg-gridengine-devel] Bug#698286: incorrect value for "max vmem" is reported : possible fix

[Alois Schloegl]

The attached patch should address this issue. The patch is essentially this

commit af73e397da01a4f70c01387f284e87262e42e7a3
Author: Dave Love <d.love at liverpool.ac.uk>
Date:   Thu Apr 21 12:44:36 2011 +0000

    Introduce lUlong64  to fix wrong vmem reporting on 64-bit GNU/Linux
(from Univa)


from http://arc.liv.ac.uk/repos/git/sge

combined with a minor change for backporting to	6.2u5-7.1

--- a/gridengine_add64bit_support.patch	2013-06-05 14:24:17.415377163 +0200
+++ b/gridengine_add64bit_support.patch	2013-06-05 15:15:59.137610718 +0200
@@ -366,7 +366,7 @@
 +   if (pos < 0) {
 +      /* someone has called lGetPosUlong64() */
 +      /* makro with an invalid nm        */
-+      CRITICAL((SGE_EVENT, SFNMAX,
MSG_CULL_GETPOSULONG64_GOTINVALIDPOSITION ));
++      CRITICAL((SGE_EVENT, MSG_CULL_GETPOSULONG64_GOTINVALIDPOSITION ));
 +      DEXIT;
 +      abort();
 +   }





I've tested the patch using this procedure:

On wheezy machine, I downloaded the source package of gridengine 6.2u5-7.1

   apt-get -b source gridengine

Then applied the attached patch to the extracted source, and rebuild the
package in the following way:

   dpkg-buildpackage -rfakeroot -uc -b


and it builds cleanly and can be installed.








-------------- next part --------------
A non-text attachment was scrubbed...
Name: gridengine_add64bit_support.patch
Type: text/x-patch
Size: 50578 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gridengine-devel/attachments/20130605/885ae43f/attachment-0001.bin>