Well, I removed Apache2, and mod_php 4.3.2r2. Removed my config files/directories to make sure there was no confusion. Checked /etc/make.conf (<red-faced>my USE line was set right for my system, but someone forgot to remove the # character at the beginning of the line</red-faced>. My USE line is:
USE="-X -gtk -gnome -alsa libwww maildir sasl ssl -ipv6" Have I missed anything special for PHP? (my research hasn't revealed anything needed here for PHP). Note, I had to remove IMAP from this list because it wanted to install uw-imap, whereas I already have Courier-IMAP installed. Anways, I did "emerge mod_php", which then installed Apache 1.3.27, and mod_php. Next, I ran the command "ebuild /usr/portage/dev-php/mod_php/mod_php-4.3.2.ebuild config I then checked through the config files and made sure everything looked right. (-D PHP is in the /etc/conf.d/apache file. Next, I restarted Apache and tried retrieving a PHP file from my Windows box. Was prompted to save the file. I then rebooted the server, then tried tried again (with Apache running), and was again prompted to save the file. I did save the file, and examined it with notepad - the raw php code was present (i.e. <? phpinfo(); ?> ), not the rendered text. At this point, I think I'm missing something in my kernel, or had/have the wrong configuration for the USE variable when I compiled apache/mod_php. I'll bring the box to the install-fest, and see if someone can point out what I missed. If not, no big deal just yet - I can write plain HTML code just as easy. Using server-side code would make life much easier though. Thank you to everyone who has contributed to this thread. And to everyone else for putting up with me difficulties. Shawn -----Original Message----- From: Trevor Lauder [mailto:[EMAIL PROTECTED] Sent: Friday, June 20, 2003 10:35 AM To: [EMAIL PROTECTED] Subject: RE: (clug-talk) Apache 2 and PHP Shawn Grover said: > The only issue with this is that Apache2 is also considered unstable (it's > masked). So, by removing the "~x86" from the ACCEPT_KEYWORDS, we will end > up installing Apache 1.x. Not a big deal. There is no real reason I'm > trying to run Apache2 (other than it's has newer features/patches > applied). > I'll go through this exercise tonight - It only takes about 30 minutes to > emerge Apache / mod_php. You can use "~x86" on a per-package bases if you want. The command: ACCEPT_KEYWORDS="~x86" emerge apache -p should tell you it's going to emerge apache 2.0.46 as that is the latest 2.0.x release. It can get a little annoying sometimes if you have lots of "~x86" packages installed but you don't want the whole system that way because when you do a 'emerge -Duv world' it will probably try to downgrade any packages that were installed using "~x86". I created a script that takes a list of packages that I have installed using "~x86", does an 'emerge sync' and then uses sed to replace "~x86" with "x86" in those ebuilds. That way portage will think those packages are really stable. An example for apache would be in /usr/portage/net-www/apache/apache-2.0.46.ebuild, I replaced the line: KEYWORDS="~x86 ~ppc ~alpha ~hppa ~mips ~sparc" with: KEYWORDS="x86 ~ppc ~alpha ~hppa ~mips ~sparc" That way, I don't have to worry about setting the "~x86" keyword when I want to install it. That line needs to be modified every time you do a 'emerge sync' because it will over-write that file, but my little script does all the work for me. There might be a better way, but I found this system I wrote out works for me. I'm really busy at the moment, but I will post that script as soon as I can :) Cheers, -- Trevor Lauder Web: http://www.thelauders.net E-Mail: [EMAIL PROTECTED] Resume: http://www.thelauders.net/resume/ Gentoo Linux Powered "Any intelligent fool can make things bigger and more complex... It takes a touch of genius -- and a lot of courage to move in the opposite direction." -- Albert Einstein
