From owner-freebsd-advocacy Mon Oct 5 12:28:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11002 for freebsd-advocacy-outgoing; Mon, 5 Oct 1998 12:28:03 -0700 (PDT) (envelope-from owner-freebsd-advocacy@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10908 for ; Mon, 5 Oct 1998 12:27:49 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id OAA21944 for ; Mon, 5 Oct 1998 14:27:24 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id OAA01594; Mon, 5 Oct 1998 14:26:51 -0500 Message-ID: <19981005142651.29722@right.PCS> Date: Mon, 5 Oct 1998 14:26:51 -0500 From: Jonathan Lemon To: advocacy@FreeBSD.ORG Subject: Re: PETSc Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I sent off a note to the PETSc maintainers last week and received a reply this morning. The upshot was: Their build environment does a lot of "include this/config/file" kind of syntax, and FreeBSD's make did not understand the "include ..." syntax. (Checking the CVS logs shows whether "include ..." is understood is contained within a SYSV compatability #define, which defaulted to "off" until 2 years ago.) I guess this also says something about the age of the system that they were using. They polled their mailing list of users, and only one user was using FreeBSD, and was also in the process of converting to Linux. So, given: 1. no FreeBSD demand for their software (according to their ftp logs), 2. no apparent users, and 3. an apparently broken make, I guess I can understand their wording. They did say that they would be changing the wording of the page to reflect the fact that the software will work with later versions of FBSD. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message