From owner-freebsd-current Mon Jun 10 8:39:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 4C7A337B408 for ; Mon, 10 Jun 2002 08:39:24 -0700 (PDT) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.3/8.12.2) with ESMTP id g5AFdLJn037660; Mon, 10 Jun 2002 08:39:21 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.3/8.12.3/Submit) id g5AFdLYD037659; Mon, 10 Jun 2002 08:39:21 -0700 (PDT) Date: Mon, 10 Jun 2002 08:39:21 -0700 From: "David O'Brien" To: Terry Lambert Cc: Stanislav Grozev , Shizuka Kudo , freebsd-current@freebsd.org Subject: Re: My postgresql7 not working for new gcc Message-ID: <20020610083921.A37639@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20020601195008.GJ17045@elvis.mu.org> <20020605113540.62177.qmail@web11402.mail.yahoo.com> <20020610115150.GA91765@meerkat.dungeon> <3D04B166.950171E2@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3D04B166.950171E2@mindspring.com>; from tlambert2@mindspring.com on Mon, Jun 10, 2002 at 07:02:14AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 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 On Mon, Jun 10, 2002 at 07:02:14AM -0700, Terry Lambert wrote: > > one messy and temporary solution is to compile with > > make CFLAGS=-Wp,-w CXXFLAGS=-Wp,-w > > which tells gcc to pass -w to the preprocessor, and -w means inhibit > > all warnings. with this, postgresql compiles and works fine. > > for 'correct' solution - the configure script for postgresql must be > > regenerated from configure.in, using the newer autoconf, but I am not > > sure whether that would be successfull, as there were (AFAIK), some > > incompatibilities between the two - but i may be wrong. > > anyway, HTH > > That's ugly. > > Since it's jamming in includes anyway: > > By using both `-nostdinc' and `-I-', you can limit > the include-file search file to only those directo- > ries you specify explicitly. > > e.g.: you should be able to get it to work with warnings fully > enabled, and explicit use of system include paths in the Makefile. > > This might be a more permanent fix... *sigh*, why not a *real* fix? --- configure.in.orig Thu Sep 27 01:03:56 2001 +++ configure.in Mon Apr 29 13:20:27 2002 @@ -200,7 +200,9 @@ done if test "$ac_found_openssl_lib_dir" != "no"; then echo "found in $ac_found_openssl_lib_dir" - INCLUDES="-I$ac_found_openssl_inc_dir $INCLUDES" + if test "$ac_found_openssl_inc_dir" != "/usr/include"; then + INCLUDES="-I$ac_found_openssl_inc_dir $INCLUDES" + fi DEFINES="-DOPENSSL $DEFINES" else echo "not found." You'll note that they bother with this kind of check for other headers, but for some reason didn't consider it for openssl headers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message