Re: Can't Install DBD::mysql
[email protected] ("Enrique Terrazas")
| Newsgroups | perl.macosx |
|---|---|
| Message-ID | <[email protected]> |
Take a look at the following to specify the makefile flags: <http://jayallen.org/journey/2006/04/dbd-mysql-build-problems-on-mac- book-pro> Enrique On Nov 28, 2007, at 2:58 PM, Charlie Minow wrote: > On Nov 28, 2007, at 3:51 PM, Lola J. Lee Beno wrote: > >> Charlie Minow wrote: >>> I ran into this on Tiger as well. For some reason, it's looking >>> for the MySQL libraries in the wrong place. MySQL puts them in�/ >>> usr/local/mysql/lib, but the make file for DBD::mysql looks a >>> little deeper, in�/usr/local/mysql/lib/mysql. I could never >>> figure out how to fix that path in the makefile, so, in the >>> interest of getting on with my life, I made a "mysql" directory >>> in /usr/local/mysql/lib, then copied all the dylib files into that. >> As in copy all the files that already exist in /lib into /mysql >> directory which I need to create, right? > > Right. I just copied the ".dylib" files and none of the other ones > into the new "mysql" directory, though. So far, it's all good. > > charlie > -- > Charlie Minow > [email protected] > http://www.cminow.org > > "...it may well be doubted whether human ingenuity can construct an > enigma of the kind which human ingenuity may not, by proper > application, resolve." - Edgar Allen Poe, The Gold Bug > > > > -- Enrique Terrazas, MD, MS Director, Laboratory Medicine Residency Program Director, NCPL Laboratories Chief, Laboratory Information Systems HS Associate Clinical Professor University of California, San Francisco Clinical Laboratories, Box 0100 415.353.1375(UCSF/China Basin phone) 415.353.1620(UCSF/Parnassus phone) 415.353.4826(fax) 415.443.0913(pager) [email protected] CONFIDENTIALITY NOTICE: The information contained in this transmission, including any enclosed files, is confidential and intended solely for the addressee. If you are not the intended recipient, you are hereby notified that any distribution, copying, disclosure and use of, the contents of this transmission is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply email and permanently delete this message, enclosures and all copies.