Tag Info

New answers tagged

1

The file you're using has windows style line feeds (CR) at the end of them (same thing happened to me using Cygwin on Windows XP). Use 'dos2unix.exe' to rectify and you should be ok: $ dos2unix.exe script.sh dos2unix: converting file script.sh to Unix format... Then rerun your script and those error messages should no longer appear.


2

This looks like the version that patched shellshock (Subject to other bug variations / patches.) for cygwin bash: Date: Mon, 29 Sep 2014 15:22:43 -0600 https://cygwin.com/ml/cygwin-announce/2014-09/msg00040.html AKA: 4.1.14-7 " This is a minor rebuild which picks up an upstream patch to fix CVE-2014-7169 and all other ShellShock attacks (4.1.13-6 was ...


0

Run ./configure -cc "gcc -Wl,--stack,16777216" (plus any other option you want) if you want to always run gcc with the argument -Wl,--stack,16777216 during the compilation process. After that, run make clean, then make world.opt again. You need to clean all previously generated binaries (not the byte compiled files, but it's easier to just do make clean) so ...


0

With makefiles that follow standard conventions, you can use make CC='gcc -fwhatever or make CFLAGS='-fwhatever'. (For C++, it's CXX and CXXFLAGS)


4

As per the official Cygwin Installation Page: Installing and Updating Cygwin for 64-bit versions of Windows Run setup-x86_64.exe any time you want to update or install a Cygwin package for 64-bit windows. The signature for setup-x86_64.exe can be used to verify the validity of this binary using this public key. I had a hunch this bash was ...



Top 50 recent answers are included