Hi,
I don't get SIGPOLL on Cygwin in a software that runs fine on Linux and
Solaris. Is there a known issue concerning SIGPOLL and named pipes.
The setup code looks like this:
Input = open(optarg,O_RDONLY);
if (Input == -1)
error("could not open input file %s: %s\n",optarg,strerror(errno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** perl-ExtUtils-Depends-0.300-2
This release includes a patch, combined with perl-5.10.0-5, which allows
the linking of Gtk2-Perl modules without further intervention. cygport
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** cygport-0.3.13-1
This is the latest release of the cygport package building tool.
Please note that this version of cygport is meant solely for Cygwin 1.5.
The next release fr
Is it possible that there is somewhere a race condition in the
cygwin.dll that causes the reader on a named pipe getting a return value
of 0 from read, although another process has already opened the named
pipe for writing.
In consequence, in my application I see sporadic occurrences of SIGPIPE,
w
On Sun, Aug 24, 2008 at 01:47:56PM +0200, Thomas Maier-Komor wrote:
>I don't get SIGPOLL on Cygwin in a software that runs fine on Linux and
>Solaris. Is there a known issue concerning SIGPOLL and named pipes.
SIGPOLL (aka SIGIO) is not implemented in Cygwin.
>Additionally, there seem to be a bu
2008/8/24 Yaakov (Cygwin Ports):
> This release includes a patch, combined with perl-5.10.0-5, which allows
> the linking of Gtk2-Perl modules without further intervention. cygport
> will soon require this release for gtk2-perl.cygclass.
Did you look into the root cause for this headache, libtoo
Greetings:
~ $ date;cygcheck -c cygwin
Sun Aug 24 11:37:36 CDT 2008
Cygwin Package Information
Package VersionStatus
cygwin 1.5.25-15 OK
~ $ "$COMSPEC"
-bash: D:\WINNT\system32\cmd.exe: command not found
~ $ ls -l "$COMSPEC"
-rwxrwxr-x+ 1 A
Christopher Faylor wrote:
> On Sun, Aug 24, 2008 at 01:47:56PM +0200, Thomas Maier-Komor wrote:
>> I don't get SIGPOLL on Cygwin in a software that runs fine on Linux and
>> Solaris. Is there a known issue concerning SIGPOLL and named pipes.
>
> SIGPOLL (aka SIGIO) is not implemented in Cygwin.
>
On Sun, Aug 24, 2008 at 07:29:59PM +0200, Thomas Maier-Komor wrote:
>OK, thanks for the information. Do you know when 1.7 is planned to be
>released?
Yes, but I'm not telling.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problem
On Sun, 24 Aug 2008, Christopher Faylor wrote:
On Sun, Aug 24, 2008 at 07:29:59PM +0200, Thomas Maier-Komor wrote:
OK, thanks for the information. Do you know when 1.7 is planned to be
released?
Yes, but I'm not telling.
CGF,YABM!
-Steve
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
> Did you look into the root cause for this headache, libtool?
The gtk2-perl hack had nothing to do with libtool, it had to do with the
unique case of linking one Perl module against another. I was referring
to the EU::Liblist::K
Tom Rodman wrote:
Greetings:
~ $ date;cygcheck -c cygwin
Sun Aug 24 11:37:36 CDT 2008
Cygwin Package Information
Package VersionStatus
cygwin 1.5.25-15 OK
~ $ "$COMSPEC"
-bash: D:\WINNT\system32\cmd.exe: command not found
~ $ ls -l "$COMSPE
> Apparently my understanding of FAT is wrong then.
> Brian
FAT stores Unicode on disk, if necessary, as part of the "long name" support.
That is, if a name happens to be 8.3, both in length and character set "etc.",
it occupies just one "normal" directory entry.
If a name is not 8.3, either
Yaakov (Cygwin Ports) schrieb:
Reini Urban wrote:
Did you look into the root cause for this headache, libtool?
The gtk2-perl hack had nothing to do with libtool, it had to do with the
unique case of linking one Perl module against another. I was referring
to the EU::Liblist::Kid patch we disc
Reini Urban wrote:
> Sure. Fixing libtool of course.
> Mixing static and dynamic libs should be possible.
I think you're missing the point of why libtool disallows it: not
because it won't work in a specific instance, but because it is not
portable. There is no fix for the fact that on some syst
2008/8/24 Brian Dessent:
> Reini Urban wrote:
>
>> Sure. Fixing libtool of course.
>> Mixing static and dynamic libs should be possible.
>
> I think you're missing the point of why libtool disallows it: not
> because it won't work in a specific instance, but because it is not
> portable. There is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin Ports) wrote:
> With 1.7, there is no such issue; make manifypods builds OOTB. So any
> such workaround would have to be caught in the cygport postinstall
> stage, maybe in __prepman(). But I'm not sure that it would be at all
> nece
Re:-
Note that the official support for Windows 95, Windows 98, and Windows Me
will be discontinued with the >
next major version (1.7.0) of Cygwin.
Its bad enough having to use windows, but having to upgrade to XP or VISTA
is just out of the question. Looks like I won't be using any new versi
You're missing the best version of Windows that ever exist, Windows 2000.
On Mon, Aug 25, 2008 at 2:10 AM, Trans-Mit Support
<[EMAIL PROTECTED]> wrote:
> Re:-
>>
>> Note that the official support for Windows 95, Windows 98, and Windows Me
>> will be discontinued with the >
>> next major version (1
19 matches
Mail list logo
