zsh-workers
 help / color / mirror / code / Atom feed
From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: guthrie@math.upenn.edu (John Guthrie)
Cc: zsh-workers@math.gatech.edu
Subject: Re: configure on linux
Date: Mon, 8 Jul 1996 18:32:46 +0200 (MET DST)	[thread overview]
Message-ID: <199607081632.SAA07164@bolyai.cs.elte.hu> (raw)
In-Reply-To: <199607081611.MAA16536@hans.math.upenn.edu> from John Guthrie at "Jul 8, 96 12:11:07 pm"

> zsh-3.0-pre2 compiles fine on linux, with a few warnings.  However, for the
> past several releases, configure has always failed to successfully determine
> that lstat is in fact on my system.  Here are the relevant lines from

It seems that you did not read Etc/MACHINES despite the note at the very
beginning of the README.  I quote the relevant part:

Linux:  If you are using an early minor version of libc 5, then a bug
        in the auto-configuration process may cause zsh to think that
        your system doesn't support the lstat function.  If the
        configure process reports that there is no lstat, edit
        config.h and change HAVE_LSTAT to 1.
        libc-5.2.18 or later does not have this problem.

Perhaps you use libc-5.0.9.  It is really time to upgrade now, especially
if you want to use Linux-2.0.  I think it is very unlikely that autoconf
will be fixed so if you do not want to upgrade your libc, manually editing
config.h seems to be the only solution.  As an alternative you may edit
config.cache and change ac_cv_func_lstat='no' to ac_cv_func_lstat='yes'.
Next time when configure finds this cache in the current directory it will
use the information provided there.

Zoltan



  reply	other threads:[~1996-07-08 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-08 16:11 John Guthrie
1996-07-08 16:32 ` Zoltan Hidvegi [this message]
1996-07-08 19:01 guthrie

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=199607081632.SAA07164@bolyai.cs.elte.hu \
    --to=hzoli@cs.elte.hu \
    --cc=guthrie@math.upenn.edu \
    --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).