Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 1 Nov 2000 14:40:48 -0500 From: Christopher Faylor To: "'cygwin@sources.redhat.com'" Subject: Re: latest cygwin does not track pwd? Message-ID: <20001101144048.C16358@redhat.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: "'cygwin@sources.redhat.com'" References: <80575AFA5F0DD31197CE00805F650D7602CDF1@wilber.adroit.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <80575AFA5F0DD31197CE00805F650D7602CDF1@wilber.adroit.com>; from drobinow@dayton.adroit.com on Wed, Nov 01, 2000 at 02:18:23PM -0500 On Wed, Nov 01, 2000 at 02:18:23PM -0500, Robinow, David wrote: >> It's definitely 'getcwd(NULL, 0)' in Chuck's sources. > Also in 5.7.0 development sources. >> I think I'll just revert the behavior. It appears that a number of >> packages are expecting it. > Is there a reason these packages can't be fixed? > Is 'getcwd(NULL, -1)' broken in some version? Not that I know of, but Corinna has pointed out that some versions of linux suggest that getcwd(NULL, 0) is ok and, possibly, BSD allows this construction. So, I think we'll be constantly responding to this on the mailing list. I'd rather just "fix" cygwin. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com