Page 1 of 1

Rebuild PHP 5.3.8 - MD5 sum mismatch

Posted: Wed Sep 28, 2011 12:50 pm
by jas8522
I'm trying to do a straight recompile (with no patches or anything else applied) of the 5.3.8 release. I need to do this in order to allow for higher file descriptor limits. So far I have recompiled all srpms necessary according to Parallels here: http://kb.parallels.com/article_41_260_en.html

But once I reach the last step and attempt to recompile and reinstall PHP, I get:
error: unpacking of archive failed on file /usr/src/redhat/SOURCES/macros.php;4e834e03: cpio: MD5 sum mismatch
Using:

Code: Select all

rpmbuild --rebuild php-5.3.8-1.art.src.rpm
Is there a simple way to fix this and complete the recompile?

I'm doing this on 32-bit CentOS 5.7 (Final)

Thanks!

Jordan

Re: Rebuild PHP 5.3.8 - MD5 sum mismatch

Posted: Wed Sep 28, 2011 2:57 pm
by scott
you wont be able to --rebuild that, you'll need to install it with --nomd5 and then build it -ba

Re: Rebuild PHP 5.3.8 - MD5 sum mismatch

Posted: Mon Oct 03, 2011 7:29 am
by jas8522
Thanks Scott. I'll be sure to do it that way if I wind up needing to do this again. Turns out the problem that triggered my need to recompile may not actually be a file descriptor limit issue, so rebuilding PHP may not be necessary after all. The actual problem I'm encountering is the one with the http authenticaton bug in apr.

Just in case this winds up being related to file descriptor limits after all, can you tell me if the systems you're building your binaries on are using system defaults for file descriptors (1024) or an increased amount? I can't recall for sure, but I thought you mentioned you were using 4096 as the file descriptor limit a while back.

I find it a bit ridiculous that an enterprise OS has such low limits to start with. After all, of all operating systems, shouldn't an enterprise OS be configured to handle high resource requirements? Not your fault, for sure, just something that always puzzled me.

Thanks,

Jordan

Re: Rebuild PHP 5.3.8 - MD5 sum mismatch

Posted: Sun Oct 09, 2011 10:08 am
by scott
Its a memory use & optimization thing. The vast majority of users out there would never run into this, so redhat opt'd for the biggest benefit approach.

The only packages that would really be effected by this are httpd and openssl. httpd is the only thing built here (in the -testing channel). Its using the default of 1024 currently.