Bug #59122 | 5.1.53 build broken on centos 5.2 | ||
---|---|---|---|
Submitted: | 23 Dec 2010 4:04 | Modified: | 23 Dec 2010 23:51 |
Reporter: | Mark Callaghan | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Compiling | Severity: | S2 (Serious) |
Version: | 5.1.53 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | 5.1.53, build, SOURCE |
[23 Dec 2010 4:04]
Mark Callaghan
[23 Dec 2010 5:11]
MySQL Verification Team
looks like bug #57989
[23 Dec 2010 16:13]
Mark Callaghan
We are back to warning spam as these were also added to the build but the numerous warnings that follow were not fixed. And now serious warnings added by new code will get lost from the less serious warnings about unused parameters. -Wextra -Wunused -Wwrite-strings -Wno-strict-aliasing -Wno-unused-parameter With the flags above there are 41300 warnings in my 5.1.53 build
[23 Dec 2010 17:40]
Davi Arnaut
This is a bug in system headers that I think we will have to workaround. AFAIK, it builds mostly clean if used properly. For example, a -Wall flag will cancel a previous -Wno-unused-parameter. This will happen if one adds it via CFLAGS/CXXFLAGS and at the same time use the MySQL maintainer mode flags.
[23 Dec 2010 17:48]
Mark Callaghan
How do I avoid using maintainer mode? Because of my patches, I run BUILD/autorun.sh
[23 Dec 2010 17:48]
Davi Arnaut
--with-debug automatically enables the MySQL maintainer mode. Also, recent systems will provide a hack for this problem. For example, on OS X: termcap.h:extern NCURSES_EXPORT(int) tgetflag (NCURSES_CONST char *); Another thing, the fact that the flags leak to readline/libedit is a bug that we do not intended to fix on 5.1. We are not aiming for warning free code in third-party tools that we ship.
[23 Dec 2010 17:51]
Davi Arnaut
> How do I avoid using maintainer mode? Because of my patches, I run BUILD/autorun.sh There is a configure time option. Look at ./configure --help. For example, --with-debug --enable-mysql-maintainer-mode=no should disable it.
[23 Dec 2010 23:51]
Sveta Smirnova
Thank you for the report. Shane is right: this is duplicate of bug #57989