On 09/18/11 12:11, Jim Meyering wrote:
> Since kFreeBSD also lacks /proc/self/fd support, this has the
> drawback of making getcwd non-thread-safe, and making it possible
> that getcwd will exit under some unusual conditions. But neither
> of those matter to coreutils,
I doubt whether the
Jim Meyering wrote:
> Michael Stone wrote:
>> On Fri, Sep 16, 2011 at 06:54:32PM +0200, Jim Meyering wrote:
>>>Michael Stone wrote:
This one was actually in gnulib; what's the best way to pursue it?
FAIL: test-getcwd (exit: 16)
>>>
>>>Hi Michael,
>>>
(dropped the cc by accident)
- Forwarded message from Michael Stone -
On Fri, Sep 16, 2011 at 09:02:20PM +0200, you wrote:
Then maybe your system has problems with long names?
What is errno when getcwd returns NULL here?
also ENOENT
/* If libc has the bug in question, this invocati
Michael Stone wrote:
> On Fri, Sep 16, 2011 at 06:54:32PM +0200, Jim Meyering wrote:
>>Michael Stone wrote:
>>> This one was actually in gnulib; what's the best way to pursue it?
>>>
>>> FAIL: test-getcwd (exit: 16)
>>>
>>
>>Hi Michael,
>>
>>Thanks for the report.
>>I'
On Fri, Sep 16, 2011 at 06:54:32PM +0200, Jim Meyering wrote:
Michael Stone wrote:
This one was actually in gnulib; what's the best way to pursue it?
FAIL: test-getcwd (exit: 16)
Hi Michael,
Thanks for the report.
I'll Cc bug-gnulib, but to start with, note that
Michael Stone wrote:
> This one was actually in gnulib; what's the best way to pursue it?
>
> FAIL: test-getcwd (exit: 16)
>
Hi Michael,
Thanks for the report.
I'll Cc bug-gnulib, but to start with, note that test-getcwd.c's main
does this:
return test_abort_bug ()
