From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39411) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dkCim-0003jz-Dg for guix-patches@gnu.org; Tue, 22 Aug 2017 13:12:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dkCig-0002A5-Pk for guix-patches@gnu.org; Tue, 22 Aug 2017 13:12:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:41118) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dkCig-0002A1-ML for guix-patches@gnu.org; Tue, 22 Aug 2017 13:12:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dkCig-0002dN-HV for guix-patches@gnu.org; Tue, 22 Aug 2017 13:12:02 -0400 Subject: [bug#28045] [PATCH] gnu: Add openfoam Resent-Message-ID: Message-ID: <1503421859.3048.11.camel@tourbillion-technology.com> From: Paul Garlick Date: Tue, 22 Aug 2017 18:10:59 +0100 In-Reply-To: <87r2w369im.fsf@gnu.org> References: <20170811110636.23339-1-pgarlick@tourbillion-technology.com> <20170814214925.2cd96b3f@centurylink.net> <1502905946.2548.31.camel@tourbillion-technology.com> <17DA467A-7864-4EED-9F61-16D634A0B976@centurylink.net> <1502962978.2875.25.camel@tourbillion-technology.com> <87r2w369im.fsf@gnu.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 28045@debbugs.gnu.org Hi Ludo, > I think we should introduce a “scotch32” variant (with a clear > explanation of what the “32” means). I think this is the most flexible approach.  Packages could then select the standard 'scotch' or, if preferred, the 'scotch32' variant, if memory usage or performance is a concern. A method of implementing this would be for 'scotch32' to inherit the 'scotch' definition, replacing the configure phase with a similar section specifying INTSIZE32 instead of INTSIZE64.  This would be similar to the Debian approach, in which a different Makefile.inc is used for 32-bit and 64-bit integers. A new package 'pt-scotch32' would then be the same as 'pt-scotch' but inherit from 'scotch32' instead of 'scotch'. Any comments? Paul.