Building additional modules after installing core modules

Building additional modules after installing core modules

am 10.11.2008 06:09:54 von Baskara

I decided to install php from source. I have installed the core
modules only. Is that possible to install additional modules 〔such as,
gd, ming bcmath etc〕after installing php core modules without
compiling the entire source code?

On 11/9/08, Fergus Gibson wrote:
> On Sun, Nov 9, 2008 at 11:58 AM, TG wrote:
>> Shared hosting is fine.. I don't mind a little "slow" every now and then.
>> For what this customer needs, a full dedicated server is total overkill.
>>
>> But the big problem here is that if you exceed a certain amount of CPU
>> and/or
>> slow query time in a given 60 second window, your site visitors get a big
>> message saying "CPU/Queries Exceeded!" and they disable your account for
>> 5-10 mins.
> [...]
>
> It doesn't sound like you think that's fine. It sounds like you have
> a problem with it. A dedicated server will solve that problem. Your
> only other realistic option is to dump this provider for another one.
> But there's no guarantee you won't have exactly the same problem or
> worse on someone else's shared server. The point is that shared
> hosting is something you don't control. With a dedicated server, you
> can call all the shots. Yes, it's expensive, but it's a trade-off.
>
> I've this sort of bullcrap from other hosts before. It's not limited
> to one host. It happens. A company I worked for stopped working with
> clients who wanted to put our application on shared hosting because it
> was too much of a headache. One client, for example, had his site
> disabled because the host felt it generated too many database queries.
> Um, well, they didn't publish anything about that in their ToS. You
> just sign up, roll the dice, and discover whether the host will work
> for you. And in the process, you've got a lot of PITA. So I don't
> recommend a shared host for providing a database-driven application of
> any significant size.
>
> Good luck trying to persuade your chosen host to amend their policies
> or improve their server.
>
> --
> PHP Database Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--
Sent from Gmail for mobile | mobile.google.com

--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: Building additional modules after installing core modules

am 10.11.2008 06:24:45 von dmagick

Baskara wrote:
> I decided to install php from source. I have installed the core
> modules only. Is that possible to install additional modules ?such as,
> gd, ming bcmath etc?after installing php core modules without
> compiling the entire source code?

Please don't reply to someone elses thread with something new. Hijacking
threads is frowned upon and makes things hard to follow.

You have to compile against the same source code as the base (ie it has
to be the same version, you can't compile the core as 5.2.4 and the new
version as 5.2.6). Whether that compiles the whole lot again depends on
what you're adding and whether the original compiled version was kept or
not. gcc ignores the bits it doesn't need to do again if it'll turn out
exactly the same.

--
Postgresql & php tutorials
http://www.designmagick.com/


--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: Building additional modules after installing core modules

am 10.11.2008 13:33:03 von Goltsios Theodore

> I decided to install php from source. I have installed the core
> modules only. Is that possible to install additional modules 〔such as,
> gd, ming bcmath etc〕after installing php core modules without
> compiling the entire source code?
>

Try not to top-post.

If you need the flexibility to add additional extensions that are not
modules installed using pecl it is better to use a package system. Most
distros are including in their repositories php modules like php-gd,
php-soap, php-mssql etc. Why compile if you don't need to.

This of course can be used if compiling php for performance is not
mandatory. If otherwise have in mind that you need not only to compile
the modules against the same src tree but to configure the src tree the
same way as the installed php. Thus you will have to keep the original
src you used to install php on the first place. At least IMHO this is
the best practice.

--
Thodoris


--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php