On Jul 6, 2008, at 19:02, John Korchok wrote:
> Good news for Oracle Mac users! The Instant Client for Intel > machines has > finally been released > http://www.oracle.com/technology/software/tech/oci/instantclient/ > htdocs/inte > l_macsoft.html > > Ryan, when time permits, would it be possible to get an upgrade to > Macports > php5 +oracle to include the new Intel version? Thanks many times > over! The > PPC version has not been upgraded from the earlier 10.1.0.3. oracle-instantclient was already updated to support Intel on 2008-05-16; see r36833 and r36865. > I have included > my earlier notes below about wrinkles in previous installation. Can > Macports > add the path to opt/local/apache2/bin/envvars? I'm not sure; I'll have to look into this. Is there already a ticket filed? If not, please file one and assign it to me so I don't forget. > John Korchok > >> -----Original Message----- >> From: Ryan Schmidt [mailto:[EMAIL PROTECTED] >> Sent: Friday, February 15, 2008 11:50 PM >> To: John Korchok >> Cc: 'MacPorts Users' >> Subject: Re: Oracle Notes >> >> On Feb 3, 2008, at 16:14, John Korchok wrote: >> >>> For anyone else who may be struggling with getting Oracle >> to play with >>> MacPorts PHP, here are my notes after installation on three systems >>> and about 100 hours of tinkering. Start with a PowerPC, as >> the Oracle >>> Instant Client for Mac does not yet work with Intel machines. >>> >>> 1. Install php5 with oracle support: >>> sudo port install php5 +apache2 +oracle >>> >>> 2. So that the Apache user can find the relevant files, add >>> environment variables to opt/local/apache2/bin/envvars: >>> export LD_LIBRARY_PATH="/opt/local/lib/oracle" >>> export TNS_ADMIN="/Applications/Oracle" (or whatever folder is a >>> convenient spot to store sqlnet.ora and tnsnames.ora) Many >> web sites >>> refer to setting DYLD_LIBRARY_PATH, you can do that instead of >>> LD_LIBRARY_PATH and it has the same effect. Heck, use 'em both for >>> good measure! >> >> I'm surprised LD_LIBRARY_PATH has any effect. I thought that >> was for Linux and DYLD_LIBRARY_PATH was the Mac OS X equivalent. >> >> I'm also surprised you needed to set this variable at all. I >> thought that fixing the library name with install_name_tool >> like I do in the portfile would make this unnecessary. What >> error occurs if you do not set this variable? >> >>> Do _not_ use putenv in a PHP script or SetEnv in httpd.conf >> to set the >>> variables, it won't work. Apache will also not pick up environment >>> variables from /private/etc/profile. Note to Ryan: can >> MacPorts update >>> envvars? >> >> MacPorts can set environment variables for its own use during >> any of the phases (configure, build, destroot, etc.). However >> these do not persist after the port has been installed. >> >>> 3. Restart Apache > > _______________________________________________ > macports-users mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
