Bug #77655 CXXFLAGS and CFLAGS are populated with server flags instead of the system ones.
Submitted: 8 Jul 2015 11:24 Modified: 17 Nov 2015 19:29
Reporter: Marcin Szalowicz Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / C++ Severity:S3 (Non-critical)
Version:1.1.6 OS:Any
Assigned to: CPU Architecture:Any

[8 Jul 2015 11:24] Marcin Szalowicz
Description:
When building connector c++ the MySQL Server CXXFLAGS and CFLAGS are being used instead of the system default ones.
This is causing later problems during library usage if application maintainer doesn't know about it.
For example this is how it's done in Debian by default:
https://people.debian.org/~doko/logs/gcc5-20150701/mysql-connector-c++_1.1.3-6_unstable_gc...
For now in Workbench we're always forced to rebuild connector with disabled server flags.

How to repeat:
Build connector c++

Suggested fix:
Connector c++ shouldn't use by default cflags and cxxflags from the server. instead, a system default cxxflags and cflags should be used. 
Also option for cmake should be available to use server flags if someone needs that.
[17 Nov 2015 19:29] Paul Dubois
Noted in 1.1.7 changelog.

During Conneector/C++ builds, the MySQL Server CXXFLAGS and CFLAGS
values were used rather than the system default values.
[17 Nov 2015 22:39] Paul Dubois
Revised changelog entry:

During Conneector/C++ builds, the MySQL Server CXXFLAGS and CFLAGS
values were used rather than the system default values. To specify
explicitly to use the server values, enable the new
USE_SERVER_CXXFLAGS CMake option.