git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Riesen" <raa.lkml@gmail.com>
To: "John Freeman" <jfreeman@cs.tamu.edu>
Cc: git@vger.kernel.org
Subject: Re: clone fails: Could not get the current working directory
Date: Wed, 24 Sep 2008 13:30:45 +0200	[thread overview]
Message-ID: <81b0412b0809240430y682d6dd9wef801c33a6ee2f85@mail.gmail.com> (raw)
In-Reply-To: <48D95C96.4030906@cs.tamu.edu>

2008/9/23 John Freeman <jfreeman@cs.tamu.edu>:
> Alex Riesen wrote:
>> Again: try a simple program which just does getpwd for this pathname
>
> From what I gather, getpwd() is in libiberty, which I didn't feel like
> messing with for this example.  I ran a small test program that called
> getcwd() in the repo directory, and it failed.  errno was set to EACCES,
> indicating insufficient permissions.

So there we are...

> http://www.opengroup.org/onlinepubs/009695399/functions/getcwd.html

It suggest a rather dubious workaround (calling pwd).

> I may get around later to patching this, but for now we're moving ahead with
> a workaround.

...but that's a system-inflicted workaround. We just have to do it or something
like what it does.

General question: What does Sun's pwd do?

  reply	other threads:[~2008-09-24 11:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21  0:49 clone fails: Could not get the current working directory John Freeman
     [not found] ` <d3a045300809211012l35b1ec2dq39f4174170d8c926@mail.gmail.com>
2008-09-21 22:18   ` John Freeman
2008-09-22 18:32     ` John Freeman
2008-09-23 12:39 ` Alex Riesen
2008-09-23 13:23   ` John Freeman
2008-09-23 14:12     ` Alex Riesen
2008-09-23 14:45       ` John Freeman
2008-09-23 15:01         ` Alex Riesen
2008-09-23 21:16           ` John Freeman
2008-09-24 11:30             ` Alex Riesen [this message]
2008-09-24 13:30               ` John Freeman
2008-09-24 14:43                 ` Alex Riesen

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=81b0412b0809240430y682d6dd9wef801c33a6ee2f85@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jfreeman@cs.tamu.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. 
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).