compile IMAP into PHP 4.2.3

[silvernetuk]

Hi,

I have been trying to compile IMAP support into PHP 4.2.3 by using the latest buildapache.sea, when I try and install IMAP with Mcrypt and GD it fails (not noted error) but when installing IMAP on it only it ok, but I need to have Mcrypt, GD and IMAP compiled into PHP.

Does anyone have the answer to compile it with using buildapache.sea or can you give me a step by step guide on how to manual install IMAP with Mycrypt, GD and the other standard stuff into PHP 4.2.3 ?

Regards,
Garry

 

[silvernetuk]

Hi,

This has now been installed and working

Regards,
Garry

 

[myusername]

Yes I know this post is verrrrry old but silvernetuk or any others out there what did you do to get Imap with GD and Mcrypt into php? (as well as the defaults via WHM)

 

[myusername]

I think I will bump this one since it ha been a reeeealy long time since I asked last.

Anyone had any success with this?

 

[brentp]

Old post. Mods, please lock.

Regards,
Brent

 

[B12Org]

I would imagine he upgraded his backend, and server software - then compiled apache with the latest php build with the desired modules. I know that sounds too simple . . .

 

[myusername]

Old post. Mods, please lock.

Regards,
Brent

Go away. Unless you have anything useful to say.

Do you even know how to use easy apache or the apache update in WHM?

The question was, is this issue resolved? It might be nice to know before someone tries to compile Apache and it fails.

Why post something asking mods to close a thread, simply because you do not know the answer.

 

[B12Org]

Althoguh your wording is harsh, I kind of agree with the principal - however keep in mind that this issue is almost a year old and doubtfull that the "bug" (if there was one) in the php compilation still occurs since it has newer versions.

 

[myusername]

There was (still might be) a bug in it that would not allow one to compile IMAP with things like GD and mcrypt, for a very long time.

it existed long before our buddy brentp even had his cPanel forum logins, and last I checked, was still and issue, which was only several months back.

Maybe it as harsh, but what I really wanted to say was worse. It just does not make an inkling of sense to close a thread such as this because the date is "old." Many of these problems resurface after several months or years for that matter. Having a locked thread benefits no one.

Requesting a thread be locked is a great way to increase one's post count, but hardly beneficial to the cpanel community.

 

[HawkeVIPER]

There was (still might be) a bug in it that would not allow one to compile IMAP with things like GD and mcrypt, for a very long time.
<snip>
Requesting a thread be locked is a great way to increase one's post count, but hardly beneficial to the cpanel community.

There is a bug on RH based boxes, in that if you don't have the php-imap rpm installed, php will not compile with imap selected. Install the rpm, recompile.

That said, brent is right; replying to a year and a half year old post is not helpful and is very poor netiquette.

--HV

 

[myusername]

HawkeVIPER,

Thanks for your contribution, at least it was semi-useful.

Why open a new thread and search the other 15 of them for an answer, when this one is already keyword dense, and primed up for the search function?

With things like IMAP, GD, Mcrypt and others seeded into this thread, it would be a shame to waste.

I suppose I have ruined this thread so far as keywords go. I Never understood the point of starting anew, when many familiar are subscribed, and can answer with a reasonable reply to the topic at hand.

 

[B12Org]

I think people open a new one because once people see that a post has a few posts to it a lot dont bother reading Shame really