From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 17 16:08:20 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6802D244 for ; Wed, 17 Jul 2013 16:08:20 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog105.obsmtp.com (eu1sys200aog105.obsmtp.com [207.126.144.119]) by mx1.freebsd.org (Postfix) with ESMTP id BC1B6AE4 for ; Wed, 17 Jul 2013 16:08:19 +0000 (UTC) Received: from mail-we0-f172.google.com ([74.125.82.172]) (using TLSv1) by eu1sys200aob105.postini.com ([207.126.147.11]) with SMTP ID DSNKUebBcksbQUbcO2Xkkjxr94Yo3WmuVBOT@postini.com; Wed, 17 Jul 2013 16:08:19 UTC Received: by mail-we0-f172.google.com with SMTP id q56so2001441wes.3 for ; Wed, 17 Jul 2013 09:08:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:cc:reply-to :x-gm-message-state; bh=kednhSqKrT+WQBD8Zj/cLLKdW6u8CT37fbV7PXMJtjU=; b=FUHJou3cvt4VN5EujHVgdMMgi9tq3BYfOITiKvIBBX+ck8FoDAC5JI/Mr7NAASwOVv vIEQXnK4LMBnZhBQGsHr3O6N2i9cXiq9ShMK9g8diqgbq+mrmJ1XMaC8CPbBzvB1t8b0 Gln2cTSShIa66OW5J3rjQGk9pW+LkYYm7/w0SJPn/XzqE5pilFNqbhJs2wHQ8jemUQ1X 9wUyrZyotfYfM+xEYTAcf3PjuxOnInz89fY4SZ3i5uDXdfipd4/8AFsjavUPHnqzClYI a4LnxWIZh2Jh+DcOQGwwaItiAF8tTAHfAkMT8nwTcSinj4YJXRhCREO4730qfbvA6Yi9 pMHg== X-Received: by 10.180.206.70 with SMTP id lm6mr16418869wic.50.1374077298401; Wed, 17 Jul 2013 09:08:18 -0700 (PDT) X-Received: by 10.180.206.70 with SMTP id lm6mr16418865wic.50.1374077298337; Wed, 17 Jul 2013 09:08:18 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id d8sm10730915wiz.0.2013.07.17.09.08.16 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Jul 2013 09:08:17 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6HG8FgL022827 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 17 Jul 2013 17:08:15 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6HG8Eo2022826; Wed, 17 Jul 2013 17:08:14 +0100 (BST) (envelope-from mexas) Date: Wed, 17 Jul 2013 17:08:14 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307171608.r6HG8Eo2022826@mech-cluster241.men.bris.ac.uk> To: fortran@freebsd.org Subject: objections to MAINTAINER=fortran@ in devel/fpp X-Gm-Message-State: ALoCoQkP1038DLydrYPVn1KJCwlYOlYYPSyJ6Gs+kg1y9cCMHfBcKG1liA9cUWgEgS3m2SFTjdHdtOv3tK8OSeOrcaYXnarZUEIZPBNmi85lBbjvjttrmo/YyHvliPAbvEUyh82hBIyfvu9LgakknaGyqT9gvktkwg== Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 16:08:20 -0000 (copy to ports@ in case some users of devel/fpp are not on fortran@) devel/fpp is a Fortran pre-processor. It is unmaintained. I think fortran@ list is the most logical maintainer. Any objections? Anton P.S. I just updated devel/fpp to conform to the latest ports framework. The port is old, but builds and works. However, I don't really use it, so don't want to maintain it myself. From owner-freebsd-fortran@FreeBSD.ORG Sat Jul 20 17:45:28 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9CCEC7E5 for ; Sat, 20 Jul 2013 17:45:28 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog118.obsmtp.com (eu1sys200aog118.obsmtp.com [207.126.144.145]) by mx1.freebsd.org (Postfix) with ESMTP id EFD23CF4 for ; Sat, 20 Jul 2013 17:45:27 +0000 (UTC) Received: from mail-we0-f179.google.com ([74.125.82.179]) (using TLSv1) by eu1sys200aob118.postini.com ([207.126.147.11]) with SMTP ID DSNKUerMsHa2r9XbI8Gns0JU9p9Iagd0dgbd@postini.com; Sat, 20 Jul 2013 17:45:28 UTC Received: by mail-we0-f179.google.com with SMTP id t57so82282wes.10 for ; Sat, 20 Jul 2013 10:45:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:reply-to:x-gm-message-state; bh=hSsv3l+Cslo0jxNOyjyqXs8rJyRFVNgK32Q/5Z9IVSw=; b=Un0TIWzlHT2suOHv+jEFk/CfD6OTg6dKIXISdr5YpR56Sp/mJtvzOOISBqxMhyHeUr yJe+74vAdTIwtwyVcq01+7JsHBrsxaT2+kb2VN51Cw5yTY4DdrSMeCzh60hm3K6ju8+V l03ojSxydyzO000N6VpSm4GnZ5W+xTM+Mw6dwkz5ved5/l1vpW4leXnhHeT1BP6NJOa+ vUiUQ0HUS3Uc8FX0KTexVYK/mI+/xWouTFdk2rbJME+rpWJcnoG6Ne+0F4sWVj6jj+km eH4DUCZ5Kf+IDJzqjiwj9S7YAI72RYXayR9EygPHxGSTE17F6KjwTdcUDSwrY2eO0SH6 6bTQ== X-Received: by 10.194.80.134 with SMTP id r6mr15184008wjx.88.1374341868615; Sat, 20 Jul 2013 10:37:48 -0700 (PDT) X-Received: by 10.194.80.134 with SMTP id r6mr15184005wjx.88.1374341868516; Sat, 20 Jul 2013 10:37:48 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id f8sm3956872wiv.0.2013.07.20.10.37.46 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 20 Jul 2013 10:37:47 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6KHbjmD009229 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 20 Jul 2013 18:37:45 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6KHbjSS009228 for fortran@freebsd.org; Sat, 20 Jul 2013 18:37:45 +0100 (BST) (envelope-from mexas) Date: Sat, 20 Jul 2013 18:37:45 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307201737.r6KHbjSS009228@mech-cluster241.men.bris.ac.uk> To: fortran@freebsd.org Subject: math/slatec - worth fixing deleted language features? X-Gm-Message-State: ALoCoQkYpizKBO+qYpse8qDZZXVoFXr3+e2Myf/Tci5HdcXXzIfvZaPUGZLOzzd2J4a0iNOd9AKuLuEwLy9i074i41t+4vf1tAkANK9St/kGLt7qmRyZq1RaIdyF9aaOSHQwG+E+O9y6zVLj7r4LGUhEQQ/iP5rRVw== X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bris.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 17:45:28 -0000 Anybody uses math/slatec? This is a collection of >1400 f77 routines. The problem is that there is no upstream anymore, and the code has deleted features, e.g.: dplpmn.f:216.72: 20019 ASSIGN 20020 TO NPR007 1 Warning: Deleted feature: ASSIGN statement at (1) dplpmn.f:624.18: GO TO NPR005, (20018,20154,20243) 1 Warning: Deleted feature: Assigned GOTO statement at (1) The full log: https://redports.org/~mexas/20130719210000-42286-133231/slatec-4.1.log Fixing each individual deleted feature is not that hard. However, there are a lot of those. In addition, there is a risk of introducing new bugs. The library, as it is, is supposed to be thoroughly tested. So I'll asking for opinions on what to do with math/slatec; (1) nothing - leave as it is, (2) try updating deleted (and obsolete) language constructs, (3) spawn another port, with no deleted or obsolete features, but with little testing? Anton From owner-freebsd-fortran@FreeBSD.ORG Sat Jul 20 20:38:35 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3C78D9A4 for ; Sat, 20 Jul 2013 20:38:35 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 07F382E6 for ; Sat, 20 Jul 2013 20:38:35 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r6KKQetO068508; Sat, 20 Jul 2013 13:26:40 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r6KKQeiM068507; Sat, 20 Jul 2013 13:26:40 -0700 (PDT) (envelope-from sgk) Date: Sat, 20 Jul 2013 13:26:40 -0700 From: Steve Kargl To: Anton Shterenlikht Subject: Re: math/slatec - worth fixing deleted language features? Message-ID: <20130720202640.GA68466@troutmask.apl.washington.edu> References: <201307201737.r6KHbjSS009228@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201307201737.r6KHbjSS009228@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 20:38:35 -0000 On Sat, Jul 20, 2013 at 06:37:45PM +0100, Anton Shterenlikht wrote: > Anybody uses math/slatec? I don't use it currently. When I was actively contributing to gfortran (to ensure that gfortran worked on FreeBSD), I fed routinely fed slatec into gfortran looking for bugs. > This is a collection of >1400 f77 routines. > The problem is that there is no upstream anymore, > and the code has deleted features, e.g.: (snip) > Fixing each individual deleted feature is not that hard. There is nothing to fix. You will be hard pressed to find a Fortran, which works on FreeBSD, that does not support the deleted features used by slatec. > In addition, there is a risk of introducing new bugs. > The library, as it is, is supposed to be thoroughly tested. This is why compilers still support the deleted features. Code written 50 years will still compile and work. > > So I'll asking for opinions on what to do > with math/slatec; (1) nothing - leave as it is, yes > (2) try updating deleted (and obsolete) language constructs, No. Do nothing. If the warnings bother you, add FFLAGS+=-w or FFLAGS+=-std=legacy to the Makefile. > (3) spawn another port, with > no deleted or obsolete features, but with little testing? Do nothing. -- Steve