# Tag Info

39

I was starting to get an exception as well: make: Interrupt/Exception caught (code = 0xc00000fd, addr = 0x4227d3) Might be a different reason, but this problem is apparently caused when the PATH variable contains parentheses (, ), as it does on Win Vista/7. Unfortunately, the available GNU for Windows is hopelessly outdated. My problem was fixed by ...

29

bash is probably getting started as a login shell, in which case it doesn't read .bashrc automatically. Instead, it reads .bash_profile. From the Bash manual: So, typically, your ~/.bash_profile' contains the line if [ -f ~/.bashrc ]; then . ~/.bashrc; fi' after (or before) any login-specific initializations. So in summary, create a ...

14

Rather than removing Windows' find.exe, I strongly recommend putting GNU in your path before Windows\System32. For example, with Cygwin, you can use something like: path c:\cygwin\bin;c:\windows\system32;c:\windows;c:\program files\foo;c:\program files\bar;c:\windows\system32\wbem

9

$pwd -W C:/MinGW/msys/1.0/home/Steven 8 You can check out my releases of Vim for Windows to save yourself some time. It's built using MinGW-w64 toolchain (don't worry, you don't need its runtime libraries for my build to work). Have support for both x86 (32-bit) and x64 (64-bit) architectures, "huge" feature set, and scripting interfaces for most popular programming languages: Python; Ruby; Lua; ... 6 If I'm understanding you correctly, you're looking for a tabbed interface for multiple bash shells, right? If so, you could use Console2 to host your mingw windows. I use it for Cygwin and it works great! Just configure each tab in Console2 to start the MinGW bash shell. 6 I had that issue when I added Git's bin directory to the PATH environment variable. The reason seems to be that Git ships with a version of MSYS and that seems to conflict with MinGW (maybe it doesn't conflict when it's the right version of MSYS and/or MinGW but that's just guessing). So make sure that there is no (other) MSYS distribution in your PATH. 5 mingw-get is available at sourceforge.net/projects/mingw/files/Installer/mingw-get After you have that installed run mingw-get install msys-coreutils 5 Ok, the proper answer follows. To escape the arguments such that dos executables can be used, you double the slashes, such as: growlnotify //a:Application //t:Title "message here" The reason it would fail for me was because somehow I wasn't using the same application name as I had when I started the day before (and as a different application it was ... 5 I had the same issue, linking an icon from a folder without whitespace in it did a trick (I had Git installed to C:\Program Files (x86) which has whitespace in it). Simply copy the icon somewhere else, e.g. C:\icons. 5 I have just found the solution to this problem on the NetBeans forums here: http://forums.netbeans.org/topic54884.html All you need to do is: Go to C:\MinGW\bin and make a copy of mingw32-make.exe. Then rename it to make.exe Now go to C:\MinGW\msys\1.0\bin and rename make.exe to makeOLD.exe (just in case) Then move your new make.exe into ... 5 I found this one somewhere: rm -r */ Seems the easiest way to go. With your example, you would have to confirm each case, if you have 5 files it's OK, but with bigger file structures an interactive mode is't the way to go... Just as a suggestion, if it's important information, make a backup... 4 Use GuiMacro ConEmuC -GuiMacro Rename 0 "serverxyz" 4 I managed to compile a 64-bit version of gVim.exe using the full version of Visual Studio 2010 and the commands from this superuser answer: nmake -f Make_mvc.mak GUI=yes CPU=AMD64 PYTHON=C:\Python27 DYNAMIC_PYTHON=yes PYTHON_VER=27 It's probably possible with the 64-bit mingw toolset linked by heavyd too, but I couldn't find anything that worked on ... 4 Aliases are available for the NT Command Prompt through the doskey command: doskey word="%ProgramFiles%\Windows NT\Accessories\wordpad.exe"$* You may now use the alias instead of the (full) name of the executable: word %SystemDrive%\boot.ini

4

I am running Windows XP and had the same problem. I found HOWTO Create an MSYS Build Environment. This is the important line: To help identify the runtime build and the current working directory, the following can be added to the ~/.profile file. In MinGW shell, I created .profile: cd ~ touch .profile I used Notepad++ to edit it as a Unix format text ...

3

Futher to Norbet P.'s answer, I found that adding: PATH= to the top of my Makefile fixed this particular problem for me.

3

The problem is that gcc cross-compilers can be names differently. It depends on how it is built in the first place. The programs you are referring to (i686-pc-mingw32-g++ and i586-mingw32msvc-g++) are two of the many possibilities when naming the MinGW binaries. But they should behave more or less similarly. If the third-party Makefile uses this name ...

3

This make bug is fixed at least in GNU Make 3.82 Built for i686-pc-mingw32 .

3

To make your command work I don't think you can avoid sub-shelling, something like: find /cygdrive/c/MinGW/bin/ -name "*.exe" -print0 | xargs -0 -n1 bash -c 'ln -s {} $(basename {})' If all the files are in the same directory, you can also use cp -s: cp -s /cygdrive/c/MinGW/bin/* . 3 Since ln accepts directories as targets: ln -s /cygdrive/c/MinGW/bin/*.exe /path/to/otherdirectory/ 3 CtrlU will erase from the current cursor position back to the beginning of the line, so you can then type your correct password. 3 I've gone down basically the same path with the following exception: Checking for gnutls >= 2.5.0 : fail --- libeio --- Checking for library pthread : not found Checking for function pthread_create : not found error: the configuration failed (see 'd:\\Code\\Javascript\\node\\build\\config.log') config.log basically says it ... 3 Try cd /y/ to solve your problem 3 You can "escape" specific metacharacters by prefixing with backslash.$ touch 'aaa(bbb)ccc' $rm *$$*$$*$ ls $3 cd to the parent directory, then: for f in */abcd*; do mv$f ./ done that will match mydir1/abcdfoo, mydir2/abcdbar etc. and move them to the pwd (which is the parent directory). If you only want to look in directories called mydir* you could specify for f in mydir*/abcd*; do mv \$f ./ done You could also do find . -name "abcd*" -type f -exec mv {} ./ ...

3

No that would give you "missing operand" since you didn't specify anything. Putting a "*" would prompt also for files. I'd give a try to: find -mindepth 1 -maxdepth 1 -type d -exec rm -r {} \; The "mindepth 1" will exclude "." from the results, the "maxdepth 1" will exclude trying to do under the directories that will anyway get deleted (therefore ...

3

I'm not sure what version of msysgit you are using, but for me calling msys.bat does not change the current directory. If you see the directory being changed, check the etc/profile file in the msysgit directory for cd commands. As this file gets executed when a login shell is started it might be the cause for you to always land in your home directory.

3

Some console replacements support changing the colors along with other features missing with the one that comes with Windows. One example Console2. Note that behind it is still the same cmd.exe as the normal console window or another command processor if desired. An example of the settings dialog where Yellow has been made to show as blue. To setup Git ...

3

The default windows echo command adds spaces and line termination, even if called with -n. Try this: echo -n hello > a.txt followed by dir, and you'll see you don't have a 5 byte file.

Only top voted, non community-wiki answers of a minimum length are eligible