Hi!
Ok, let see if I remember the commands to get info:
uname -a: Linux srv73 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux
gcc --version: gcc (Debian 4.7.2-5) 4.7.2
dpkg -l | grep boost: libboost-dev 1.49.0.1, libboost1.49-dev 1.49.0-3.2
I rarerlly see the -Werror option when clonning from trees. Using -Werror by default involves messing a lot of sources which are used to build drizzle, like protobuf, and others, which have minnor error in code which are obsolete to new gcc standard, like arrays ending with comma, which is tottaly normal this days. Usually this generates only warnings, but with -Werror it stops.
I think drizzle should update to gcc++0x or gcc++11, and make -Werror disabled by default and use a switch to enable it for code sanitize.
I've seen in ./configure that gcc++0x is present to be enabled, but it always uses gcc++98. What condition leads to this I don't know.
Hi!
Ok, let see if I remember the commands to get info:
uname -a: Linux srv73 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux
gcc --version: gcc (Debian 4.7.2-5) 4.7.2
dpkg -l | grep boost: libboost-dev 1.49.0.1, libboost1.49-dev 1.49.0-3.2
I rarerlly see the -Werror option when clonning from trees. Using -Werror by default involves messing a lot of sources which are used to build drizzle, like protobuf, and others, which have minnor error in code which are obsolete to new gcc standard, like arrays ending with comma, which is tottaly normal this days. Usually this generates only warnings, but with -Werror it stops.
I think drizzle should update to gcc++0x or gcc++11, and make -Werror disabled by default and use a switch to enable it for code sanitize.
I've seen in ./configure that gcc++0x is present to be enabled, but it always uses gcc++98. What condition leads to this I don't know.