Skip to main content
Participant
April 8, 2008
Question

cannot launch CF8 update1 on leopard

  • April 8, 2008
  • 2 replies
  • 811 views
Clean install of CF8 update 1 on Leopard. Trying to get it to work with the Apache version already installed with OSX 10.5.2. Once installer is done the installer gives a message that the coldfusion service is not running, the web server connectors did not install successfully etc etc. I made sure that the apache connectors were set as described in the installation guide. Trying to launch the service from the terminal also fails.

The cfserverlog has the follwing entries:
/Applications/Coldfusion8/bin/coldfusion: line 59: /Applications/ColdFusion8/runtime/bin/coldfusion8: Bad CPU type in executable

I have spend a whole day trying every possible combination on the CF installer with the same results. Very disappointing since we have been waiting for the "leopard" CF version to come around and yet same issues as before.

Any help would be greatly appreciated.

Thanks
This topic has been closed for replies.

2 replies

April 11, 2008
Hi, just chucking in that I installed CF 8.0.1. on OS X 10.5.2 Leopard (not server) for development, but will be using the internal server (8500), runs great and it was easy to install.
Participant
April 11, 2008
Thanks for everyones input.
I was able to install CF 8.0 (not update 1) on OSX 10.5.2 on top of a MAMP installation for running Apache. At some point I will try to install CF 8.01 on this configuration and see if it works.
Participating Frequently
April 9, 2008
Hi,

Are you trying on a ppc based machine? CF8.0.1 does not support leopard on ppc bases macs.

Thanks,
Hemant
Participant
April 9, 2008
Thanks for the reply.
No this is an intel based macbook pro (2 GHz Intel core Duo)
Participating Frequently
April 9, 2008
Have you run any programs (such as monolingual) at any time that strip the PPC code out of all your applications?

Just guessing at this point. I have it running fine on a 2.4 GHz Core 2 Duo Macbook Pro. The only other guess I have is maybe it has to do with the Core Duo -> Core 2 Duo difference...