From owner-freebsd-questions Mon Jul 23 11:40:11 2001 Delivered-To: freebsd-questions@freebsd.org Received: from comp04.prc.uic.edu (comp04.prc.uic.edu [128.248.230.104]) by hub.freebsd.org (Postfix) with SMTP id 61E3737B407 for ; Mon, 23 Jul 2001 11:40:06 -0700 (PDT) (envelope-from lucas@comp04.prc.uic.edu) Received: (qmail 76159 invoked by uid 1000); 23 Jul 2001 18:40:02 -0000 Date: Mon, 23 Jul 2001 13:40:02 -0500 From: Lucas Bergman To: "f.johan.beisser" Cc: Peter Brezny , freebsd-questions@FreeBSD.ORG Subject: Re: configure question Message-ID: <20010723134002.B74870@comp04.prc.uic.edu> Reply-To: iceberg@pobox.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jan@caustic.org on Mon, Jul 23, 2001 at 10:39:26AM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Peter Brezny wrote: > > > When installing something from source, for instance apache_modssl, > > if you perform a > > [asks if ./configure with new options overwrites configuration] f.johan.beisser wrote: > > yes. it does. Quite right. One caveat, though, is that GNU configure scripts (the vast majority of them) cache some of the results found in the configure scripts. So, for example, if you run configure, then install a library (say, GTK) that you didn't have before, then rerun configure, it may not catch the new library, because of the cache. So, in some situations, you need to blow away config.cache before re-running configure to get certain changes to take effect. > this is technically not freebsd related. please try to keep your > posts on topic. True enough. However, I'm hard pressed to think of another forum that is more appropriate. If Peter's question were something like, "I can't get AC_FOO() to work in my project's configure.in," then I would certainly direct him to an autoconf group. Lucas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message