From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-5809-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 27093 invoked from network); 15 Mar 1999 11:45:06 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 15 Mar 1999 11:45:06 -0000
Received: (qmail 17390 invoked by alias); 15 Mar 1999 11:44:50 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 5809
Received: (qmail 17383 invoked from network); 15 Mar 1999 11:44:49 -0000
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Peter Stephenson" <pws@ibmth.df.unipi.it>,
        "Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: 3.1.5-pws-12: getcwd
Date: Mon, 15 Mar 1999 14:43:34 +0300
Message-ID: <002201be6ed9$0e804b00$21c9ca95@mowp.siemens.ru>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <9903151113.AA27244@ibmth.df.unipi.it>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211

>
> Another configure cock-up I made.  For the last couple of weeks
> everybody's
> been using the native getcwd() on every architecture.  The fact nobody's
> complained may be significant.
>

What is wrong with native getcwd? (Apart, that it may use native malloc() to
allocate buffer)? If there are any known problems, is it possible to write a
configure check for them?

/andrej