On Aug 18 16:29, Achim Gratz wrote:
> Corinna Vinschen writes:
> > There's no xlocale.h on Linux either. What do these packages do in
> > that case?
>
> I've dug a little bit deeper. The trouble is that perl.h has picked up
> xlocale.h as the location of some of the interfaces it wants to use
>
Corinna Vinschen writes:
> There's no xlocale.h on Linux either. What do these packages do in
> that case?
I've dug a little bit deeper. The trouble is that perl.h has picked up
xlocale.h as the location of some of the interfaces it wants to use
during configuration, so that means you can't comp
On Aug 18 14:06, Achim Gratz wrote:
> Corinna Vinschen writes:
> > - Eliminate a header file name collision with on case
> > insensitive filesystems by reverting back to .
>
> What's the suggested way to deal with software that expects to be able
> to "#include "? I think I'll see that more o
Corinna Vinschen writes:
> - Eliminate a header file name collision with on case
> insensitive filesystems by reverting back to .
What's the suggested way to deal with software that expects to be able
to "#include "? I think I'll see that more often than X11
applications that have their inclu
On Aug 18 01:43, Takashi Yano wrote:
> Hi Corinna,
>
> On Fri, 16 Aug 2019 16:48:11 +0200
> Corinna Vinschen wrote:
> > I now had an idea, but I'm not entirely sure if it's the right thing to
> > do. Can you please test this? It consists of two patches, one with the
> > revamped signalfd handlin
Hi Corinna,
On Fri, 16 Aug 2019 16:48:11 +0200
Corinna Vinschen wrote:
> I now had an idea, but I'm not entirely sure if it's the right thing to
> do. Can you please test this? It consists of two patches, one with the
> revamped signalfd handling, and one with the revert of the signalfd
> patch
Hi Takashi,
On Aug 15 17:09, Corinna Vinschen wrote:
> On Aug 15 17:04, Corinna Vinschen wrote:
> > On Aug 15 12:36, Corinna Vinschen wrote:
> > > On Aug 15 09:49, Corinna Vinschen wrote:
> > > > On Aug 15 04:21, Takashi Yano wrote:
> > > > > On Wed, 14 Aug 2019 15:49:00 +0200
> > > > > Corinna Vi
On Aug 15 17:04, Corinna Vinschen wrote:
> On Aug 15 12:36, Corinna Vinschen wrote:
> > On Aug 15 09:49, Corinna Vinschen wrote:
> > > On Aug 15 04:21, Takashi Yano wrote:
> > > > On Wed, 14 Aug 2019 15:49:00 +0200
> > > > Corinna Vinschen wrote:
> > > > > The only reason I can see is if sigwait_co
On Aug 15 12:36, Corinna Vinschen wrote:
> On Aug 15 09:49, Corinna Vinschen wrote:
> > On Aug 15 04:21, Takashi Yano wrote:
> > > On Wed, 14 Aug 2019 15:49:00 +0200
> > > Corinna Vinschen wrote:
> > > > The only reason I can see is if sigwait_common() returns EINTR because
> > > > it was interrupt
On Aug 15 09:49, Corinna Vinschen wrote:
> On Aug 15 04:21, Takashi Yano wrote:
> > On Wed, 14 Aug 2019 15:49:00 +0200
> > Corinna Vinschen wrote:
> > > The only reason I can see is if sigwait_common() returns EINTR because
> > > it was interrupted by an unrelated signal. This in turn lets the rea
On Aug 15 04:21, Takashi Yano wrote:
> On Wed, 14 Aug 2019 15:49:00 +0200
> Corinna Vinschen wrote:
> > The only reason I can see is if sigwait_common() returns EINTR because
> > it was interrupted by an unrelated signal. This in turn lets the read()
> > call fail with EINTR and that should be exp
On Wed, 14 Aug 2019 15:49:00 +0200
Corinna Vinschen wrote:
> The only reason I can see is if sigwait_common() returns EINTR because
> it was interrupted by an unrelated signal. This in turn lets the read()
> call fail with EINTR and that should be expected by the callers, in
> theory.
Strangely,
On Aug 14 20:47, Takashi Yano wrote:
> On Wed, 14 Aug 2019 20:41:00 +0900
> Takashi Yano wrote:
> > Hi Corinna,
> >
> > On Tue, 13 Aug 2019 12:47:53 +0200
> > Corinna Vinschen wrote:
> > > I created a patch which *seems* to do the right thing. I'm not
> > > yet sure it's the best solution, but it
On Wed, 14 Aug 2019 20:41:00 +0900
Takashi Yano wrote:
> Hi Corinna,
>
> On Tue, 13 Aug 2019 12:47:53 +0200
> Corinna Vinschen wrote:
> > I created a patch which *seems* to do the right thing. I'm not
> > yet sure it's the best solution, but it seems to do the trick, at
> > least.
> >
> > I'm ju
Hi Corinna,
On Tue, 13 Aug 2019 12:47:53 +0200
Corinna Vinschen wrote:
> I created a patch which *seems* to do the right thing. I'm not
> yet sure it's the best solution, but it seems to do the trick, at
> least.
>
> I'm just creating new developer snapshots, please try. I'll
> create another t
On Tue, 13 Aug 2019 23:50:54 +0200
Thorsten Kampe wrote:
> > I compiled tree
> > (http://mama.indstate.edu/users/ice/tree/src/tree-1.8.0.tgz).
> >
> > Mintty: 2.5s
> > Cmd: 122s
> >
> > Make clean[1]:
> > Mintty: 0.3s
> > Cmd: 60,3s
>
> A second compile took even three minutes:
> real3m1,82
* Takashi Yano (Tue, 13 Aug 2019 04:44:51 +0900)
> I looked into this problem, and found that this is due to a
> bug of ConEmu.
>
> Attached is the simple test case (conemu-chk.c).
> In command prompt, the output of this program is:
> AAA
> BBB
>
> However, in ConEmu, the output is:
> AAA
>BB
* Thorsten Kampe (Tue, 13 Aug 2019 23:45:14 +0200)
> The issue is definitely not just with ConEmu but also with a
> standard Windows console (cmd.exe).
>
> I compiled tree
> (http://mama.indstate.edu/users/ice/tree/src/tree-1.8.0.tgz).
>
> Mintty: 2.5s
> Cmd: 122s
>
> Make clean[1]:
> Mintty:
* Corinna Vinschen (Mon, 12 Aug 2019 15:01:52 +0200)
>
> On Aug 11 09:27, Thorsten Kampe wrote:
> > * Corinna Vinschen (Fri, 9 Aug 2019 20:53:38 +0200)
> > > I uploaded a new Cygwin test release 3.1.0-0.1
> > >
> > > This release comes with a couple of new features and quite a few
> > > bug fixes
On Aug 12 17:36, Corinna Vinschen wrote:
> On Aug 12 22:44, Takashi Yano wrote:
> > [...]
> > (4) Segmentation fault occurs in some cases regarding signalfd.
> > [...]
> > However, I can not find out the cause of problem (4). This seems
> > to affect only 32bit version of cygwin.
> >
> > To reprod
On Mon, 12 Aug 2019 15:01:52 +0200
Corinna Vinschen wrote:
> On Aug 11 09:27, Thorsten Kampe wrote:
> > * Corinna Vinschen (Fri, 9 Aug 2019 20:53:38 +0200)
> > > I uploaded a new Cygwin test release 3.1.0-0.1
> > >
> > > This release comes with a couple of new features and quite a few
> > > bug fi
On Aug 12 22:44, Takashi Yano wrote:
> [...]
> (4) Segmentation fault occurs in some cases regarding signalfd.
> [...]
> However, I can not find out the cause of problem (4). This seems
> to affect only 32bit version of cygwin.
>
> To reproduce (4), use a simple test case attached (signalfd-chk.c)
Hi Corinna,
On Fri, 9 Aug 2019 20:53:38 +0200
Corinna Vinschen wrote:
> Hi folks,
>
>
> I uploaded a new Cygwin test release 3.1.0-0.1
>
> This release comes with a couple of new features and quite a few
> bug fixes.
>
> The most interesting change, courtesy Ken Brown, is a revamp of the
> o
On Aug 11 09:27, Thorsten Kampe wrote:
> * Corinna Vinschen (Fri, 9 Aug 2019 20:53:38 +0200)
> > I uploaded a new Cygwin test release 3.1.0-0.1
> >
> > This release comes with a couple of new features and quite a few
> > bug fixes.
> >
> > The most interesting change, courtesy Ken Brown, is a rev
* Corinna Vinschen (Fri, 9 Aug 2019 20:53:38 +0200)
> I uploaded a new Cygwin test release 3.1.0-0.1
>
> This release comes with a couple of new features and quite a few
> bug fixes.
>
> The most interesting change, courtesy Ken Brown, is a revamp of the
> old FIFO code. It should now be possibl
Hi folks,
I uploaded a new Cygwin test release 3.1.0-0.1
This release comes with a couple of new features and quite a few
bug fixes.
The most interesting change, courtesy Ken Brown, is a revamp of the
old FIFO code. It should now be possible to open FIFOs multiple times
for writing, something
26 matches
Mail list logo
