Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <80575AFA5F0DD31197CE00805F650D7602CDF2@wilber.adroit.com> From: "Robinow, David" To: "'cygwin AT sources DOT redhat DOT com'" Subject: RE: latest cygwin does not track pwd? Date: Wed, 1 Nov 2000 14:34:43 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" > 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. OK, it's your call. For what it's worth Solaris and IRIX both require EINVAL. I can't think of why failure to return EINVAL would break something though. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com