From owner-freebsd-current Mon Jun 10 21:56:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id D725637B40B; Mon, 10 Jun 2002 21:56:08 -0700 (PDT) Received: from pool0454.cvx22-bradley.dialup.earthlink.net ([209.179.199.199] helo=mindspring.com) by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #2) id 17Hdgt-0000Ct-00; Mon, 10 Jun 2002 21:55:37 -0700 Message-ID: <3D05824A.4261352B@mindspring.com> Date: Mon, 10 Jun 2002 21:53:30 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Shizuka Kudo Cc: obrien@freebsd.org, Stanislav Grozev , freebsd-current@freebsd.org Subject: Re: My postgresql7 not working for new gcc References: <20020611030445.20140.qmail@web11406.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Shizuka Kudo wrote: > I don't think autoconf was called in postgresql7 port, > and patching configure is necessary. It's derived data, and the patches will likely not remain valid after the next release/upgrade. That basically means that the way to correct your complaint about autoconf not being run is to make the port Makefile run autoconf. A patch to a derived file is not one that will make it back into the project source tree. If the patch isn't one that the Postgres people will accept, it's probably a bad patch. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message