|
Brian McCann
Brian.McCann at viziant.net
Wed Apr 4 12:06:41 EDT 2007
Hi Jore, here are all references ro apxs, there was no apxs wit Collabnet, that's why I installed apache2-devel to get it the version of apache that came with the RH install was 2.0.52 and the one with the collabnet install 2.2.3 there is an apxs in /usr/sbin/ but when I run configure pointing to it, I get the output in bold below pointing to apache 2.0.52 not 2.2.3 are you saying that if I can get the apxs associated with apache version 2.2.3(the version CollabNet uses)mod_python will build succcessfully? Thanks, -Brian [root at sirius1 conf]# updatedb [root at sirius1 conf]# locate apxs /usr/share/man/man8/apxs.8.gz /usr/share/man/man8/apxs2.8.gz /usr/sbin/apxs /usr/sbin/apxs2 /var/www/manual/programs/apxs.html.ko.euc-kr /var/www/manual/programs/apxs.html.en /var/www/manual/programs/apxs.html /etc/opt/CollabNet_Subversion/default-site/htdocs/manual/programs/apxs.html /etc/opt/CollabNet_Subversion/default-site/htdocs/manual/programs/apxs.html.ko.euc-kr /etc/opt/CollabNet_Subversion/default-site/htdocs/manual/programs/apxs.html.en [root at sirius1 mod_python-3.3.1]# ./configure --with-python=/usr/bin/python2.3 --with-apxs=/usr/sbin/apxs --with-flex=/usr/bin/flex checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for ar... ar checking for a BSD-compatible install... /usr/bin/install -c checking whether make sets $(MAKE)... yes checking for main in -lm... yes checking for an ANSI C-conforming const... yes checking your blood pressure... a bit high, but we can proceed configure: checking whether apxs is available... checking for --with-apxs... /usr/sbin/apxs executable, good checking Apache version... 2.0.52 checking for Apache libexec directory... /usr/lib/httpd/modules checking for Apache include directory... -I/usr/include/httpd checking for --with-python... /usr/bin/python2.3 checking Python version... 2.3 checking Python install prefix... /usr checking checking where python libraries are installed... /usr/lib/python2.3 checking for Py_NewInterpreter in -lpython2.3... yes checking what libraries Python was linked with... -lpython2.3 -lpthread -ldl -lutil -lm checking linker flags used to link Python... checking where Python include files are... -I/usr/include/python2.3 checking for --with-python-src... no checking for --with-mutex-dir... no Using MUTEX_DIR /tmp checking for --with-max-locks... no Using 8 MAX_LOCKS. checking for --with-flex... /usr/bin/flex found /usr/bin/flex, we'll use this. Use --with-flex to specify another. checking flex version... configure: WARNING: Flex version 2.5.4 found. Version 2.5.31 or greater is required. You can generally ignore this warning unless you need to regenerate psp_parser.c from psp_parse.l. If you do need regenerate psp_parser.c, use --with-flex to specify the location of the correct flex version. See the README for more information. configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating Doc/Makefile config.status: creating src/include/mod_python.h config.status: creating test/Makefile config.status: creating test/testconf.py config.status: creating dist/setup.py config.status: creating dist/Makefile ________________________________ From: Jorey Bump [mailto:list at joreybump.com] Sent: Wed 4/4/2007 11:22 AM To: Brian McCann Cc: mod_python at modpython.org Subject: Re: [mod_python] mod_python install fails Brian McCann wrote: > These are the versions\locations on our server > [root at sirius1 bin]# /opt/CollabNet_Subversion/bin/httpd -V > Server version: Apache/2.2.3 > Server built: Feb 5 2007 13:01:55 > I cp this httpd file to httpd2 and put that file in /etc Why would you do that? > this is what I get now whenI run configure, make, make > install[root at sirius1 mod_python-3.3.1]# ./configure > --with-python=/usr/bin/python2.3 --with-apxs=/usr/sbin/apxs2 > --with-flex=/usr/bin/flex You're still using an apxs that doesn't match your target Apache installation. As root, run the following commands: updatedb locate apxs See if the output shows apxs somewhere within your CollabNet installation. > and the try to restart apache I get this garbled error > [root at sirius1 bin]# apachectl restart > httpd: Syntax error on line 55 of > /etc/opt/CollabNet_Subversion/conf/httpd.conf: API module structure > `python_module' in file /usr/lib/apache2/mod_pyt > hon.so is garbled - perhaps this is not an Apache module DSO? > [root at sirius1 bin]# > > CollabNet did not come with apxs2 so I installe dthe package apache2-devel That will only work for Red Hat's corresponding Apache RPM. Keep in mind that the original upstream Apache httpd distribution doesn't use the names apxs2 or httpd2, a convention used by packagers to support installing Apache httpd versions 1.x and 2.x on the same machine. A vanilla installation of httpd will simply provide apxs and httpd. I have no familiarity with CollabNet, but if they're distributing Apache, they must provide the source, so you will be able to install a working apxs, somehow. They may even supply it as another package. In any case, you should use the apxs that corresponds to your target Apache installation. Once you understand it, the default Apache httpd is flexible and well designed. If CollabNet hasn't crippled it in any way, it should be easy to add functionality like mod_python. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mm_cfg_has_not_been_edited_to_set_host_domains/pipermail/mod_python/attachments/20070404/7bb2485e/attachment.html
|