Bugzilla Bug 1307

Please find attached a new ebuild script for the mysql++ api. I have tested
this
ebuild in dev-db/mysql++ which is where it would seem to go.

As might be expected, mysql++ allows a programmatic interface from C++
applications.

Created an attachment (id=419) [details]
ebuild script for mysql++

this is the ebuild script

well i noticed it has a huge amount of docs, but you install -zero- of them.

could you please go through and install them, then submit your
changes.

closed bug until the original submitter updates his ebuild ...

not gonna happen -- he submitted in march. let's get this to a dev to take care
of post-freeze

Created an attachment (id=4684) [details]
Updated ebuild with docs installed as requested

correct ebuild. installs docs

Created an attachment (id=4685) [details]
Corrected ebuild

This adds in the KEYWORDS, SLOT, LICENSE fields that were missing in the update

Created an attachment (id=4710) [details]
patch to work with GCC3

this patch corrects the errors generated using gcc3

Errors out:

connection1.hh:51: after previous specification in `bool
   MysqlConnection::real_connect(const cchar* = "", const cchar* = "", const
   cchar* = "", const cchar* = "", unsigned int = 0, char = 0, unsigned int =
   60, const cchar* = "", unsigned int = 0)'
connection.cc:45: default argument given for parameter 8 of `bool
   MysqlConnection::real_connect(const cchar*, const cchar*, const cchar*,
   const cchar*, unsigned int, char = 0, unsigned int = 60, const char* = "",
   unsigned int = 0)'
connection1.hh:51: after previous specification in `bool
   MysqlConnection::real_connect(const cchar* = "", const cchar* = "", const
   cchar* = "", const cchar* = "", unsigned int = 0, char = 0, unsigned int =
   60, const cchar* = "", unsigned int = 0)'
connection.cc:45: default argument given for parameter 9 of `bool
   MysqlConnection::real_connect(const cchar*, const cchar*, const cchar*,
   const cchar*, unsigned int, char = 0, unsigned int = 60, const char* = "",
   unsigned int = 0)'
connection1.hh:51: after previous specification in `bool
   MysqlConnection::real_connect(const cchar* = "", const cchar* = "", const
   cchar* = "", const cchar* = "", unsigned int = 0, char = 0, unsigned int =
   60, const cchar* = "", unsigned int = 0)'
make[2]: *** [connection.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
c++ -DHAVE_CONFIG_H -I. -I. -I.. -I. -I../sqlplusint -I/usr/include/mysql
-march=i686 -O3 -pipe -Wp,-MD,.deps/coldata.pp -c coldata.cc -o coldata.o
>/dev/null 2>&1
mv -f .libs/coldata.lo coldata.lo
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
`/var/tmp/portage/mysql++-1.7.9/work/mysql++-1.7.9/sqlplusint'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/mysql++-1.7.9/work/mysql++-1.7.9'
make: *** [all-recursive-am] Error 2

Created an attachment (id=5049) [details]
Patch to be applied after first patch 

this will have it work with gcc 3.2

Applied patches and testing:

make[2]: Entering directory `/var/tmp/portage/mysql++-1.7.9/work/mysql++-
1.7.9/examples'
make[2]: *** No rule to make target `resetdb.@OBJEXT@', needed by 
`resetdb@EXEEXT@'.  Stop.

still working...

Created an attachment (id=6173) [details]
Patch that solves the compiling errors during example directory

Hi, this is an patch that allows to compile mysql++ without an error! (by
excluding the examples directory, that does not matter to the important files!)

Created an attachment (id=6174) [details]
ebuild that is fully compatible with gcc-3.2 ( needs the gcc-3.0, gcc-3.2, and
the example patch #6173)

Hi,

this is a full functional ebuild for building mysql++-1.7.9 with gentoo-1.4
(gcc-3.2).
It needs the example patch #6173 and the mysql-gcc3.0 and mysql-gcc3.2 patches.

Then it compiles without errors. My applications compile and work well.
cya

Created an attachment (id=6175) [details]
official mysql++-gcc-3.0-patch

the official mysql++-gcc-3.0.patch i used for #6174

Created an attachment (id=6176) [details]
offical mysql++-gcc-3.2.patch

offical mysql++-gcc-3.2.patch i used for #6174

have a nice try

committed.

Sorry i've to REOPEN this bug, as i found again some big problems in mysql++
with gcc-3.2.1, but finally (after quite a long time!) i got that fixed ;-)!
For me mysql++-1.7.9 works, and even my old source code runs again.

The following attachments are the modified ebuild, and the patch fixing some
throw errors, that prevented programs (not the package!) to compile!

So for my state of view, the package may become stable after quite a few tests
by other users!

Created an attachment (id=8161) [details]
modified ebuild that should allow to use the mysql++ api

Created an attachment (id=8162) [details]
patch that corrects some throw() errors during compiling custom projects
againts mysql++ api

I get this error message while emerging mysql-1.7.9-r1: 

( i have mysql 4.0.13-r3 )

shell> emerge mysql++

>>> Unpacking mysql++-1.7.9.tar.gz mysql++-gcc-3.0.patch.gz mysql++-gcc-3.2.patch.gz to /var/tmp/portage/mysql++-1.7.9-r1/work 
/usr/sbin/ebuild.sh: line 289: ${x%.*}: ambiguous redirect 

!!! ERROR: dev-db/mysql++-1.7.9-r1 failed. 
!!! Function unpack, Line 289, Exitcode 1 
!!! failure unpacking mysql++-1.7.9.tar.gz mysql++-gcc-3.0.patch.gz mysql++-gcc-3.2.patch.gz 



Am I the only one getting this error message? 
Seems like a ebuild error in my eyes.

try updating portage.   
emerge rsync 
emerge portage 
emerge mysql++