Gisle Vanem

My motive for *Large file support* was to build KitchenSink using MSVC (and/or clang-cl). But due to the above, I figured I had to add `-DQT_NO_FILESYSTEMWATCHER` to the CFLAGS. This...

I did build my `make.exe` with `#define HAVE_CASE_INSENSITIVE_FS 1`. Did you? And BTW, I do not use Cygwin's terminal nor CMD. I use [4NT](http://jpsoft.com). But that should not matter.

Here is (for me) a clearer `test-fs-issue.bat`: ```bat :: :: Test for issue: :: https://github.com/mbuilov/gnumake-windows/issues/3 :: @echo off setlocal echo. > my.h echo all: My.moc.cpp > issue-3.mk echo `%.moc.cpp: %.h;...

> but it seems to me that entry 4 is the one No, with `py -3 python-example\cmdline.py -c 12D -a 4`, I just get another PortAudio error-code: ``` ... programname...

Very well, but the `make-4.3-warn-env.patch` could be useful sometimes. But it should IMHO add more fine-control of warnings. And how about warnings on *unused variables*?

BTW. I get a warning on the use of `$(MAKECMDGOALS)`. It is a built-in variables. E.g. `make clean` ->`MAKECMDGOALS = clean`.

I'm not very familiar with git pull request. But my attempt: https://github.com/google/benchmark/pull/1488

> BIO_new_ef() What kind of OpenSSL library is this? (Google came up pretty blank on this function).

Here: http://www.watt-32.net/dx/PR_090226-0558_01200kHz_000_055900_060030.wav (720 MByte!!) *Edit:* Hang on. The upload failed. It's ready now.

> This file looks nothing like the first screenshot on my install Try zooming a bit. The file I uploaded **is** the same .wav-file in this PR. > looks like...