Mintty font problem

Mintty font problem

[Paul Ausbeck]

Cygwin setup just updated some older packages while installing a 
requested new component and now mintty does not recognize fonts 
properly. I was previously using lucinda-console but now some default 
font is being used. When I try to change the mintty font through the 
Options... dialog, the following message appears when I press Select...:

"There are no fonts installed.
  Open the Fonts folder from the Control Panel to install fonts."

I've looked through the cygwin announce history and mintty v2.3.3 
advertises some font support changes. I'm still running Windows XP on 
this machine and I'm wondering if it could be that this new version of 
mintty has not been tested on XP?


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Mintty font problem

[Thomas Wolff]

Am 05.04.2016 um 01:54 schrieb Paul Ausbeck:
> Cygwin setup just updated some older packages while installing a 
> requested new component and now mintty does not recognize fonts 
> properly. I was previously using lucinda-console but now some default 
> font is being used. When I try to change the mintty font through the 
> Options... dialog, the following message appears when I press Select...:
>
> "There are no fonts installed.
>  Open the Fonts folder from the Control Panel to install fonts."
>
> I've looked through the cygwin announce history and mintty v2.3.3 
> advertises some font support changes. I'm still running Windows XP on 
> this machine and I'm wondering if it could be that this new version of 
> mintty has not been tested on XP?
It hasn't, in fact. I'll check that.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Mintty font selection problem on Windows XP

[Thomas Wolff]

Am 05.04.2016 um 02:40 schrieb Thomas Wolff:
> Am 05.04.2016 um 01:54 schrieb Paul Ausbeck:
>> Cygwin setup just updated some older packages while installing a 
>> requested new component and now mintty does not recognize fonts 
>> properly. I was previously using lucinda-console but now some default 
>> font is being used. When I try to change the mintty font through the 
>> Options... dialog, the following message appears when I press Select...:
>>
>> "There are no fonts installed.
>>  Open the Fonts folder from the Control Panel to install fonts."
>>
>> I've looked through the cygwin announce history and mintty v2.3.3 
>> advertises some font support changes. I'm still running Windows XP on 
>> this machine and I'm wondering if it could be that this new version 
>> of mintty has not been tested on XP?
> It hasn't, in fact. I'll check that.
This is fixed in the repository. Can you compile 
https://github.com/mintty/mintty/archive/master.zip and retry?
Thomas

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Mintty font problem

[john refling]

Paul Ausbeck <paula <at> soe.ucsc.edu> writes:

> 
> Cygwin setup just updated some older packages while installing a 
> requested new component and now mintty does not recognize fonts 
> properly. I was previously using lucinda-console but now some default 
> font is being used. When I try to change the mintty font through the 
> Options... dialog, the following message appears when I press Select...:
> 
> "There are no fonts installed.
>   Open the Fonts folder from the Control Panel to install fonts."
> 
> I've looked through the cygwin announce history and mintty v2.3.3 
> advertises some font support changes. I'm still running Windows XP on 
> this machine and I'm wondering if it could be that this new version of 
> mintty has not been tested on XP?
> 
> 


I'm having the same problem with a new XP install and cygwin, where it 
worked before.  Tried v 2.3.3, v2.3.5, and older archived v2.2.4 which 
certainly worked fine on previous XP machine.  Nothing works now, so not 
sure if it is mintty or XP setup.  Exact same XP install disk as previous.  
Different hardware.

One MS forum suggested to make sure that at least 1 printer was installed to 
make fonts visible in some applications.

Another suggested checking permissions on the font directory.

A cygwin forum suggested that there might be no monospace fonts installed 
and that mintty needs monospaced fonts only (make sense).

I've tried all the above, and no luck.

Something else suggested using tweakui to rebuild certain system folders.

I'll try that next.

John Refling


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Postinstall script errors on cygwin x86 install

