[MacPorts] #20589: Instructions for port "smokeping" do not cover 10.5

MacPorts noreply at macports.org
Tue Apr 13 13:13:17 PDT 2010


#20589: Instructions for port "smokeping" do not cover 10.5
-------------------------------------+--------------------------------------
  Reporter:  schneider.pj@…          |       Owner:  markd@…           
      Type:  defect                  |      Status:  reopened          
  Priority:  Normal                  |   Milestone:                    
 Component:  ports                   |     Version:  1.7.1             
Resolution:                          |    Keywords:                    
      Port:  smokeping               |  
-------------------------------------+--------------------------------------

Comment(by northnet04@…):

 Replying to [comment:6 markd@…]:
 > The path is ${prefix}/share/doc/speedycgi/mod_speedycgi.so only if you
 use the variant apple_apache.  Then you need to copy it to
 /usr/libexec/apache2.  (I fixed a minor error with the ui_msg just now in
 r66423)  The ui_msg uses an isset_variant keyword to display the right
 ui_msg block.
 >
 > It sounds like you want to use Apple's built-in Apache but didn't use
 the apple_apache variant.  Can you try that and let me know?
 >
 > If you don't use the apple_apache variant, macports apache2 is installed
 and the file is placed in ${prefix}/apache2/modules.


  I'd have to uninstall, clean and run it again to be positive, but I think
 I tried removing macports in its entirety, instlalled, selfupdate, and
 then install smokeping with the +apple_apache variant as the first and
 only 'install' and I still ended up with the module installed under the
 apache2 port. I thought that odd, that it would even install apache when
 I'm telling it I don't need it.

  My stubborn problem with smokeping is the mod_speedycgi.so, as it refuses
 to make properly for my platform. The apple apache2 server pukes due to it
 being the wrong architecture.

  I did do a complete uninstall, clean, install etc., and I ran perl5.8 and
 apache2 with the universal variant specified, then I ran smokeping with
 the apple_apache switch and speedycgi did end up where it was supposed to
 be. However, the mod_speedycgi.so is still not right for my archtitecture.

  I'll do another complete uninstall, clean and install from scratch and
 see where it ends up. Any idea why speedycgi wouldn't be right for my
 platform? I'll run it with -d this time.

 Model Name:     Xserve
   Model Identifier:     Xserve1,1
   Processor Name:       Dual-Core Intel Xeon
   Processor Speed:      2.66 GHz
   Number Of Processors: 2
   Total Number Of Cores:        4
   L2 Cache (per processor):     4 MB
   Memory:       4 GB
   Bus Speed:    1.33 GHz
   Boot ROM Version:     XS11.0080.B01
   SMC Version (system): 1.11f5
   LOM Revision: 1.2.8
   System Version:       Mac OS X Server 10.5.8 (9L34)
   Kernel Version:       Darwin 9.8.0

 Regards,

-- 
Ticket URL: <http://trac.macports.org/ticket/20589#comment:7>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list