The error in the title is what appears on my Bash on Windows 10 when I try using make I did read many tips and none seems to work when I tried mingw-get install msys-make.
I got the error message that it's already installed on my pc. Now I dunno what to do, even when the package is installed, bash: make: command not found is still there. On the other hand, I did add almost all the possible path to PATH, and sometimes the error change to
/mingw64/make-4.3/tests/scripts/variables/make: line 3: =: command not found
/mingw64/make-4.3/tests/scripts/variables/make: line 5: =: command not found
/mingw64/make-4.3/tests/scripts/variables/make: line 7: syntax error near unexpected token `q!'
/mingw64/make-4.3/tests/scripts/variables/make: line 7: `run_make_test(q!'
You should add its path to the $PATH variable and reboot Windows. OS updates viriables after reboot.
Related
Being grateful for some people on the Internet who helped me at stackexchange(and stackoverflow,sourceforge.....), I finally got to the step "make" when I want to build the cmu sphinxbase from source.
Here are the most recent commands I execute under sphinxbase directory (Windows cygwin):
- $./autogen.sh
- $./configure
- $make
I got this message:
/usr/bin/bash: -c: line 20: syntax error near unexpected token `('
/usr/bin/bash: -c: line 20: ` (CDPATH="${ZSH_VERSION+.}:" && cd
$subdir && C:/Program Files (x86)/GnuWin32/bin/make $local_target) \'
make: *** [check-recursive] Error 1
After some information searching, I guess that this is due to the $PATH variable issue.
I am not pretty sure if the error raises because of the behavior of cygwin or maybe of the GNU-make(for win32).
If the system searches for some string containing usr/bin/, it might get the wrong route.
Maybe there is something else I haven't noticed, so I welcome any helps or ideas.
Edited:
Please see my Makefile link here.
As Iguananaut and Matzeri say in the comment,
cygwin make is not cygwin build
and
cygwin make is not GNUwin32 make
I open my cygwin and execute
apt-cyg install make
And redo the make command under the sphinxbase directory.
It works fine.
(However, we need to install apt-cyg in advance.)
Never use Cygwin for Linux things, it is always broken. Simply install Linux in a virtual machine.
Only a guess: Quote this to:
"C:/Program Files (x86)/GnuWin32/bin/make"
^^
(... or the related symbol)
I am trying to live with Windows (at least have to on working environment)... And I do not like cygwin actually. I am using git-bash as minimal env.
I would like to use vim as my favourite editor. After setting SVN_EDITOR to vim
export SVN_EDITOR=/bin/vim
And I have stopped on the error
'C:/Program' is not recognized as an internal or external command, operable program or batch file.
svn: E200012: system('C:/Program Files (x86)/Git/bin/vim svn-prop.tmp') returned 1
Setting vim to some more stylish dir, playing slashes and quotes didn't help. Also finally I have looked throw those issues on stackoverflow, but with no success
svn errors out strangely
Getting error trying to commit using Subversion on Mac OS X
Finally I've resolved issue by following. Hope that helps to anybody.
export SVN_EDITOR=bash /bin/vim --noplugins
You have to escape the spaces and the parentheses in your path:
export SVN_EDITOR='C:/Program\ Files\ \(x86\)/Vim/vim74/gvim.exe'
Otherwise , you'll get No such file or directory for not having escaped spaces and sh: -c: line 0: syntax error near unexpected token `(' if you forgot to escape the parentheses in your path.
I've used virtualenv to program using my mac terminal for about 1/2 a year w/no issues. Suddenly today I began to get relative path errors when I tried to load python. There was no apparent reason for it, and eventually I tried restarting my computer.
Then I opened a new terminal window, and these new errors were present for the first time:
-bash: eval: line 4: unexpected EOF while looking for matching `"'
-bash: eval: line 5: syntax error: unexpected end of file
I assume the two misbehaviors are related in some way. Any idea what would be causing it? What files could the terminal be looking at that would cause this? AFIAK, I haven't changed anything on which it would depend.
Thx for any advice!
My guess is that a bash startup file (~/.bashrc, or possibly /etc/profile, ~/.bash_profile, ~/.bash_login or ~/.profile) contains a syntax error, and that causes all sorts of errors for other programs because the setup of the environment they expect does not take place.
From the error message it seems like an unterminated string constant, i.e. a missing ".
The bash manual on startup files has information about this.
You can also try to start bash in debug mode (bash -x (interactive shell) or bash -lx ( login shell)) to try to identify the error.
My laptop crashed and when it rebooted, "cmd /" (toggle comment) was broken. When I try to toggle comments on a line that only contains "foo", I get this output in my code instead of "# foo":
/tmp/temp_textmate.2erfLj:68:in
/bin/bash: -c: line 0: unexpected EOF
while looking for matching ''
/bin/bash: -c: line 1: syntax error:
unexpected end of filemap' for "
foo":String (NoMethodError) from
/tmp/temp_textmate.2erfLj:48:in
/bin/bash: -c: line 0: unexpected EOF
while looking for matching''
/bin/bash: -c: line 2: syntax error:
unexpected end of file'
This is driving me nuts
Matt Hayes' answer pointed me to the trouble spot.
Bundles -> Bundle Editor -> Edit Commands --> Source --> Comment Line / Selection
change line 139:
- lines = text.to_a
+ lines = text.split(/$/).map(&:chomp)
#to_a is no longer a string method.
http://ruby-doc.org/core-1.9.3/String.html
I ran into the same issue and figured out a workaround. Reinstalling TextMate did not help in my case.
Bundles -> Bundle Editor -> Edit Commands --> Source --> Comment Line / Selection
At the top of the script you should see this:
#!/usr/bin/env ruby
I changed this to use another installation of Ruby. In my case I'm using RVM to manage different Ruby versions, so I have:
#!/Users/_username_/.rvm/rubies/ruby-1.8.7-p334/bin/ruby
So it seems something got screwed up with the default system Ruby.
I had this same problem. Reinstalling TextMate seems to have solved the problem.
This problem appeared after migrating from one Mac to another. I'm not sure if thats the cause though. They where both MacBook Pro's running snow leopard.
If you're using ruby 2.0 or you recently upgraded to Mavericks (system ruby in Mavericks is now 2.0), edit abovementioned command and add "-Ku" to the first line, like so:
#!/usr/bin/env ruby -Ku
Worked for me.
Has anyone tryed to install Nutch on Windows? I'm following this installation guide: http://zillionics.com/resources/articles/NutchGuideForDummies.htm
After a few bumps I'm stuck trying to run the crawler. It gives me this error:
bin/nutch: line 15: syntax error near unexpected token '$'in\r''
'in/nutch: line 15: 'case "'uname'" in
Apparently I need to install the uname utility in cygwin but I can't find it anywhere. Does anyone know in which package is it in or if there another way to fix this?
The problem isn't that uname is missing. The problem is that the nutch script has incorrect line termination. I do the following:
1) open nutch in vi
2) :set ff=unix
3) :wq
Well I've found the solution to this: uname was installed that was not the problem. The weird thing is that the shell scripts are in DOS text format instead of Unix text format. Using the 'd2u' command to convert this files fixed the problem.