From owner-freebsd-ports@FreeBSD.ORG Fri Sep 23 20:45:10 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35B13106564A for ; Fri, 23 Sep 2011 20:45:10 +0000 (UTC) (envelope-from rmtodd@servalan.servalan.com) Received: from ln.servalan.com (unknown [IPv6:2600:3c00::f03c:91ff:fe96:62f5]) by mx1.freebsd.org (Postfix) with ESMTP id EF4F18FC15 for ; Fri, 23 Sep 2011 20:45:09 +0000 (UTC) Received: from uucp by ln.servalan.com with local-rmail (Exim 4.71) (envelope-from ) id 1R7CcP-00059n-Gx for freebsd-ports@freebsd.org; Fri, 23 Sep 2011 15:45:09 -0500 Received: from rmtodd by servalan.servalan.com with local (Exim 4.76 (FreeBSD)) (envelope-from ) id 1R7CUk-00058D-Ru for freebsd-ports@freebsd.org; Fri, 23 Sep 2011 15:37:14 -0500 To: freebsd-ports@freebsd.org References: <4E7C2F91.8040705@zedat.fu-berlin.de> <4E7CAA51.2060102@freebsd.org> From: Richard Todd Date: Fri, 23 Sep 2011 15:37:14 -0500 In-Reply-To: <4E7CAA51.2060102@freebsd.org> (Julian Elischer's message of "Fri, 23 Sep 2011 08:48:33 -0700") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.5-b28 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: sysutils/sge6[012]: Sun Grid Engine - still broklen due to utmpx? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2011 20:45:10 -0000 Julian Elischer writes: > On 9/23/11 12:04 AM, Hartmann, O. wrote: >> I was wondering if the SUN Grid Engine, located in port >> sysutils/sge6[012] is still broken due to utmpx. >> >> My department uses this GRID engine on Linux and since a long time I >> wish to use it also on FreeBSD. >> >> Are there alternatives? What are people using on HPC FreeBSD? > > so how broken is it? > Since almost none of the active developers use SGE it is up to the > users to help us get it fixed.. IIRC, the actual breakage is due to an included slightly-hacked version of tcsh that gets used to build the qtcsh command. Since I never used that command, I just hacked that one part of the included tcsh to not do anything with utmp and it built; something like this: --- 3rdparty/qtcsh/FREEBSD_I386/config.h.orig 2003-03-07 20:27:15.000000000 -0600 +++ 3rdparty/qtcsh/FREEBSD_I386/config.h 2011-06-10 13:26:20.421119769 -0500 @@ -26,6 +26,9 @@ */ /* #undef POSIXSIGS */ +/* XXX quick hack to make qtcsh build by disabling utmp usage altogether. */ +#define HAVENOUTMP + /* * VFORK This machine has a vfork(). * It used to be that for job control to work, this define A better fix would be to apply whatever fixes were done in fbsd tcsh code to accomodate the New Utmp Scheme, of course, but this was good enough for me.