Thanks for both responses. Haven't had much time to progress this but got everything built and installed. When running up Apache however, it just hangs when validating configuration. Hang occurs even when run 'apachectl -t' directly.
The only no standard option I selected at any point was to enable threading in APR for Apache build as without that mod_wsgi daemon mode isn't going to work. At least, assumed I should select that. FWIW, running truss on 'httpd -t', it is running, but think it is looping over trying to do some DNS setup. Note that all I have done with the OS installation is to say use DHCP, nothing else. Graham 2010/1/16 mog <[email protected]>: > On 15/01/2010 11:57, Graham Dumpleton wrote: >> >> I have a FreeBSD 7.2 image installed under VmWare and think I have >> ports installed. >> >> How do I install mod_wsgi 2.8/3.1 ports given that they aren't in >> standard ports tree, plus, even the ones at freshports are setup for >> Apache 1.3 and not Apache 2.2. >> >> http://www.freshports.org/www/mod_wsgi/ >> http://www.freshports.org/www/mod_wsgi3/ >> >> I have never installed FreeBSD before or used ports, so good >> instructions for getting Apache 2.2 and newest mod_wsgi versions >> installed from ports appreciated. >> >> Graham >> > > The system I was using to get things working on to begin with runs FreeBSD > 7.2 (amd64), then the machine I built a jail on for a clean testing > environment is running FreeBSD 7.2 (i386). > > First you need to make sure your ports tree is present and up-to-date. For > most people, the best way to do this is using portsnap(8). To run portsnap > for the first time, you need to use the following commands: > > portsnap fetch > portsnap extract > > Naturally the first time portsnap runs, it has quite a lot of work to do, so > it may take a while. Future updates should happen quicker and can be > performed just by issuing the 'portsnap fetch update' command. For more > information on portsnap you may wish to check out the handbook page: > > http://www.freebsd.org/doc/en/books/handbook/portsnap.html > > Once the ports tree is updated, you can start installing things. Personally, > I'm using perl-5.10 at the moment (and Apache will want it) so I like to > install it first to get it out the way. If another port has already > installed a different version, it probably doesn't matter for what you're > doing. > > To install perl I do: > > /usr/ports/lang/perl5.10 && make install clean > > A number of ports will display an Options menu when you go to install them. > This is just a simple list of checkbox options that can allow you to tweak > common configure/build options the port uses in a user-friendly manner. For > most ports you'll usually find that the default Options settings are fine. > > As you'd expect, the ports system will automatically install any > dependencies required by the port you are trying to install, so don't be > surprised if it shows you an Options menu for something else at some point. > > Next you might like to install Python. You can do this like so: > > cd /usr/ports/lang/python26 && make install clean > > Then Apache: > > cd /usr/ports/www/apache22 && make install clean > > Then mod_wsgi 2.x: > > cd /usr/ports/www/mod_wsgi && make install clean > > Or for mod_wsgi 3.x use: > > cd /usr/ports/www/mod_wsgi3 && make install clean > > Note that the ports system (quite sensibly) will not allow you to have both > of these installed at the same time. To install a different version, you > must first remove the version currently installed. For example, you might > remove mod_wsgi like this. > > pkg_info | grep mod_wsgi > mod_wsgi-3.1 Python WSGI adapter module for Apache > > pkg_delete mod_wsgi-3.1 > > The pkg_info(1) command simply generates a list of all currently installed > ports / packages. Then the pkg_delete(1) command will delete whatever port / > package you tell it to. > > Once installed, you'll find your Apache configuration files located in: > > /usr/local/etc/apache22/ > > Note that the mod_wsgi ports will automatically add the LoadModule directive > into your httpd.conf for you. But it always makes sense to check through it > all anyway just in case. > > You can let FreeBSD's rc.d help you manage the starting and stopping of > Apache. Doing these commands as root will also tell Apache to start when > your system boots up: > > echo 'apache22_enable="YES"' >> /etc/rc.conf > echo 'apache22_http_accept_enable="YES"' >> /etc/rc.conf > > And then use the rc.d control script to start Apache: > > /usr/local/etc/rc.d/apache22 start > /usr/local/etc/rc.d/apache22 stop > /usr/local/etc/rc.d/apache22 graceful > etc > Do '/usr/local/etc/rc.d/apache22' with no arguments for a list of available > options. > > Hope that helps. If I've missed anything out or something doesn't make > sense, just give me a shout. > > mog. > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > > >
-- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
