Re: question

ok, that makes alot of sense, and i bet you are right. So, now, since i want to include this thing called TWIG, in which the instructions given are clearly a static compile, then i guess i have to use the big static PHP setting, instead of the dynamic one that i now have working, right? .. i guess the more things you add, the more you will have to go static? thanks On Fri, 17 Nov 2000, Chris Lee wrote: > ok, this is where people start yelling and screaming saying im wrong, but > Im pretty sure this is how it works. > > when you compile as static it takes all the libraries you asked to link > with, ie. libgd, MySQL, libpdf, etc and puts them inside the libphp4 file, that > way libphp4 gets big, its slightly faster (problably not much if any), > and if some hacker kid gets in your system and puts a trojan version of > libpdf, then your libphp4 isnt affected because you compiled it > statically (I dont think this is a huge concern) > > I usually compile as shared just so that I can be lazy and dont have to > recompile php if I compile a new version of libpng etc. > > Chris Lee > > > > In article <Pine.OSF.4.30.0011171811400.16402-100000@ewald.mbi.ucla.edu>, > holton@mbi.ucla.edu wrote: > > > > > I just wanted to say thanks to everyone who has helped in this list. I > > have yet another question: > > > > Can anyone explain the different between static and dynamic PHP? And > > does making a new static PHP have any effect on an already running > > dynamic PHP > > (libphp4.so) sitting in my /usr/lib/ and /usr/lib/apache directories? > > thanks again, > > > > > > > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > For additional commands, e-mail: php-general-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net >