From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by coral.primenet.com.au (8.7.5/8.7.3) with ESMTP id DAA01837 for ; Wed, 21 Aug 1996 03:45:47 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id NAA18370; Tue, 20 Aug 1996 13:46:15 -0400 (EDT) Resent-Date: Tue, 20 Aug 1996 13:46:15 -0400 (EDT) Date: Tue, 20 Aug 1996 10:44:34 -0700 Message-Id: <199608201744.KAA10302@hiro.zanshin.com> From: Bob Glickstein To: schaefer@nbn.com CC: zsh-workers@math.gatech.edu In-reply-to: <960820102425.ZM7680@candle.brasslantern.com> (schaefer@candle.brasslantern.com) Subject: Re: 3.0.0 configure failure (bug in autoconf 2.10?) Organization: Zanshin Software, Inc. X-Attribution: BG Reply-to: Bob Glickstein Resent-Message-ID: <"prReG3.0.xU4.ddV6o"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2039 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu > Perhaps AC_CHECK_FUNCS is the wrong way to test for lstat? I don't > have autoconf 2.10 installed to check the info for a more specific > AC_* test. Well, there's AC_PROG_LN_S, which tests whether "ln -s" works; that should indirectly indicate the availability of lstat(). But AC_CHECK_FUNCS should work, and I consider it a bug in autoconf that it doesn't. I suggest sending a bug report to bug-gnu-utils@prep.ai.mit.edu.