Bug #15637 compilation error: invalid conversion from `const char*' to `char*'
Submitted: 9 Dec 2005 15:55 Modified: 12 Jan 2006 8:50
Reporter: Chuck Foster Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.16 OS:Linux (Fedora 2)
Assigned to: CPU Architecture:Any

[9 Dec 2005 15:55] Chuck Foster
Description:
Error reported during make:
mysqld.cc: In function `int main(int, char**)':
mysqld.cc:3306: error: invalid conversion from `const char*' to `char*'

configure arguments specified:
CFLAGS="-O3" CXX=gcc \
CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" \
./configure \
        --prefix=/usr/local/mysql-5.0.16 \
        --with-unix-socket-path=/usr/local/mysql/etc/mysql.sock \
        --with-localstatedir=/var/db/mysql \
        --with-innodb --with-libwrap \
        --with-openssl=/usr

Looking at the code shows it is within a LIBWRAP definition, recompiling without libwrap support succeeds without a problem.

compiler used: gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)

How to repeat:
using the configuration options above, specifically --with-libwrap

Suggested fix:
not known at this point
[12 Dec 2005 8:50] Valeriy Kravchuk
Thank you for a problem report. Sorry, but I was not able to repeat with the latest 5.0.18-BK sources on my Fedora Core 1 box (the closest to FC2 I was able to found). I had performed the following commands:

./configure --prefix=/home/openxs/dbs/5.0 --with-libwrap
make

and make worked OK for me. My environment is the following:

[openxs@Fedora mysql-5.0]$ gcc --version
gcc (GCC) 3.3.2 20031022 (Red Hat Linux 3.3.2-1)
Copyright (C) 2003 Free Software Foundation, Inc.
...

[openxs@Fedora mysql-5.0]$ uname -a
Linux Fedora 2.4.22-1.2115.nptl #1 Wed Oct 29 15:42:51 EST 2003 i686 i686 i386 GNU/Linux

So, can you, please, try to download and compile latest snapshot (http://downloads.mysql.com/snapshots/mysql-5.0/mysql-5.0.18-nightly-20051211.tar.gz)  with the same options?
[13 Jan 2006 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".