Bash: applet not found when starting gradle in MobaXterm
I am currently evaluating MobaXterm as a replacement for my current simple Cygwin installation on my Windows7 machine. One thing I'm stuck with is "gradle" works. On execution, I always get
bash: applet not found
Other people have had similar problems with commands on mobile devices and routers, for example:
- http://forum.xda-developers.com/showthread.php?t=169113
- http://comments.gmane.org/gmane.linux.busybox/35809
Not sure how this fits together, but the solutions most often refer to changing symlinks or copying around base shell executables. Does anyone know the gradle environment dependencies for forking workers / daemons and the like, or even provide details on the differences between the cygwin mobaXterm environment and the simple cygwin environment? Cygwin and MobaXterm use the same .bash_profile on my machine.
thanks for typing! Greetings
source to share
after kindly answer from MobaXterm support I found a solution. The problem stems from the fact that most of the basic MobaXterm commands (ls, cat, kill, etc.) are built on busybox, which returns the mentioned "bash: applet not found" error statement. (Can be played with the "busybox bash" command).
According to the gradle sources, gradle unixStartScript.txt has the following script preamble:
#!/usr/bin/env bash
I realized that in MobaXterm the env command is represented by a symbolic link exactly to busybox.exe. This seems to run / resolve before the actual bash command to run the gradle script. which calls
#!/usr/bin/busybox.exe bash
to perform environment preparation.
Long story short: To fix this issue, make /bin/env.exe a hard link to /bin/busybox.exe, or just copy the /bin/busybox.exe file and rename it to env.exe file in Windows Explorer to get gradle. finally launched in MobaXTerm!
Cheers Ben
source to share