On 2/4/19 3:25 PM, Corinna Vinschen wrote:
> On Feb 4 14:19, Michael Haubenwallner wrote:
>> On 2/3/19 12:19 PM, Corinna Vinschen wrote:
>>> On Jan 31 20:48, Corinna Vinschen wrote:
On Jan 31 09:47, Michael Haubenwallner wrote:
> Hi Corinna,
>
> I'm missing that topic/forkables br
On Feb 5 09:42, Michael Haubenwallner wrote:
> On 2/4/19 3:25 PM, Corinna Vinschen wrote:
> > Are you going to test the patched branch?
>
> Sorry, was indeed unclear: Yes, of course!
> Will start testing on Server 2012 while setting up a 2019 VM.
>
> For now, there's already this one patch I've
On 2/5/19 10:44 AM, Corinna Vinschen wrote:
> On Feb 5 09:42, Michael Haubenwallner wrote:
>> On 2/4/19 3:25 PM, Corinna Vinschen wrote:
>>> Are you going to test the patched branch?
>>
>> Sorry, was indeed unclear: Yes, of course!
>> Will start testing on Server 2012 while setting up a 2019 VM.
On Feb 5 12:28, Michael Haubenwallner wrote:
>
> On 2/5/19 10:44 AM, Corinna Vinschen wrote:
> > On Feb 5 09:42, Michael Haubenwallner wrote:
> >> On 2/4/19 3:25 PM, Corinna Vinschen wrote:
> >>> Are you going to test the patched branch?
> >>
> >> Sorry, was indeed unclear: Yes, of course!
> >>
On 2/2/19 9:29 PM, Corinna Vinschen wrote:
> Hi folks,
>
>
> I uploaded a new Cygwin test release 3.0.0-0.6
> Please test.
Ok... there's a regression since Cygwin 2.11 with bash co-processes:
$ echo abc > >(cat)
-bash: /dev/fd/62: No such file or directory
$
Expected behaviour (modified fo
I would like to locate an accurate changelog for the main Cygwin setup
executable that you run when you install Cygwin.
In the cygwin-announce mailing list, I can find some of them by searching for
"updated: setup", but not all of them come up and it's a very clunky way of
finding them.
In htt
1 [main] sh 19920 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.
Please report this problem to
the public mailing list cygwin@cygwin.com
CES@Med startscript revision_12 (2017-08-23)
66605 [main] sh 34256 C:\ecad\cygwin\bin\sh.exe: *** fatal error - fork:
can't reserve memory for
On Feb 5 13:02, Michael Haubenwallner wrote:
> On 2/2/19 9:29 PM, Corinna Vinschen wrote:
> > Hi folks,
> >
> >
> > I uploaded a new Cygwin test release 3.0.0-0.6
>
> > Please test.
>
> Ok... there's a regression since Cygwin 2.11 with bash co-processes:
>
> $ echo abc > >(cat)
> -bash: /de
On Feb 5 13:42, WST CI wrote:
> I would like to locate an accurate changelog for the main Cygwin setup
> executable that you run when you install Cygwin.
>
> In the cygwin-announce mailing list, I can find some of them by searching for
> "updated: setup", but not all of them come up and it's a
On Feb 5 14:37, Corinna Vinschen wrote:
> On Feb 5 13:02, Michael Haubenwallner wrote:
> > On 2/2/19 9:29 PM, Corinna Vinschen wrote:
> > > Hi folks,
> > >
> > >
> > > I uploaded a new Cygwin test release 3.0.0-0.6
> >
> > > Please test.
> >
> > Ok... there's a regression since Cygwin 2.11 wi
Hi folks,
I uploaded a new Cygwin test release 3.0.0-0.7
This release comes with a couple of new features and some interesting
bug fixes.
It also changes the output of uname(2) for newly built applications.
Applications built so far (that includes uname(1) from coreutils)
will still print the o
Greetings, Sierk, Dietmar!
> 1 [main] sh 19920 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
> pointer. Please report this problem to
> the public mailing list cygwin@cygwin.com
This indicates that you are using a very old Cygwin installation.
The issue leading to this warning was fixed over
L A Walsh writes:
> I can't get many cpan things to work with current perl.
Then these are unlikely to work with an older perl as well.
> Things like
> Term::Size::chars no longer works as it says chars isn't exported.
> but it is 'EXPORT_OK', and it used to work.
Import it into your namespace?
On 2/4/2019 4:18 PM, Wayne Davison wrote:
> On Mon, Feb 4, 2019 at 2:33 PM L A Walsh wrote:
>
>> Things like
>> Term::Size::chars no longer works as it says chars isn't exported.
>> but it is 'EXPORT_OK', and it used to work.
>>
>
> Remember that EXPORT_OK means that you can ask for it to b
On 2/1/2019 11:34 AM, Corinna Vinschen wrote:
>
> - Cygwin PIDs have been decoupled from Windows PID. Cygwin PIDs are
> now incrementally dealt in the range from 2 up to 65535, POSIX-like.
>
Posix like? Posix starts from '1' (usually for init), but
never heard it limited to 65535 ---
L
Greetings, L A Walsh!
> On 2/4/2019 4:18 PM, Wayne Davison wrote:
>> On Mon, Feb 4, 2019 at 2:33 PM L A Walsh wrote:
>>
>>> Things like
>>> Term::Size::chars no longer works as it says chars isn't exported.
>>> but it is 'EXPORT_OK', and it used to work.
>>>
>>
>> Remember that EXPORT_OK m
On 2/5/2019 4:25 PM, Andrey Repin wrote:
>
>> Yes...it worked for me up till the latest perl. I was surprised.
>
> STC ?
>
>> The man page documents usage as:
STC?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On 2/4/2019 3:09 PM, Peter A. Castro wrote:
> On Mon, Feb 04, 2019 at 02:32:35PM -0800, L A Walsh wrote:
>
> Greetings,
>
>
>> Can we have an older perl, say, perl-5.0.16? works for my stuff mostly
>> unchanged,
>>
>
> You sure you mean 5.0.16? That's really, really old! Maybe you mean
>
Greetings, Corinna Vinschen!
> Changes from 3.0.0-0.3:
> - Cygwin PIDs have been decoupled from Windows PID. Cygwin PIDs are
> now incrementally dealt in the range from 2 up to 65535, POSIX-like.
I don't quite get it.
What's the rationale? Why not just use system PID's?
--
With best regard
L A Walsh wrote:
On 2/5/2019 4:25 PM, Andrey Repin wrote:
Yes...it worked for me up till the latest perl. I was surprised.
STC ?
The man page documents usage as:
STC?
Please provide a Simple Test Case that shows exactly what you're trying and
exactly what happens that's inco
On Tue, Feb 5, 2019 at 4:23 PM L A Walsh wrote:
> Yes...it worked for me up till the latest perl. I was surprised.
Which latest perl is that? The 5.26.3 version I cited is the latest
version on cygwin, and it's working fine in all the simple tests I
tried (I tried scalar & array contexts for bo
21 matches
Mail list logo
