Allen Hewes via Cygwin writes:
> I think the recent man* package update has an issue in the postinstall script:
Yes, the script got broken when it was generated for packaging. It's
hopefully fixed now.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wal
Brent writes:
> I am not sure what you mean by "the R that comes with Cygwin". I do
> not think that cygwin comes with its own version R installed by
> default, like it default installs perl. In fact, quickly skimming
> cygwin's setup-x86.exe list of available packages, I do not see an R
> in the
Achim wrote:
>You are obviously not using the R that comes with Cygwin
My R is the Windows version of the program.
I am not sure what you mean by "the R that comes with Cygwin". I do not think
that cygwin comes with its own version R installed by default, like it default
installs perl. In f
Brent writes:
> I recently encountered a very similar problem, and I think that I have
> a simple solution, so I wanted to followup.
I don't think you've solved your problem.
> --this morning, however, some R code failed that worked just 2 days ago (and
> was not changed in the interim...)
>
Sorry I have again misoperate the post.
Anyway my problem is solved and I will not post for this topic any longer.
Tatsuro
--
View this message in context:
http://cygwin.1069669.n5.nabble.com/Mintty-font-problem-tp125968p126351.html
Sent from the Cygwin list mailing list archive at Nabble.com
Sorry for I have posted to the unrelated thread.
Here the links to the previous post and replies.
http://cygwin.1069669.n5.nabble.com/Mintty-font-problem-td125968.html#a126120
http://cygwin.1069669.n5.nabble.com/Mintty-font-problem-td125968.html#a126121
http://cygwin.1069669.n5.nabble.com/Mintty-fo
On 4/11/2016 4:42 PM, Tatsuro MATSUOKA wrote:
3are unable to find another cygwin DLL.installed the cygwin distribution.
Rebooting is also suggested if youreside in x:\cygwin\bin, where 'x' is the drive
on which you haveand delete all but the most recent version. The most recent
version *shou
Tatsuro MATSUOKA writes:
> 6 [main] bash (7088) c:\cygwin\bin\bash.exe: *** fatal error
> - cygheap base mismatch detected - 0xC0F400/0xBDF400.
> However, I have only one x\cygwin\bin and x is C.
Well, since that cygheap base address is changing, I guess this comes
down to BLODA. What malware sca
On 4/11/2016 11:49 AM, Kenneth Lobb wrote:
Getting setup-x86_64.exe postinstall script errors, starting with
/etc/postinstall/ca-certificates.sh.
Script just hangs.
Is this the only postinstall script that gives you problems? What
happens if you rename it to ca-certificates.sh.done so that s
>
[Please don't reply to some totally unrelated message when you're starting a
new thread.]
Tatsuro MATSUOKA yahoo.co.jp> writes:
> I have tried to install Cygwin x86 in my netbook (win 10 32bit).
> Only default packages were installed.
Please check /var/log/setup.log.full for what those errors
> From: Ken Brown
> To: cygwin
> Cc:
> Date: 2016/4/11, Mon 07:12
> Subject: Re: Postinstall script errors on cygwin x86 install
>
> On 4/10/2016 4:18 PM, Tatsuro MATSUOKA wrote:
>> Hello
>> I have tried to install Cygwin x86 in my netbook (win 10
On 4/10/2016 4:18 PM, Tatsuro MATSUOKA wrote:
Hello
I have tried to install Cygwin x86 in my netbook (win 10 32bit).
Only default packages were installed.
In the final panel, I saw the following:
Postinstall script errors
Package: 0/Perpetual
0p_000_autorebase.dash exit code 2
0p_update-inf
"Dr. Volker Zell" writes:
>> Christian Kellermann writes:
>
> > Hi Volker,
>
> Hi
>
> > Thanks for your feedback! I do need further information (see below).
>
> > vz...@volkerzell.de (Dr. Volker Zell) writes:
> >> For both architectures chicken postinstall scripts fail.
>
> Christian Kellermann writes:
> Hi Volker,
Hi
> Thanks for your feedback! I do need further information (see below).
> vz...@volkerzell.de (Dr. Volker Zell) writes:
>> For both architectures chicken postinstall scripts fail.
>>
>> 32-bit:
>> ===
>>
Hi Volker,
Thanks for your feedback! I do need further information (see below).
vz...@volkerzell.de (Dr. Volker Zell) writes:
> For both architectures chicken postinstall scripts fail.
>
> 32-bit:
> ===
>
> 2015/02/08 14:46:54 running: C:\cygwin\bin\bash.exe --norc --noprofile
> "/etc/postin
vz...@volkerzell.de (Dr. Volker Zell) writes:
> Hi
>
> For both architectures chicken postinstall scripts fail.
>
> 32-bit:
> ===
>
> 2015/02/08 14:46:54 running: C:\cygwin\bin\bash.exe --norc --noprofile
> "/etc/postinstall/chicken.sh"
>
> Error: (require) cannot load extension: setup-downlo
Apologies for the spam...forgot to reattach the results of the cygcheck when
resending.
-Original Message-
From: Shaun Gosse
Sent: Tuesday, February 25, 2014 3:07 PM
To: 'cygwin AT Cygwin DOT com'
Subject: RE: postinstall script errors (-1073741819 / STATUS_ACCESS_VIOLATION)
My previous send didn't go through apparently; needs address obfuscation, now
done.
-Original Message-
From: Shaun Gosse
Sent: Tuesday, February 25, 2014 2:00 PM
To: 'cygwin AT cygwin DOT com'
Subject: RE: postinstall script errors (-1073741819 / STATUS_ACCESS_VIOLATI
On Tue, Feb 25, 2014 at 06:25:18PM +, Shaun Gosse wrote:
>Oh, and http://cygwin.com/problems.html suggested running cygcheck, but it's
>not found:
>-sh-4.1$ cygcheck
>-sh: cygcheck: command not found
It's there if you have a shell prompt. You likely just have to
specify the complete path.
Y
On 5/31/2013 2:29 AM, paul.nicker...@desknetinc.com wrote:
From: "Larry Hall (Cygwin)"
To: cygwin at cygwin dot com,
Date: 05/29/2013 03:51 PM
Subject: Re: Postinstall Script Errors With Exit Code 128
Sent by: cygwin-owner at cygwin dot com
On 5/29/2013 3:18 PM, Paul.Nickerson at
> From: "Larry Hall (Cygwin)"
> To: cygwin at cygwin dot com,
> Date: 05/29/2013 03:51 PM
> Subject: Re: Postinstall Script Errors With Exit Code 128
> Sent by: cygwin-owner at cygwin dot com
>
> On 5/29/2013 3:18 PM, Paul.Nickerson at desknetinc dot com wrote:
&g
On 5/29/2013 3:18 PM, paul.nicker...@desknetinc.com wrote:
cygwin-owner at cygwin dot com wrote on 05/29/2013 12:28:30 PM:
From: "Larry Hall (Cygwin)"
To: cygwin at cygwin dot com,
Date: 05/29/2013 12:29 PM
Subject: Re: Postinstall Script Errors With Exit Code 128
Sent by: cygwi
cygwin-owner at cygwin dot com wrote on 05/29/2013 12:28:30 PM:
> From: "Larry Hall (Cygwin)"
> To: cygwin at cygwin dot com,
> Date: 05/29/2013 12:29 PM
> Subject: Re: Postinstall Script Errors With Exit Code 128
> Sent by: cygwin-owner at cygwin dot com
&
On 5/29/2013 12:04 PM, Paul.Nickerson wrote:
I tried each of your suggestions, and they did not help it install. I also
tried cygcheck again, and it did not run any better. Any other ideas? I'm
at a loss right now.
This list has seen the occasional question about AWS and Cygwin in the past
b
>> Paul.Nickerson at desknetinc dot com wrote on 05/28/2013 03:43:11 PM:
>> From: Paul.Nickerson at desknetinc dot com
>> To: cygwin at cygwin dot com,
>> Date: 05/28/2013 03:43 PM
>> Subject: Postinstall Script Errors With Exit Code 128
>>
>> I am attempting to install Cygwin, and am getting er
On 5/28/2013 3:43 PM, paul.nicker...@desknetinc.com wrote:
I am attempting to install Cygwin, and am getting errors near the end of
the process. I am using version 2.774 of setup.exe on Microsoft Windows
Server 2003 R2 Datacenter x64 Edition Service Pack 2 and the default
Cygwin packages. This is
Hello,
It works now, I was able to install gcc 4.3.4.
Thanks!
Tilman
On Fri, 13 Aug 2010 11:48:04 +0200, Corinna Vinschen wrote:
>On Aug 12 19:50, Tilman Hausherr wrote:
>> On Thu, 12 Aug 2010 11:59:30 +0200, Corinna Vinschen wrote:
>>
>> >That's probably a fault in the postinstall scripts.
On Aug 12 19:50, Tilman Hausherr wrote:
> On Thu, 12 Aug 2010 11:59:30 +0200, Corinna Vinschen wrote:
>
> >That's probably a fault in the postinstall scripts. It would be nice if
> >you could provide more details about what fails exactly in the script,
> >or better, what in the script has a non-0
On Thu, 12 Aug 2010 11:59:30 +0200, Corinna Vinschen wrote:
>That's probably a fault in the postinstall scripts. It would be nice if
>you could provide more details about what fails exactly in the script,
>or better, what in the script has a non-0 exit code. That would help us
>lazy maintainers
Am 12.08.2010 17:15, schrieb Corinna Vinschen:
> On Aug 12 17:04, Matthias Andree wrote:
>> Am 12.08.2010 16:54, schrieb Corinna Vinschen:
>> > On Aug 12 16:52, Matthias Andree wrote:
>> >> Am 12.08.2010 16:40, schrieb Corinna Vinschen:
>> >> > I misinterpreted the `chgrp --silent'. I thought it w
On Aug 12 17:04, Matthias Andree wrote:
> Am 12.08.2010 16:54, schrieb Corinna Vinschen:
> > On Aug 12 16:52, Matthias Andree wrote:
> >> Am 12.08.2010 16:40, schrieb Corinna Vinschen:
> >> > I misinterpreted the `chgrp --silent'. I thought it would result
> >> > in an exit code of 0 from chgrp, b
Am 12.08.2010 16:54, schrieb Corinna Vinschen:
> On Aug 12 16:52, Matthias Andree wrote:
>> Am 12.08.2010 16:40, schrieb Corinna Vinschen:
>> > On Aug 12 16:10, Matthias Andree wrote:
>> >> Am 12.08.2010 15:37, schrieb Jeremy Ramer:
>> >> > I verified that $created_passwd and $created_group were bo
On Aug 12 16:52, Matthias Andree wrote:
> Am 12.08.2010 16:40, schrieb Corinna Vinschen:
> > On Aug 12 16:10, Matthias Andree wrote:
> >> Am 12.08.2010 15:37, schrieb Jeremy Ramer:
> >> > I verified that $created_passwd and $created_group were both no so
> >> > both conditionals will fail. But beca
Am 12.08.2010 16:40, schrieb Corinna Vinschen:
> On Aug 12 16:10, Matthias Andree wrote:
>> Am 12.08.2010 15:37, schrieb Jeremy Ramer:
>> > I verified that $created_passwd and $created_group were both no so
>> > both conditionals will fail. But because the last conditional is the
>> > last thing ru
On Aug 12 16:10, Matthias Andree wrote:
> Am 12.08.2010 15:37, schrieb Jeremy Ramer:
> > I verified that $created_passwd and $created_group were both no so
> > both conditionals will fail. But because the last conditional is the
> > last thing run, the script returns 1. Adding an exit 0 to the scr
Am 12.08.2010 15:37, schrieb Jeremy Ramer:
> On Thu, Aug 12, 2010 at 3:59 AM, Corinna Vinschen
> wrote:
>> On Aug 11 09:18, Jeremy Ramer wrote:
>>> I recently upgraded from cygwin 1.5 to 1.7. At the end of the install
>>> there were errors with some of the postinstall scripts. From the
>>> setup.
On Aug 12 07:37, Jeremy Ramer wrote:
> On Thu, Aug 12, 2010 at 3:59 AM, Corinna Vinschen
> wrote:
> > On Aug 11 09:18, Jeremy Ramer wrote:
> >> I recently upgraded from cygwin 1.5 to 1.7. At the end of the install
> >> there were errors with some of the postinstall scripts. From the
> >> setup.fu
On Thu, Aug 12, 2010 at 3:59 AM, Corinna Vinschen
wrote:
> On Aug 11 09:18, Jeremy Ramer wrote:
>> I recently upgraded from cygwin 1.5 to 1.7. At the end of the install
>> there were errors with some of the postinstall scripts. From the
>> setup.full.log:
>>
>> 2010/08/11 08:39:53 running: C:\cyg
On Aug 11 09:18, Jeremy Ramer wrote:
> I recently upgraded from cygwin 1.5 to 1.7. At the end of the install
> there were errors with some of the postinstall scripts. From the
> setup.full.log:
>
> 2010/08/11 08:39:53 running: C:\cygwin\bin\bash.exe --norc --noprofile
> /etc/postinstall/bash.sh
>
39 matches
Mail list logo