[Tatsuro MATSUOKA]

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
<snip>
Package: 0/Perpetual
 0p_000_autorebase.dash exit code 2
 0p_update-info-dir.dash exit code 2
Package: _/base-cygwin
 000-cygwin-post-install.sh exit code 254
Package: _/coreutils
 coreutils.sh exit code 127
Package: _/bash
 bash.sh exit code 254
Package: _/base-files
 base-files-mketc.sh exit code 254
 base-files-profile.sh exit code 254
Package: _/ca-certificates
 ca-certificates.sh exit code 254
Package: _/lynx
 lynx.sh exit code 254
Package: _/man-db
 man-db.sh exit code 254
What were happened?
As expecteded from the errors above installed Cywin were buggy 
and colud not be usable

Tatsuro

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Postinstall script errors on cygwin x86 install

[Ken Brown]

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
> <snip>
> Package: 0/Perpetual
>   0p_000_autorebase.dash exit code 2
>   0p_update-info-dir.dash exit code 2
> Package: _/base-cygwin
>   000-cygwin-post-install.sh exit code 254
> Package: _/coreutils
>   coreutils.sh exit code 127
> Package: _/bash
>   bash.sh exit code 254
> Package: _/base-files
>   base-files-mketc.sh exit code 254
>   base-files-profile.sh exit code 254
> Package: _/ca-certificates
>   ca-certificates.sh exit code 254
> Package: _/lynx
>   lynx.sh exit code 254
> Package: _/man-db
>   man-db.sh exit code 254
> What were happened?
> As expecteded from the errors above installed Cywin were buggy
> and colud not be usable

Take a look at var/log/setup.log.full and see if it gives any clues as 
to why the postinstall scripts are failing.  You could also try running 
them manually.

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Postinstall script errors on cygwin x86 install

[Tatsuro MATSUOKA]

> 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 32bit).
>>  Only default packages were installed.
>>  In the final panel, I saw  the following:
>>  Postinstall script errors
>>  <snip>
>>  Package: 0/Perpetual
>>    0p_000_autorebase.dash exit code 2
>>    0p_update-info-dir.dash exit code 2
>>  Package: _/base-cygwin
>>    000-cygwin-post-install.sh exit code 254
>>  Package: _/coreutils
>>    coreutils.sh exit code 127
>>  Package: _/bash
>>    bash.sh exit code 254
>>  Package: _/base-files
>>    base-files-mketc.sh exit code 254
>>    base-files-profile.sh exit code 254
>>  Package: _/ca-certificates
>>    ca-certificates.sh exit code 254
>>  Package: _/lynx
>>    lynx.sh exit code 254
>>  Package: _/man-db
>>    man-db.sh exit code 254
>>  What were happened?
>>  As expecteded from the errors above installed Cywin were buggy
>>  and colud not be usable
> 
> Take a look at var/log/setup.log.full and see if it gives any clues as to why 
> the postinstall scripts are failing.  You could also try running them manually.
> 
Thanks!
I will try when I will be back to my home.
Tatsuro


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Postinstall script errors on cygwin x86 install

[Achim Gratz]

>
[Please don't reply to some totally unrelated message when you're starting a
new thread.]

Tatsuro MATSUOKA <tmacchant2 <at> 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 were
specifically.  What is the user you are running setup under?


Regards,
Achim.

Re: Postinstall script errors on cygwin x86 install

[Tatsuro MATSUOKA]

> From: Achim Gratz
> To: cygwin
> Cc: 
> Date: 2016/4/11, Mon 15:37
> Subject: Re: Postinstall script errors on cygwin x86 install
           
> [Please don't reply to some totally unrelated message when you're 
> starting a
> new thread.]

> [Please don't reply to some totally unrelated message when you're 
> starting a
> new thread.]
Sorry I will take care for that.
> Please check /var/log/setup.log.full for what those errors were
> specifically.  What is the user you are running setup under?
> 
Today number of errors is reduced.
*******************************************
Package: 0/Perpetual
 0p_000_autorebase.dash exit code 2
 0p_update-info-dir.dash exit code 2
