I want to be able to recompile php, so I downloaded the src dvd and did a
rpm -i php-4.3.9-3.15.src.rpm
After doing that I wanted to check to see if I can recompile it before making changes. So, I went to the SPECS dir and did a
rpmbuild -i php.spec
It spent a lot of time doing the compile, but at the end there were errors.
What am I missing?
Todd
On Fri, Jan 12, 2007 at 07:18:59AM -0800, Todd Cary enlightened us:
I want to be able to recompile php, so I downloaded the src dvd and did a
rpm -i php-4.3.9-3.15.src.rpm
After doing that I wanted to check to see if I can recompile it before making changes. So, I went to the SPECS dir and did a
rpmbuild -i php.spec
It spent a lot of time doing the compile, but at the end there were errors.
What am I missing?
Telling us what the errors were, for starters.
Matt
Matt -
I did rpmbuild -ba php.spec 2> /tmp/build_errors.txt
The build_errors.txt file is quite large, so I am not sure if I should sent it as an attachment. Here are the last few lines:
cpio: php-4.3.9/ext/standard/<stdout>: No such file or directory 18492 blocks + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + umask 022 + cd /usr/src/redhat/BUILD + cd php-4.3.9 + cd build-cgi + export NO_INTERACTION=1 REPORT_EXIT_STATUS=1 MALLOC_CHECK_=2 + NO_INTERACTION=1 + REPORT_EXIT_STATUS=1 + MALLOC_CHECK_=2 + unset TZ LANG LC_ALL + make test make: *** [test] Error 1 + set +x error: Bad exit status from /var/tmp/rpm-tmp.36559 (%check) Bad exit status from /var/tmp/rpm-tmp.36559 (%check)
Matt Hyclak wrote:
On Fri, Jan 12, 2007 at 07:18:59AM -0800, Todd Cary enlightened us:
I want to be able to recompile php, so I downloaded the src dvd and did a
rpm -i php-4.3.9-3.15.src.rpm
After doing that I wanted to check to see if I can recompile it before making changes. So, I went to the SPECS dir and did a
rpmbuild -i php.spec
It spent a lot of time doing the compile, but at the end there were errors.
What am I missing?
Telling us what the errors were, for starters.
Matt
On Fri, Jan 12, 2007 at 08:17:59AM -0800, Todd Cary enlightened us:
Matt -
I did rpmbuild -ba php.spec 2> /tmp/build_errors.txt
The build_errors.txt file is quite large, so I am not sure if I should sent it as an attachment. Here are the last few lines:
cpio: php-4.3.9/ext/standard/<stdout>: No such file or directory 18492 blocks
- /usr/lib/rpm/redhat/brp-compress
- /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
- /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
- umask 022
- cd /usr/src/redhat/BUILD
- cd php-4.3.9
- cd build-cgi
- export NO_INTERACTION=1 REPORT_EXIT_STATUS=1 MALLOC_CHECK_=2
- NO_INTERACTION=1
- REPORT_EXIT_STATUS=1
- MALLOC_CHECK_=2
- unset TZ LANG LC_ALL
- make test
make: *** [test] Error 1
- set +x
error: Bad exit status from /var/tmp/rpm-tmp.36559 (%check) Bad exit status from /var/tmp/rpm-tmp.36559 (%check)
Tough to tell from that. Can you post the entire log somewhere and send a URL to the list?
Matt
Matt -
Try this: http://209.204.172.137/misc/build_errors.txt
Would it help to pipe the complete build process to a file?
Todd
Matt Hyclak wrote:
On Fri, Jan 12, 2007 at 08:17:59AM -0800, Todd Cary enlightened us:
Matt -
I did rpmbuild -ba php.spec 2> /tmp/build_errors.txt
The build_errors.txt file is quite large, so I am not sure if I should sent it as an attachment. Here are the last few lines:
cpio: php-4.3.9/ext/standard/<stdout>: No such file or directory 18492 blocks
- /usr/lib/rpm/redhat/brp-compress
- /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
- /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
- umask 022
- cd /usr/src/redhat/BUILD
- cd php-4.3.9
- cd build-cgi
- export NO_INTERACTION=1 REPORT_EXIT_STATUS=1 MALLOC_CHECK_=2
- NO_INTERACTION=1
- REPORT_EXIT_STATUS=1
- MALLOC_CHECK_=2
- unset TZ LANG LC_ALL
- make test
make: *** [test] Error 1
- set +x
error: Bad exit status from /var/tmp/rpm-tmp.36559 (%check) Bad exit status from /var/tmp/rpm-tmp.36559 (%check)
Tough to tell from that. Can you post the entire log somewhere and send a URL to the list?
Matt
On Fri, Jan 12, 2007 at 08:33:36AM -0800, Todd Cary enlightened us:
Matt -
Try this: http://209.204.172.137/misc/build_errors.txt
Would it help to pipe the complete build process to a file?
Might. It's obviously dying in the %check stanza of the .spec file, so you might look there and see what it's trying to do that would be failing. Is SELinux enabled on the build system, perhaps? I think that can do weird things sometimes.
Matt
Matt -
I have the spec, build and error file on my server:
http://209.204.172.137/misc/php.spec http://209.204.172.137/misc/build.txt http://209.204.172.137/misc/build_errors.txt
Todd
Matt Hyclak wrote:
On Fri, Jan 12, 2007 at 08:33:36AM -0800, Todd Cary enlightened us:
Matt -
Try this: http://209.204.172.137/misc/build_errors.txt
Would it help to pipe the complete build process to a file?
Might. It's obviously dying in the %check stanza of the .spec file, so you might look there and see what it's trying to do that would be failing. Is SELinux enabled on the build system, perhaps? I think that can do weird things sometimes.
Matt
Quoting Todd Cary todd@aristesoftware.com:
Matt -
I have the spec, build and error file on my server:
http://209.204.172.137/misc/php.spec http://209.204.172.137/misc/build.txt http://209.204.172.137/misc/build_errors.txt
If you look at the output, it seems that the two testes failed (bug26938 and proc_open01). They did not fail because the things they were testing were not working. They failed because interbase.so module couldn't be found (tests didn't even run). Maybe they depend on interbase module for whatever strange reason. If I were you, I'd just edit the spec file and remove them. In the %prep section, just after patches are applied, thre's couple of lines that remove some other tests that fail for no good reason (preventing php rpm from being built).
Just add these two lines inthere, and you should be fine:
rm -f ext/standard/tests/file/bug26938.phpt rm -f ext/standard/tests/file/proc_open01.phpt
If you customize spec file to build more modules, some other tests may also fail (again, usually for no good reason). Check output for details. It tells you why test failed. If it's just linking problem (like with those two tests that are bugging you now), ignore it and disable the test in spec file (by removing it in %prep section).
rpmbuild -i php.spec
try , instead, rpmbuild -ba php.spec
On 1/12/07, Aleksandar Milivojevic alex@milivojevic.org wrote:
Quoting Todd Cary todd@aristesoftware.com:
Matt -
I have the spec, build and error file on my server:
http://209.204.172.137/misc/php.spec http://209.204.172.137/misc/build.txt http://209.204.172.137/misc/build_errors.txt
If you look at the output, it seems that the two testes failed (bug26938 and proc_open01). They did not fail because the things they were testing were not working. They failed because interbase.so module couldn't be found (tests didn't even run). Maybe they depend on interbase module for whatever strange reason. If I were you, I'd just edit the spec file and remove them. In the %prep section, just after patches are applied, thre's couple of lines that remove some other tests that fail for no good reason (preventing php rpm from being built).
Just add these two lines inthere, and you should be fine:
rm -f ext/standard/tests/file/bug26938.phpt rm -f ext/standard/tests/file/proc_open01.phpt
If you customize spec file to build more modules, some other tests may also fail (again, usually for no good reason). Check output for details. It tells you why test failed. If it's just linking problem (like with those two tests that are bugging you now), ignore it and disable the test in spec file (by removing it in %prep section).
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Aleksandar -
Thank you! I forgot that I had created an interbase.so file by compiling another version of php (tared). Who knows where and what that did! So, I reinstalled Centos (I am just setting this server up, so it was no big deal). I was able to recompile the source without a problem.
NOW, I am going to take the same src.rpm and add the Interbase to it with a higher build number (e.g. -rtc.1) and see what happens.
Todd
Aleksandar Milivojevic wrote:
Quoting Todd Cary todd@aristesoftware.com:
Matt -
I have the spec, build and error file on my server:
http://209.204.172.137/misc/php.spec http://209.204.172.137/misc/build.txt http://209.204.172.137/misc/build_errors.txt
If you look at the output, it seems that the two testes failed (bug26938 and proc_open01). They did not fail because the things they were testing were not working. They failed because interbase.so module couldn't be found (tests didn't even run). Maybe they depend on interbase module for whatever strange reason. If I were you, I'd just edit the spec file and remove them. In the %prep section, just after patches are applied, thre's couple of lines that remove some other tests that fail for no good reason (preventing php rpm from being built).
Just add these two lines inthere, and you should be fine:
rm -f ext/standard/tests/file/bug26938.phpt rm -f ext/standard/tests/file/proc_open01.phpt
If you customize spec file to build more modules, some other tests may also fail (again, usually for no good reason). Check output for details. It tells you why test failed. If it's just linking problem (like with those two tests that are bugging you now), ignore it and disable the test in spec file (by removing it in %prep section).
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I added one line to the configuration in php.spec (--with-interbase=shared,/opt/firebird) and now I get the error that it cannot find libphp4.so, however libphp4.so is in /usr/lib/httpd/modules/
Is there some directive missing in the spec file?
http://209.204.172.137/misc/build.txt http://209.204.172.137/misc/build_errors.txt http://209.204.172.137/misc/php.spec
Todd
Todd Cary wrote:
Aleksandar -
Thank you! I forgot that I had created an interbase.so file by compiling another version of php (tared). Who knows where and what that did! So, I reinstalled Centos (I am just setting this server up, so it was no big deal). I was able to recompile the source without a problem.
NOW, I am going to take the same src.rpm and add the Interbase to it with a higher build number (e.g. -rtc.1) and see what happens.
Todd
Aleksandar Milivojevic wrote:
Quoting Todd Cary todd@aristesoftware.com:
Matt -
I have the spec, build and error file on my server:
http://209.204.172.137/misc/php.spec http://209.204.172.137/misc/build.txt http://209.204.172.137/misc/build_errors.txt
If you look at the output, it seems that the two testes failed (bug26938 and proc_open01). They did not fail because the things they were testing were not working. They failed because interbase.so module couldn't be found (tests didn't even run). Maybe they depend on interbase module for whatever strange reason. If I were you, I'd just edit the spec file and remove them. In the %prep section, just after patches are applied, thre's couple of lines that remove some other tests that fail for no good reason (preventing php rpm from being built).
Just add these two lines inthere, and you should be fine:
rm -f ext/standard/tests/file/bug26938.phpt rm -f ext/standard/tests/file/proc_open01.phpt
If you customize spec file to build more modules, some other tests may also fail (again, usually for no good reason). Check output for details. It tells you why test failed. If it's just linking problem (like with those two tests that are bugging you now), ignore it and disable the test in spec file (by removing it in %prep section).
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
first things first do you have the right libary installed. looks like your missing the libphp.so file.
You could also have a compatibilty problem with you version installed.
I added one line to the configuration in php.spec (--with-interbase=shared,/opt/firebird) and now I get the error that it cannot find libphp4.so, however libphp4.so is in /usr/lib/httpd/modules/
Is there some directive missing in the spec file?
http://209.204.172.137/misc/build.txt http://209.204.172.137/misc/build_errors.txt http://209.204.172.137/misc/php.spec
Todd
Todd Cary wrote:
Aleksandar -
Thank you! I forgot that I had created an interbase.so file by compiling another version of php (tared). Who knows where and what that did! So, I reinstalled Centos (I am just setting this server up, so it was no big deal). I was able to recompile the source without a problem.
NOW, I am going to take the same src.rpm and add the Interbase to it with a higher build number (e.g. -rtc.1) and see what happens.
Todd
Aleksandar Milivojevic wrote:
Quoting Todd Cary todd@aristesoftware.com:
Matt -
I have the spec, build and error file on my server:
http://209.204.172.137/misc/php.spec http://209.204.172.137/misc/build.txt http://209.204.172.137/misc/build_errors.txt
If you look at the output, it seems that the two testes failed (bug26938 and proc_open01). They did not fail because the things they were testing were not working. They failed because interbase.so module couldn't be found (tests didn't even run). Maybe they depend on interbase module for whatever strange reason. If I were you, I'd just edit the spec file and remove them. In the %prep section, just after patches are applied, thre's couple of lines that remove some other tests that fail for no good reason (preventing php rpm from being built).
Just add these two lines inthere, and you should be fine:
rm -f ext/standard/tests/file/bug26938.phpt rm -f ext/standard/tests/file/proc_open01.phpt
If you customize spec file to build more modules, some other tests may also fail (again, usually for no good reason). Check output for details. It tells you why test failed. If it's just linking problem (like with those two tests that are bugging you now), ignore it and disable the test in spec file (by removing it in %prep section).
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software 2200 D Street Ext Petaluma, CA 94952 (707) 773-4523
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Brent -
Check out my message "[CentOS] Problem with rpmbuild - this works". I seem to have found a way around the problem, but I am not experienced enough with Linux, especially with creating executables ad RPM's, to know exactly why it works. Nevertheless, I now have an RPM based (I assume that it is since I used the src.rpm) version of PHP that has Interbase integrated.
Todd
Brent wrote:
first things first do you have the right libary installed. looks like your missing the libphp.so file.
You could also have a compatibilty problem with you version installed.
I added one line to the configuration in php.spec (--with-interbase=shared,/opt/firebird) and now I get the error that it cannot find libphp4.so, however libphp4.so is in /usr/lib/httpd/modules/
Is there some directive missing in the spec file?
http://209.204.172.137/misc/build.txt http://209.204.172.137/misc/build_errors.txt http://209.204.172.137/misc/php.spec
Todd
Todd Cary wrote:
Aleksandar -
Thank you! I forgot that I had created an interbase.so file by compiling another version of php (tared). Who knows where and what that did! So, I reinstalled Centos (I am just setting this server up, so it was no big deal). I was able to recompile the source without a problem.
NOW, I am going to take the same src.rpm and add the Interbase to it with a higher build number (e.g. -rtc.1) and see what happens.
Todd
Aleksandar Milivojevic wrote:
Quoting Todd Cary todd@aristesoftware.com:
Matt -
I have the spec, build and error file on my server:
http://209.204.172.137/misc/php.spec http://209.204.172.137/misc/build.txt http://209.204.172.137/misc/build_errors.txt
If you look at the output, it seems that the two testes failed (bug26938 and proc_open01). They did not fail because the things they were testing were not working. They failed because interbase.so module couldn't be found (tests didn't even run). Maybe they depend on interbase module for whatever strange reason. If I were you, I'd just edit the spec file and remove them. In the %prep section, just after patches are applied, thre's couple of lines that remove some other tests that fail for no good reason (preventing php rpm from being built).
Just add these two lines inthere, and you should be fine:
rm -f ext/standard/tests/file/bug26938.phpt rm -f ext/standard/tests/file/proc_open01.phpt
If you customize spec file to build more modules, some other tests may also fail (again, usually for no good reason). Check output for details. It tells you why test failed. If it's just linking problem (like with those two tests that are bugging you now), ignore it and disable the test in spec file (by removing it in %prep section).
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software 2200 D Street Ext Petaluma, CA 94952 (707) 773-4523
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Quoting Todd Cary todd@aristesoftware.com:
Try this: http://209.204.172.137/misc/build_errors.txt
Would it help to pipe the complete build process to a file?
It would. Then you'd see where exactly failed in make test.
BTW, the "make test" in PHP package is as broken as it can get, in my experience. If you look into the spec file, it gets rid of bunch of tests anyhow. I know that I changed spec file to disable whole bunch of additional tests to be able to rebuild PHP package. They simply fail aborting the build (there was nothing wrong with the build, BTW).
You could also go simple route, and disable "make test" completely.
On Friday 12 January 2007 16:18, Todd Cary wrote:
rpmbuild -i php.spec
My rpmbuild doesn't have the option -i. If you just want to build the binary package I suggest "rpmbuild -bb php.spec"
/Peter
It spent a lot of time doing the compile, but at the end there were errors.
What am I missing?
to post the actual errors?
Peter -
Whooops! You are correct! rpmbuild -ba php.spec
I will try that... :-[
Todd
Peter Kjellstrom wrote:
On Friday 12 January 2007 16:18, Todd Cary wrote:
rpmbuild -i php.spec
My rpmbuild doesn't have the option -i. If you just want to build the binary package I suggest "rpmbuild -bb php.spec"
/Peter
It spent a lot of time doing the compile, but at the end there were errors.
What am I missing?
to post the actual errors?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I finally got a version of PHP with Interbase included, but I am not sure why it works versus using rpmbuild. Here is what I did:
Using the php-4.3.9-3.15.src.rpm and running
# rpm -i php.4.3.9-3.15.src.rpm
I now have php-4.3.9.tar.gz in /usr/src/redhat/SOURCES. This is copied to /tmp and untarred. Moving to php.4.3.9-3, I run
# ./configure -with-interbase=shared,/opt/firebird
After a # make, I have interbase.so in the modules directory. This is copied to /usr/lib/php4 and I create a interbase.ini file in /etc/php.d that has a line, "include=interbase.so".
That is it...long way around, but gosh darn, it works!!! Honestly, I am not sure of exactly what I did (at least I am not able to translate everything into what I do daily with Windoz and Delphi). I am sure some C++ experience would help me.
Todd
Todd Cary wrote:
I want to be able to recompile php, so I downloaded the src dvd and did a
rpm -i php-4.3.9-3.15.src.rpm
After doing that I wanted to check to see if I can recompile it before making changes. So, I went to the SPECS dir and did a
rpmbuild -i php.spec
It spent a lot of time doing the compile, but at the end there were errors.
What am I missing?
Todd
-
Aleksandar Milivojevic -
Brent -
Indunil Jayasooriya -
Matt Hyclak -
Peter Kjellstrom -
Todd Cary