Miscellaneous > Technical Support

PHP build chokes

<< < (2/3) > >>

worker201:
Adding the apxs line to the configure changed things immensely.  Now all sorts of things are broken, including openssl and libxml2.  For starters, the Apple versions are either too far behind or corrupted in some way.  To complicate matters, the PHP makefiles will not search for the libraries you tell it to use if those libraries are found in the system folders.

An excellent discussion of why it does this, and what can be done to fix it:
http://blog.yimingliu.com/2009/02/24/missing-library-symbols-while-compiling-php-528/

I'm doing it the fun way, by renaming the system libraries temporarily, which will force the makefile to find the libraries in the locations I have specified.  Just hope I remember to change them back afterwards.

worker201:
Finally got this thing working.  Ended up having to modify the makefile.

Proof:

worker201:
Okay, the PHP issue is past.  But then I was modifying the httpd-vhosts.conf file, and suddenly Apache shit all over the rug and started complaining that it couldn't find the PHP module.  So I had to start over again.  This time, I found a method that allowed me to install Apache 2.2.14 right over top of the built-in 2.0.x version.  Then I built the PHP, and verified that it was working.  But then when I went to check my phpinfo() in the browser (Firefox), it clearly wasn't working at all.  After some testing, I found the issue, and started over AGAIN.  The browser, though, stayed open, because I was working on something else (my online job).  After finally rebuilding Apache and PHP, things seemed okay, and the server restarted without issue, and the virtual hosts were working just fine, but phpinfo() still wasn't working.  Man, I wracked my brain and kicked my computer and studied for hours about mime types and verified ten times over that everything was installed right.  Then on a whim, I decided to check it in Safari.  Worked right away, no issues.  After restarting Firefox, it worked right as well.

I guess this is normal behavior - the content of the webroot folder had not changed even by a byte, so a refresh had no effect.  For future reference, how can you force the browser to renegotiate with the host so that server function changes have an effect?  Surely it's not necessary to reboot the browser everytime I make development changes?

davidnix71:
Firefox ram/hd caches a lot of things. I force FF to delete everything but my passwords and bookmarks every time it quits, just to be sure.

I also can't get torrents to run from localhost (a desktop file) in Opera 10, either, but that worked in Opera 9. All it will do is try to resave the existing file.

piratePenguin:

--- Quote from: http://support.mozilla.com/en-US/forum/1/333668?s=cache%20refresh ---You can bypass the cache with Ctrl+F5 (IE: Shift+F5, if I'm correct) or Shift+Ctrl+R.

--- End quote ---
Firefoxes help system (press f1) is pretty damn legendary

edit: also you can hold shift while clicking the refresh button

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version