I checked the problem on three different PCs (Win10, Win8.1 and Win8.1 (all 64bit)), and same results were got. Does this problem occur only for me? If so, it is assent that no questions about it cannot be found on the web.
Although it may not be public benefit, If you have any idea to investigate the cause of the problem, could you please tell me? Because of this problem, some configure scripts does not work.
Regards,
Shusaku KIMURA.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I checked t.sh on Windows8.1 32bit and MSYS2 32bit, and correct result could be got.
And I tried re-installing MSYS2 64bit on Windows10 64bit using msys2-x86_64-20150916.exe, and correct result could be got. But, after executing update-core, the problem began to occur.
Regards,
Shusaku KIMURA.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found MacType causes the problem. After uninstalling MacType, t.sh began to work correctly. MacType is listed in BLODA.
I did not know BLODA and I had not searched the topics about this problem in association with Cygwin, although I should know MSYS2 is derived from Cygwin. I agree ticket #254 seems to be similar problem, but I could not find it too. I am ashamed of myself.
I tried to execute strace for reference, but SEGV occured and nothing to be got. After uninstalling MacType, strace also works well.
Thanks again.
Regards,
Shusaku KIMURA.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
It seems that the command substitution does not work on sh (=bash). I wrote the following shell script and save as t.sh.
When executed it, the following result was got. But correct result is 'xFOO'.
I confirmed the issue on Windows 10 64bit and Windows 8.1 64bit. To install MSYS2, 64bit installer was used.
I'm sorry if this is known issue, but I could not find the topics about it. Please tell me any work arrounds.
Regards,
Shusaku KIMURA.
Last edit: Shusaku KIMURA 2016-02-20
I'm not able to confirm on msys64 on Windows 10.
Does
bash t.sh
also not work for you? If yes, can you paste the output ofbash -xv a.sh
?Thank you for the reply.
Yes. Same result was got.
Using zsh, correct result were got.
I checked the problem on three different PCs (Win10, Win8.1 and Win8.1 (all 64bit)), and same results were got. Does this problem occur only for me? If so, it is assent that no questions about it cannot be found on the web.
Although it may not be public benefit, If you have any idea to investigate the cause of the problem, could you please tell me? Because of this problem, some configure scripts does not work.
Regards,
Shusaku KIMURA.
I checked t.sh on Windows8.1 32bit and MSYS2 32bit, and correct result could be got.
And I tried re-installing MSYS2 64bit on Windows10 64bit using msys2-x86_64-20150916.exe, and correct result could be got. But, after executing update-core, the problem began to occur.
Regards,
Shusaku KIMURA.
I'm running the latest 64-bit MSYS2 and have tested this on Windows Server 2012 R2 and Windows 10.
It looks like your bash (or sh) has problems forking.
strace bash -xv t.sh
and paste it somewhere (probably not directly into this discussion, but rather onto pastebin or similar).Seems related to http://sourceforge.net/p/msys2/tickets/245/.
Thank you very much for kindly reply.
I found MacType causes the problem. After uninstalling MacType, t.sh began to work correctly. MacType is listed in BLODA.
I did not know BLODA and I had not searched the topics about this problem in association with Cygwin, although I should know MSYS2 is derived from Cygwin. I agree ticket #254 seems to be similar problem, but I could not find it too. I am ashamed of myself.
I tried to execute strace for reference, but SEGV occured and nothing to be got. After uninstalling MacType, strace also works well.
Thanks again.
Regards,
Shusaku KIMURA.
I'm glad to hear the issue got resolved.