If the configure script is provided with depends, it drops WARN_CXXFLAGS:
0$ CONFIG_SITE=$PWD/depends/x86_64-pc-linux-gnu/share/config.site ./configure
1...
2 CC = gcc -m64
3 CFLAGS = -pipe -O2
4 CPPFLAGS = -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -I/home/hebasto/bitcoin/depends/x86_64-pc-linux-gnu/share/../include/ -DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS
5 CXX = g++ -m64 -std=c++11
6 CXXFLAGS = -fstack-reuse=none -Wstack-protector -fstack-protector-all -pipe -O2
7 LDFLAGS = -pthread -Wl,-z,relro -Wl,-z,now -pie -L/home/hebasto/bitcoin/depends/x86_64-pc-linux-gnu/share/../lib
8 ARFLAGS = cr
9
10$ ./configure
11...
12 CC = gcc
13 CFLAGS = -g -O2
14 CPPFLAGS = -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS
15 CXX = g++ -std=c++11
16 CXXFLAGS = -fstack-reuse=none -Wstack-protector -fstack-protector-all -Wall -Wextra -Wformat -Wvla -Wswitch -Wformat-security -Wredundant-decls -Wunused-variable -Wdate-time -Wno-unused-parameter -Wno-implicit-fallthrough -g -O2
17 LDFLAGS = -pthread -Wl,-z,relro -Wl,-z,now -pie
18 ARFLAGS = cr
If this done intentionally, what are the reasons for that?
Or is it just a bug?