Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi,


I'm having a frustrating time trying to get configure to recognise my
mysql installation so that I can build the mysql-connector extension.

I am currently using the following switches :

--enable-ext-mysql-connector
--with-libmysql-path="path/to/libmysqlclient.dylib"

I've tried encapsulating with single quotes, even the whole switch,
alternating between single and double quotes - nada.

I thought maybe it was a permissions problem and the normal user
couldn't see the directories, so I tried configuring with sudo - nada.

Despite having 3 different places where the libmysqlclient library is to
be found on my system, configure stubbornly refuses to find the library.
Is there something obvious that I'm doing wrong ?

Additionally, the configure script looks for the file "libmysql.dylib"
on Mac OSX, which appears to be the incorrect name for the file. On my
system, all of the mysql client libraries are all called
"libmysqlclient.dylib". I corrected this in my local version of the
configure script, but it doesn't appear to have made the slightest bit
of difference. I can choose any of the 3 locations where the file
exists, and yet configure still baulks :

checking for mysqlc module... OK
checking for mysql pre-requisites... external Connector/C (libmysql)
checking for libmysqlclient.dylib... configure: error: not found. Please
specify proper path in --with-libmysql-path

So how do I specify it ?

TIA, for hints, advice, etc.


Alex


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: 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.