Package: _/Unknown package
 000-cygwin-post-install.sh exit code 254
 base-files-mketc.sh exit code 1
 base-files-profile.sh exit code 254
 bash.sh exit code 254
 ca-certificates.sh exit code 254
 coreutils.sh exit code 254
 lynx.sh exit code 254
 man-db.sh exit code 127
***************************************
/var/log/setup.log.full
is uploaded below (zipped)
http://www.geocities.jp/tmacchant2/setup.log.full.20160412.zip
Typical message;

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 *should*Search for cygwin1.dll using the Windows Start->Find/Search facilityThis problem is probably due to using incompatible versions of the cygwin DLL.      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.
Tatsuro
Tatsuro


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Postinstall script errors on cygwin x86 install

[Achim Gratz]

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 scanner are you using?  Can you exempt the
Cygwin installation from its actions?

But please try to install Cygwin into some other directory
that is not directly in the root of your drive (something like
C:\Freeware\Cygwin).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Postinstall script errors on cygwin x86 install

[Ken Brown]

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 *should*Search for cygwin1.dll using the Windows Start->Find/Search facilityThis problem is probably due to using incompatible versions of the cygwin DLL.      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.

cygcheck output as requested at http://cygwin.com/problems.html might 
help diagnose the problem:

"Run cygcheck -s -v -r > cygcheck.out and include that file *as an 
attachment* in your report. Please do not compress or otherwise encode 
the output. Just attach it as a straight text file so that it can be 
easily viewed."

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Warning: Mismatch between the program and library build versions detted. (WxWidgets)

[Tatsuro MATSUOKA]

Hello
I have met the following waring gnuplot with wxt terminal
Terminal type set to 'wxt'
gnuplot> plot sin(x)
10:33:39: Warning: Mismatch between the program and library build versions detted.
The library used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatie with 2.8),
and your program used 3.0 (wchar_t,compiler with C++ ABI 1002,wx containers,coatible with 2.8).
I do not have enough knowldge of difference between C++ ABI 1009 and C++ ABI 1002.
Any suggestions?
# For the program execution, I do not have troubles from the warining.
Tatsuro


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Warning: Mismatch between the program and library build versions detted. (WxWidgets)

[Marco Atzeri]

On 12/04/2016 03:41, Tatsuro MATSUOKA wrote:
> Hello
> I have met the following waring gnuplot with wxt terminal
> Terminal type set to 'wxt'
> gnuplot> plot sin(x)
> 10:33:39: Warning: Mismatch between the program and library build versions detted.
> The library used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatie with 2.8),
> and your program used 3.0 (wchar_t,compiler with C++ ABI 1002,wx containers,coatible with 2.8).
> I do not have enough knowldge of difference between C++ ABI 1009 and C++ ABI 1002.
> Any suggestions?
> # For the program execution, I do not have troubles from the warining.
> Tatsuro
>
>

Tatsuro,
can you please stop to reply to different unrelated threads
instead of starting a new one ?

It mess up the archives
https://cygwin.com/ml/cygwin/2016-04/threads.html

and mail reading.

Regards
Marco


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Warning: Mismatch between the program and library build versions detted. (WxWidgets)

[Tatsuro MATSUOKA]

> From: Tatsuro MATSUOKA
>To: cygwin
> Cc: 
> Date: 2016/4/12, Tue 10:41
> Subject: Warning: Mismatch between the program and library build versions detted. (WxWidgets)
> 
> Hello
> I have met the following waring gnuplot with wxt terminal
> Terminal type set to 'wxt'
> gnuplot> plot sin(x)
> 10:33:39: Warning: Mismatch between the program and library build versions 
> detted.
> The library used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatie 
> with 2.8),
> and your program used 3.0 (wchar_t,compiler with C++ ABI 1002,wx 
> containers,coatible with 2.8).
> I do not have enough knowldge of difference between C++ ABI 1009 and C++ ABI 
> 1002.
> Any suggestions?
> # For the program execution, I do not have troubles from the warining.
> Tatsuro

I have forgetton to execute setup_x86-64 before gnuplot buliding.
Setup seems to upgrade the cygwin and gcc-5.3.0 (to 5.3.0-3).
After setup, the warning was disappeared.
Tatsuro       

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

multiple definition of `atan2l' on the current Cygwin

[Tatsuro MATSUOKA]

I have updated Cygwin_x86 and Cygwin_x86-64 today.
In building the gnuplot I have met the error of "multiple definition of `atan2l'".
/usr/lib/gcc/x86_64-pc-cygwin/5.3.0/libstdc++.dll.a(d005836.o):(.text+0x0): multiple definition of `atan2l'
/usr/lib/../lib/libm.a(t-d000195.o):fake:(.text+0x0): first defined here
collect2: error: ld returned 1 exit status
Makefile:777: recipe for target 'gnuplot.exe' failed
This did not occur yesterday.
Perhaps the latest change gcc-5.3.0 give this results.
At the moment a workaroud is :
LDFLAGS='-Wl,--allow-multiple-definition' \
at configure.
Tatsuro


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: multiple definition of `atan2l' on the current Cygwin

[Warren Young]

On Apr 11, 2016, at 9:06 PM, Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp> wrote:
> 
> In building the gnuplot

Why aren’t you using the gnuplot package in the Cygwin package repository?

> I have met the error of "multiple definition of `atan2l’".

This is doubtless because that function was just added to Cygwin in 2.5.0.

Perhaps gnuplot is providing its own copy due to a naive platform test?  Have you tried a clean reconfigure and rebuild?
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: multiple definition of `atan2l' on the current Cygwin

[Tatsuro MATSUOKA]

Please inore this post.
I have made a mistake to post under the different thread.

       
       
> From: Tatsuro MATSUOKA 
> To: cygwin
> Cc: 
> Date: 2016/4/12, Tue 12:06
> Subject: multiple definition of `atan2l' on the current Cygwin
> 
> I have updated Cygwin_x86 and Cygwin_x86-64 today.
> In building the gnuplot I have met the error of "multiple definition of 
> `atan2l'".
> /usr/lib/gcc/x86_64-pc-cygwin/5.3.0/libstdc++.dll.a(d005836.o):(.text+0x0): 
> multiple definition of `atan2l'
> /usr/lib/../lib/libm.a(t-d000195.o):fake:(.text+0x0): first defined here
> collect2: error: ld returned 1 exit status
> Makefile:777: recipe for target 'gnuplot.exe' failed
> This did not occur yesterday.
> Perhaps the latest change gcc-5.3.0 give this results.
> At the moment a workaroud is :
> LDFLAGS='-Wl,--allow-multiple-definition' \
> at configure.
> Tatsuro
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Postinstall script errors on cygwin x86 install

[Tatsuro MATSUOKA]

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-font-problem-td125968.html#a126124
http://cygwin.1069669.n5.nabble.com/Mintty-font-problem-td125968.html#a126127
http://cygwin.1069669.n5.nabble.com/Mintty-font-problem-td125968.html#a126152
http://cygwin.1069669.n5.nabble.com/Mintty-font-problem-td125968.html#a126154
http://cygwin.1069669.n5.nabble.com/Mintty-font-problem-td125968.html#a126155
My problem is solved but I do not do detailed action.
Only things are done.
 1. Windows Update
 2. Reinstall Cygwin
Perhaps 1 or 2 and both is or are related to the solving issue.
Anyway, thanks for replies.
Tatsuro


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Postinstall script errors on cygwin x86 install

[Tatsuro MATSUOKA]

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.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Mintty font problem

[Thomas Wolff]

