Gisle Vanem

> Do you have something like COLORFGBG="15;4" in that terminal? I do not understand. I'm on Windows and `COLORFGBG` is a Gnome thing AFAICS. > Is the theme a Windows...

> .. and not the full color scheme, can you? I guess not. Have not tried [ColorTool](https://github.com/microsoft/terminal/tree/main/src/tools/ColorTool) and rtl_433. But I have yet to try this patch here to see...

> with limited functionality. Limited how?

gcc/ld does not like this: ```c CPPFLAGS += -I"$(WATT_PATH)/inc" _LDFLAGS += -L"$(WATT_PATH)/lib" ``` But this works: ```c CPPFLAGS += -I$(WATT_PATH)/inc _LDFLAGS += -L$(WATT_PATH)/lib ```

> What environment / gcc/ld version is where double-quotes are not recognized? I'm on Win-10 using djgpp's gcc ver. 12. > CPPFLAGS += "-I$(WATT_PATH)/inc" That doesn't work either: ``` f:/gv/djgpp/windows/bin/i586-pc-msdosdjgpp-gcc...

> Another option is to give up supporting dependency paths with spaces. Agree. Having paths with spaces in SW-development is madness.

But single quotes works: ``` CPPFLAGS += -I'$(WATT_PATH)/inc' _LDFLAGS += -L'$(WATT_PATH)/lib' ``` So perhaps some shell/make issue?

Add a `--debug-all` (to latest gnumake or mingw32-make), I see this passed to `sh.exe`: ``` CreateProcess(f:\CygWin64\bin\sh.exe,f:/CygWin64/bin/sh.exe -c "f:/gv/djgpp/windows/bin/i586-pc-msdosdjgpp-gcc -W -Wall -Wno-type-limits -Wno-sign-compare -I. -I../include -DNDEBUG -I\"f:/gv/net/watt/inc\" -DBUILDING_LIBCURL -c cfilters.c -o...

> Is it so that you're using a Cygwin shell with a non-Cygwin mingw32-make? That's correct. Have worked fine for year. *Edit:* I spawn Cygwin's `sh.exe` from my [4NT](https://jpsoft.com) shell....

> C:\msys64\mingw64\bin\mingw32-make -C src -f Makefile.mk Try with `make --warn-undefined-variables -C src -f Makefile.mk`. There's a lot!