Just to confuse things a bit...
When I installed LO 188.8.131.52 on my Debian-Wheezy system, the native connector
worked fine from the beginning. It does NOT work on Mint-Nadia or Windows/Vista.
Both are 32-bit systems.
Obviously - as somebody posted earlier - the connector is VERY "sensitive"
to the underlying OS, MySQL and LO-versions. I suspect it must be a nightmare
to maintain so as to make it work "independent" of which OS etc you use...
By the way, I tried "reverting" to ODBC/JDBC - not really usable for connecting
with LO. E.g., when entering new tuples into a table, default values are not
shown as defined (in create/alter table). However, when selecting the tuple
thereafter espectially so as to see what has happened, the values are shown
correctly (in SOME cases, not so in others). Under an ODBC connection, after
a while of working with Base, the CPU consumption increases considerably.
It becomes "normal" again only after saving LO/Base. So, at this point in time
there really is no choice but to get the native connector going.
I can try to install libmysqlclient18 and libmysqlcppconn5 on my Mint-system
and see what happens. Where did you download the AOO-native connector from
and which version? The version I found is from 2011.
On Thu, 21 Feb 2013 04:21:30 +0100, Dan Lewis <email@example.com> wrote:
I have a 32 bit laptop running Ubuntu 12.04. On it I have
installed LO 184.108.40.206 and 220.127.116.11.
This evening I was going to built LO 4.0.0 with the native
connector for MySQL. In the process I had to download some files needed
for autogen.sh to work properly. Among these are two groups.
These were the ones that autogen.sh had to have before it stopped
with an error message at line 201: libgnomevfs2-common,
libgnomevfs2-bin, libgnomevfs2-0, libgnomevfs2-dev, libgnomevfs2-extra,
Prior to downloading the master build, I installed two files that
Alex Thurgood suggested: libmysqlclient18 and libmysqlcppconn5 using
synaptic. I also noticed these files were available: libmysqlclient-dev
and libmysqlcppconn-dev. So I installed these also.
I had run autogen.sh a couple of times with an error stopping it
at line 201. The error led me to the first group of files which I also
installed using synaptic. Then I ran (at Alex' suggestion):
autogen.sh --with-ext-mysql-connector --with-system-mysql. (It should
have also had an option containing the path to the external mysql
connector.) So, it ignored the first option I gave it.
Since then, I have installed the MySQL Native Connector that I had
downloaded from AOO a couple of months ago. I did this to both LO
18.104.22.168 and 22.214.171.124. I have a Base file which I use to connect to my
MySQL server using the native connector. Now I can access MySQL using
this file with both 126.96.36.199 and 188.8.131.52.
So the reason for this email including the QA people is that I
would like a simple test done by someone with a 32 bit Debian system and
MySQL server. Please install the AOO MySQL native connector. Also
install these two files: libmysqlclient18 and libmysqlcppconn5. With
these installed, can you connect to MySQL? If so, part of our problem is
Tomorrow, I am going to run autogen.sh with the three needed
options. Hopefully, I will build a native connector for LibreOffice.
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
For unsubscribe instructions e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy