Hannu E K Nevalainen telia.com> writes:
> > Does anyone know of any reason an fopen on the
> > just-unlinked file would fail under Cygwin?
>
> IIRC this has been up earlier; unlink() isn't atomic.
Hence the loop. I'm sure I've even had to do this to this
exact file before (but I'm putting the
Blair P. Houghton houghton.net> writes:
>
> while(!unlink(...))
YAASA. STFU!
Figures, the moment I post that to the world I realize
that the ! looks hinky. Swot I get for not reading the
man-page for unlink(2) in about 20 years, and blindly
copying idioms I find in the common.
I forget. What's the command to dump the system config?
Here's what `uname -a' says:
CYGWIN_NT-5.1 eMachine64-3000 1.5.7(0.109/3/2) \
2004-01-30 19:32 i686 unknown unknown Cygwin
unlink(2) seems to be causing a subsequent fopen(3)
to fail. Originally, it was the unlink call that
failed, b
>> % cygcheck --version
>> cygcheck version 1.30
>> System Checker for Cygwin
>> Copyright 1998, 1999, 2000, 2001, 2002 Red Hat, Inc.
>> Compiled on Feb 8 2003
>
>FYI, this doesn't tell us anything about the version of Cygwin
D'oh!
--Blair
Peter Seebach wrote:
>In message <[EMAIL PROTECTED]>, Dario Alcocer writes:
>>Use the "set -- `getopt`" idiom instead:
>Yes, but *why*?
==
% cygcheck --version
cygcheck version 1.30
System Checker for Cygwin
Copyright 1998, 1999, 2000, 2001, 2002 Red Hat, Inc.
Compiled on Feb 8 2003
%
>The trailing backslashes aren't necessary. I've removed them in my LIB and
>INCLUDE environment variables and VC works just fine. You could try removing
>them and see if that fixes the perl build.
Well, you can remove them manually; but this is a computer and it should do the work.
The next
tim
win, that's an insecurity (although, as others have noted, if the calling context
is already
insecure, cygwin is hardly the place to expect an extra layer of armor).
--Blair
-Original Message-
From: Yitzchak Scott-Thoennes [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 28, 2003 6:25
u don't have to CC me, too.
-Original Message-
From: Charles Wilson [mailto:[EMAIL PROTECTED]
Sent: Monday, December 22, 2003 11:32 PM
To: Blair P. Houghton; [EMAIL PROTECTED]
Subject: Re: Is perl-5.8.2 canonized for use on cygwin yet?
Blair P. Houghton wrote:
> The people who
I wanted to add threading to perl, so I snarfed the
5.8.2 distro and tried to build it. I got through
Configure (not without a little Space Ace flashback,
mind you), but when I did make(1) it went down into the
B-module build and croaked. The error message is shown
below.
I hacked around in
9 matches
Mail list logo
