zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Bob Glickstein <bobg@ipost.com>
Cc: zsh-workers@math.gatech.edu
Subject: Re: 3.0.0 configure failure (bug in autoconf 2.10?)
Date: Tue, 20 Aug 1996 10:24:25 -0700	[thread overview]
Message-ID: <960820102425.ZM7680@candle.brasslantern.com> (raw)
In-Reply-To: Bob Glickstein <bobg@ipost.com> "Re: 3.0.0 configure failure (bug in autoconf 2.10?)" (Aug 20,  8:16am)

On Aug 20,  8:16am, Bob Glickstein wrote:
} Subject: Re: 3.0.0 configure failure (bug in autoconf 2.10?)
}
} > So just exactly who is wrong here?  autoconf?  gcc 2.7.0?
} 
} It could be either.  What causes the autoconf 2.10 version of the
} lstat test to fail?  (Find out by looking in config.log after running
} configure.)

I included that in the original message.

/tmp/cca194791.o(.text+0x14): undefined reference to `lstat'

That's all, nothing else.  I just figured out why it fails, though:  lstat
is an *inline function only* that expands to a call to _lxstat.  If you
don't include <sys/stat.h> (which the conftest does not), you can't detect
lstat.

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.

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern

New male in /home/schaefer:
>N  2 Justin William Schaefer  Sat May 11 03:43  53/4040  "Happy Birthday"


  reply	other threads:[~1996-08-20 17:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-08-20  5:43 Bart Schaefer
1996-08-20 15:16 ` Bob Glickstein
1996-08-20 17:24   ` Bart Schaefer [this message]
1996-08-20 17:44     ` Bob Glickstein
1996-08-22 20:43 ` Zoltan Hidvegi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=960820102425.ZM7680@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=bobg@ipost.com \
    --cc=schaefer@nbn.com \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).