-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 2, 2007, at 19:19:34, Geoffrey Sneddon wrote:
On 2 Sep 2007, at 23:42, Juan A. Pons wrote:
See my previous email, as yes other programming environments work
perfectly well with this MySQL installation and as a matter of
fact so does PH
On 2 Sep 2007, at 23:42, Juan A. Pons wrote:
See my previous email, as yes other programming environments work
perfectly well with this MySQL installation and as a matter of fact
so does PHP when using the packaged configure script. As my bug
reported, the problem occurs only after rebuild
On Sep 2, 2007, at 10:08 AM, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After seeing the incorrect runtime path in the library I find it
hard to believe that any app would actually run if linked against
the libraries and the symlink didn't exist.
Actually it would be
On Sep 2, 2007, at 8:56 AM, BuildSmart wrote:
BTW this is the first time anyone has asked for any diagnostic
information... Here is the output you requested:
$ otool -L /usr/local/mysql/lib/libmysqlclient.dylib
/usr/local/mysql/lib/libmysqlclient.dylib:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After seeing the incorrect runtime path in the library I find it hard
to believe that any app would actually run if linked against the
libraries and the symlink didn't exist.
Actually it would be pretty much impossible becuase as far as linking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 2, 2007, at 06:55:54, Juan A. Pons wrote:
On Sep 1, 2007, at 10:57 PM, BuildSmart wrote:
But the problem only exists when you use the mysql.org binaries so
that should tell you something.
Apparently does not, since a second bug was
On Sep 1, 2007, at 10:57 PM, BuildSmart wrote:
But the problem only exists when you use the mysql.org binaries so
that should tell you something.
Apparently does not, since a second bug was filed after mine was
classified as Bogus. I have also tried a completely clean install
TWICE to