Am 10.04.2016 um 21:35 schrieb john refling:
> Paul Ausbeck <paula <at> soe.ucsc.edu> writes:
>
>> "There are no fonts installed.
>>    Open the Fonts folder from the Control Panel to install fonts."
>> ... on XP?
> I'm having the same problem with a new XP install and cygwin, where it
> worked before.  Tried v 2.3.3, v2.3.5, and older archived v2.2.4 which
> certainly worked fine on previous XP machine.  Nothing works now, so not
> sure if it is mintty or XP setup.  Exact same XP install disk as previous.
> Different hardware.
>
> One MS forum suggested to make sure that at least 1 printer was installed to
> make fonts visible in some applications.
>
> Another suggested checking permissions on the font directory.
>
> A cygwin forum suggested that there might be no monospace fonts installed
> and that mintty needs monospaced fonts only (make sense).
>
> I've tried all the above, and no luck.
>
> Something else suggested using tweakui to rebuild certain system folders.
>
> I'll try that next.
Don't try so much. As I had responded before, this has been fixed in the 
repository.
Thomas

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

RE: Postinstall script errors on cygwin x86 install

[Brent]

Hello,

Tatsuro MATSUOKA started this thread
    https://cygwin.com/ml/cygwin/2016-04/msg00193.html
back on Mon, 11 Apr 2016 05:18:30 +0900 (JST), which I stumbled across just now from a web search.

I recently encountered a very similar problem, and I think that I have a simple solution, so I wanted to followup.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

First some background:

--I was forced at work to downgrade from Win 7 to Win 10 spyware as a service a few weeks ago

--at the time of that downgrade, I had some problems with cygwin, so I did a clean install of 32 bit cygwin

--I vaguely recall a few post installation warnings at that time, but I did not note them; furthermore, cygwin seemed to subsequently work

--this morning, however, some R code failed that worked just 2 days ago (and was not changed in the interim...)
    --actually, it was the R C++ compiler of some critical methods that was failing, not R per se
    --the warning message was:
        Warning: running command 'C:/PROGRA~1/RRO/R-31~1.2/bin/x64/R CMD SHLIB file9d81bb03ccf.cpp 2> file9d81bb03ccf.cpp.err.txt' had status 1
              0 [main] make (1584) c:\Rtools\bin\make.exe: *** fatal error - cygheap base mismatch detected - 0xFCF408/0xDDF408.
        This problem is probably due to using incompatible versions of the cygwin DLL.
        Search for cygwin1.dll using the Windows Start->Find/Search facility
        and delete all but the most recent version.  The most recent version *should*
        reside in x:\cygwin\bin, where 'x' is the drive on which you have
        installed the cygwin distribution.  Rebooting is also suggested if you
        are unable to find another cygwin DLL.
              0 [main] make 2544 fork: child -1 - forked process 1584 died unexpectedly, retry 0, exit code 0xC0000142, errno 11

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

After that error, I tried another clean reinstall of 32 bit cygwin.  My steps were simply:
    1) I deleted these entire directory trees:
        C:\cygwin
        <path to setup-x86.exe>\http%3a%2f%2fcygwin.mirror.constant.com%2f
    2) I reran setup-x86.exe

At the end of this reinstall, setup-x86.exe popped up a dialog that listed these post install errors:
    Package: 0/Perpetual
        0p_000_autorebase.dash exit code 2
        0p_update-info-dir.dash exit code 2
    Package: _/base-cygwin
        000-cygwin-post-install.sh exit code 254
    Package: _/coreutils
        coreutils.sh exit code 254
    Package: _/bash
        bash.sh exit code 254
    Package: _/base-files
        base-files-mketc.sh exit code 254
        base-files-profile.sh exit code 254
    Package: _/ca-certificates
        ca-certificates.sh exit code 254
    Package: _/lynx
        lynx.sh exit code 254
    Package: _/man-db
        man-db.sh exit code 254
    Package: _/mintty
        mintty.sh exit code 254

That list is very similar to Tatsuro's.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

To make a long story short, the cure for my post install errors was to do another clean install that included CLEANING THE REGISTRY AS WELL.

In particular, these are the exact reinstall steps that worked for me:
    1) delete these entire directory trees:
        C:\cygwin
        <path to setup-x86.exe>\http%3a%2f%2fcygwin.mirror.constant.com%2f
    2) run regedit and ENTIRELY delete BOTH of these registry trees:
        HKEY_LOCAL_MACHINE\Software\Cygwin
        HKEY_CURRENT_USER\Software\Cygwin
    3) restart your computer
    4) rerun setup-x86.exe


The above is an abbreviated version of the steps described in    https://cygwin.com/faq/faq.html#faq.setup.uninstall-all
(I did not need to do the other steps, since my installation had nothing fancy like cygwin services running.)

When I did the above, setup-x86.exe ran to completion with no errors whatsoever.  Furthermore my cygwin install seems to work fine (as does the R code failed this morning).

Hope this helps someone else in the future.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Postinstall script errors on cygwin x86 install

[Achim Gratz]

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...)
>     --actually, it was the R C++ compiler of some critical methods that was failing, not R per se
>     --the warning message was:
>         Warning: running command 'C:/PROGRA~1/RRO/R-31~1.2/bin/x64/R CMD SHLIB file9d81bb03ccf.cpp 2> file9d81bb03ccf.cpp.err.txt' had status 1
>               0 [main] make (1584) c:\Rtools\bin\make.exe: *** fatal error - cygheap base mismatch detected - 0xFCF408/0xDDF408.
>         This problem is probably due to using incompatible versions of the cygwin DLL.
>         Search for cygwin1.dll using the Windows Start->Find/Search facility
>         and delete all but the most recent version.  The most recent version *should*
>         reside in x:\cygwin\bin, where 'x' is the drive on which you have
>         installed the cygwin distribution.  Rebooting is also suggested if you
>         are unable to find another cygwin DLL.
>               0 [main] make 2544 fork: child -1 - forked process 1584 died unexpectedly, retry 0, exit code 0xC0000142, errno 11

You are obviously not using the R that comes with Cygwin and in addition
some extra stuff that lives in C:\Rtools.  And apparently, the latter
comes with their own Cygwin-based tools and gets delivered with their
own cygwin1.dll.  Now, If you had read the error message you might have
found where that second cygwin1.dll lives (and likely still lives).  The
next time you'll call the tools in whatever order to make that other
(older) cygwin1.dll load first or have the programs in Rtools try to use
the newer cygwin1.dll you will have that very same problem again.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Postinstall script errors on cygwin x86 install

[Brent]

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 fact, quickly skimming cygwin's setup-x86.exe list of available packages, I do not see an R in there.


>and in addition some extra stuff that lives in C:\Rtools.
>And apparently, the latter comes with their own Cygwin-based tools
>and gets delivered with their own cygwin1.dll.

I did not install any extra cygwin tools when I installed Rtools, as I already had a full cygwin installation.

In particular, the Rtools check box option to install the cygwin DLLs was left unchecked.


>Now, If you had read the error message

No, I read that message, and followed its instructions.


>you might have found where that second cygwin1.dll lives (and likely still lives).

I should have mentioned in my original email that when I searched for cygwin1.dll, I found but once instance, the expected one in C:\cygwin\bin.


>The next time you'll call the tools in whatever order to make that other
>(older) cygwin1.dll load first or have the programs in Rtools try to use
>the newer cygwin1.dll you will have that very same problem again.

I followed the recommended advice from Duncan Murdoch: I installed only cygwin 32 bit, and put Rttols before cygwin in my PATH system env var.

See
    http://r.789695.n4.nabble.com/RTools-and-previous-Cygwin-installation-conflict-td4686674.html

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Postinstall script errors on cygwin x86 install

[Achim Gratz]

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 there.

https://cygwin.com/packages/x86/R


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple