[csw-maintainers] MySQL built with GCC ??? mysql_config vs bindings
Rafael Ostertag
raos at opencsw.org
Mon Jun 18 07:54:29 CEST 2012
On Sun, Jun 17, 2012 at 09:39:33PM +0100, Maciej (Matchek) Blizi??ski wrote:
> I've pushed MySQL 5.5 to unstable and it's now on the buildfarm. It's
> built with GCC, and mysql_config returns GCC specific flags:
>
> $ mysql_config --cflags
> -I/opt/csw/include/mysql -pipe -m32 -fPIC -g -static-libgcc
> -fno-omit-frame-pointer -fno-strict-aliasing
>
> This has just caused trouble for Juergen when building Nagios plugins.
>
> One fix would be to build MySQL 5.5 with Solaris Studio. The latest attempt:
>
> "/home/maciej/src/opencsw/pkg/mysql5/branches/mysql-5.5.x/work/solaris10-sparc/build-isa-sparcv8plus/mysql-5.5.25/libmysqld/../sql/rpl_utility.h",
> line 274: Warning: extra ";" ignored.
> "/home/maciej/src/opencsw/pkg/mysql5/branches/mysql-5.5.x/work/solaris10-sparc/build-isa-sparcv8plus/mysql-5.5.25/libmysqld/../sql/mysqld.cc",
> line 3255: Error: The function "getpagesizes" must have a prototype.
> "/home/maciej/src/opencsw/pkg/mysql5/branches/mysql-5.5.x/work/solaris10-sparc/build-isa-sparcv8plus/mysql-5.5.25/libmysqld/../sql/mysqld.cc",
> line 3259: Error: The function "getpagesizes" must have a prototype.
> "/home/maciej/src/opencsw/pkg/mysql5/branches/mysql-5.5.x/work/solaris10-sparc/build-isa-sparcv8plus/mysql-5.5.25/libmysqld/../sql/mysqld.cc",
> line 3276: Error: The function "memcntl" must have a prototype.
> "/home/maciej/src/opencsw/pkg/mysql5/branches/mysql-5.5.x/work/solaris10-sparc/build-isa-sparcv8plus/mysql-5.5.25/libmysqld/../sql/mysqld.cc",
> line 3278: Error: The function "memcntl" must have a prototype.
> 4 Error(s) and 1 Warning(s) detected.
>
> I'm thinking what's the best way to go about it. Spend time on porting
> it to Studio? (It's less and less fun as time goes by.) Patch
> mysql_config and remove the GCC related flags? Thoughts?
As long as it is only including missing header files, I personally would walk that path. When it reaches
the state of patching code, because, e.g. functions are missing or not behaving
the way developers expect them to behave, I would give moving away from
SunStudio a more thorough thought.
cheers
rafi
More information about the maintainers
mailing list