Hello, I need php 4 on fedora core 5 ppc (well fc5 is not required but wanted :) ) anyway i followed this site to compile the php4 rpm and it fails. php 5 was removed, all dependencys were installed php4 begins to compile and then fails. I am not at home so can't be more specific but fails on this
rpmbuild --rebuild php-4.3.11-2.8.1.mjm.src.rpm
all the examples are for i386, so my question is whether i should do something differently or in addition to this guide to get it to compile for ppc ?
thanks, chuck
http://www.mjmwired.net/resources/mjm-fedora-php4.html
eh, left that out
On 5/1/06, chuck clark fedoramailinglist@gmail.com wrote:
Hello, I need php 4 on fedora core 5 ppc (well fc5 is not required but wanted :) ) anyway i followed this site to compile the php4 rpm and it fails. php 5 was removed, all dependencys were installed php4 begins to compile and then fails. I am not at home so can't be more specific but fails on this
rpmbuild --rebuild php-4.3.11-2.8.1.mjm.src.rpm
all the examples are for i386, so my question is whether i should do something differently or in addition to this guide to get it to compile for ppc ?
thanks, chuck
On Mon, 2006-05-01 at 11:19 -0500, chuck clark wrote:
Hello, I need php 4 on fedora core 5 ppc (well fc5 is not required but wanted :) ) anyway i followed this site to compile the php4 rpm and it fails. php 5 was removed, all dependencys were installed php4 begins to compile and then fails. I am not at home so can't be more specific but fails on this
rpmbuild --rebuild php-4.3.11-2.8.1.mjm.src.rpm
all the examples are for i386, so my question is whether i should do something differently or in addition to this guide to get it to compile for ppc ?
At what point does it fail? What is the error?
I am sure I am missing something. I prefer to start core 5 by first booting in level 3 and then to gui. I find it interesting that the gui interface does not allow me to shut the computer down in this case but if I allow the computer to boot direct to run level 5 the shut down or reboot option is offered. No particular problem just switch at the command line to either the su or root itself and then shut down. This is where a inconstancy appears. The shutdown process seems to go okay until the end when a sh-3.1# prompt appears, no matter what I do the same situation occurs; it does not seem to matter which switches I use if I want the computer actually turn off or reboot at this stage I need to manually turn the computer off. What is happening? Norm
Norm [norm@workingtools.ca] wrote:
I am sure I am missing something. I prefer to start core 5 by first booting in level 3 and then to gui. I find it interesting that the gui interface does not allow me to shut the computer down in this case but if I allow the computer to boot direct to run level 5 the shut down or reboot option is offered. No particular problem just switch at the command line to either the su or root itself and then shut down. This is where a inconstancy appears. The shutdown process seems to go okay until the end when a sh-3.1# prompt appears, no matter what I do the same situation occurs; it does not seem to matter which switches I use if I want the computer actually turn off or reboot at this stage I need to manually turn the computer off. What is happening? Norm
Either apci is not started or the shutdown is actually running init 1 and bringing you into single-user mode. At a command prompt, use the command ps -ef | grep acpid to see if it is running; if not, as root, chkconfig --add acpid. Otherwise, what shutdown command do you use?
T.
Are you using `shutdown now -h`?
I'd start there and then try to debug any issues.
DP
Norm wrote:
I am sure I am missing something. I prefer to start core 5 by first booting in level 3 and then to gui. I find it interesting that the gui interface does not allow me to shut the computer down in this case but if I allow the computer to boot direct to run level 5 the shut down or reboot option is offered. No particular problem just switch at the command line to either the su or root itself and then shut down. This is where a inconstancy appears. The shutdown process seems to go okay until the end when a sh-3.1# prompt appears, no matter what I do the same situation occurs; it does not seem to matter which switches I use if I want the computer actually turn off or reboot at this stage I need to manually turn the computer off. What is happening? Norm -- This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean.
More confused than ever, before checking testing the shutdown with -h the use of -r did not work properly. -h worked properly and now -r works as well On Mon, 2006-05-01 at 23:46 -0400, David-Paul Niner wrote:
Are you using `shutdown now -h`?
I'd start there and then try to debug any issues.
DP
Norm wrote:
I am sure I am missing something. I prefer to start core 5 by first booting in level 3 and then to gui. I find it interesting that the gui interface does not allow me to shut the computer down in this case but if I allow the computer to boot direct to run level 5 the shut down or reboot option is offered. No particular problem just switch at the command line to either the su or root itself and then shut down. This is where a inconstancy appears. The shutdown process seems to go okay until the end when a sh-3.1# prompt appears, no matter what I do the same situation occurs; it does not seem to matter which switches I use if I want the computer actually turn off or reboot at this stage I need to manually turn the computer off. What is happening? Norm -- This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean.
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
-
chuck clark -
David-Paul Niner -
Michael A. Peters -
Norm -
Thaddeus Nielsen