Re: FeeBSD build (was mod_python 3.2.1b available for testing)
Gregory (Grisha) Trubetskoy wrote: Anybody got FreeBSD? I'm getting this. This is an old and possibly misconfigured system, so the problem could be on my end. FreeBSD 4.9 apache 2.0.53 (from ports) python 2.3.3 $ make Compiling for DSO. /usr/local/sbin/apxs -I/home/grisha/src/tmp/mod_python-3.2.1b/src/include -I/usr/local/include/apache2 -I/usr/local/include/python2.3 -c mod_python.c _apachemodule.c requestobject.c tableobject.c util.c serverobject.c connobject.c filterobject.c hlist.c hlistobject.c -Wl,--export-dynamic -pthread -lm /usr/local/lib/python2.3/config/libpython2.3.a-lutil -lm /usr/local/share/apache2/build/libtool --silent --mode=compile cc -prefer-pic -O -pipe -DAP_HAVE_DESIGNATED_INITIALIZER -D_REENTRANT -D_THREAD_SAFE -I/usr/local/include/apache2 -I/usr/local/include/apache2 -I/usr/local/include/apache2 -I/usr/local/include -I/home/grisha/src/tmp/mod_python-3.2.1b/src/include -I/usr/local/include/apache2 -I/usr/local/include/python2.3 -c -o mod_python.lo mod_python.c touch mod_python.slo mod_python.c:34: syntax error before `*' mod_python.c:34: warning: data definition has no type or storage class mod_python.c: In function `python_cleanup': mod_python.c:238: warning: passing arg 1 of `free' discards qualifiers from pointer target type mod_python.c: In function `python_init': mod_python.c:517: `APR_THREAD_MUTEX_UNNESTED' undeclared (first use in this function) mod_python.c:517: (Each undeclared identifier is reported only once mod_python.c:517: for each function it appears in.) apxs:Error: Command failed with rc=65536 . *** Error code 1 Stop in /usr/home/grisha/src/tmp/mod_python-3.2.1b/src. *** Error code 1 Stop in /usr/home/grisha/src/tmp/mod_python-3.2.1b. I don't have FreeBSD, or any experience with any BSD, but I won't let that stop me from commenting. :) I don't see apr-0 listed in your includes in the above output. APR_THREAD_MUTEX_UNNESTED is defined in apr_thread_mutex.h, which on debian is in /usr/include/apr-0/. class ModPyExtension in dist/setup.py.in has been modified somewhat since the last release. This either broke the FreeBSD build or something is indeed misconfigured on your system. Jim
Re: FeeBSD build (was mod_python 3.2.1b available for testing)
On Thu, 8 Sep 2005, Jim Gallacher wrote: I don't have FreeBSD, or any experience with any BSD, but I won't let that stop me from commenting. :) I don't see apr-0 listed in your includes in the above output. APR_THREAD_MUTEX_UNNESTED is defined in apr_thread_mutex.h, which on debian is in /usr/include/apr-0/. class ModPyExtension in dist/setup.py.in has been modified somewhat since the last release. This either broke the FreeBSD build or something is indeed misconfigured on your system. 'cept that ModPyExtension doesn't do anything on non-Win32... all those args come from apxs. I'll see if I can make some time to dig deeper. I'm hoping someone else with FreeBSD access can override my outcome, else this would be a -1... Grisha
Re: FeeBSD build (was mod_python 3.2.1b available for testing)
Gregory (Grisha) Trubetskoy wrote: On Thu, 8 Sep 2005, Jim Gallacher wrote: I don't have FreeBSD, or any experience with any BSD, but I won't let that stop me from commenting. :) I don't see apr-0 listed in your includes in the above output. APR_THREAD_MUTEX_UNNESTED is defined in apr_thread_mutex.h, which on debian is in /usr/include/apr-0/. class ModPyExtension in dist/setup.py.in has been modified somewhat since the last release. This either broke the FreeBSD build or something is indeed misconfigured on your system. 'cept that ModPyExtension doesn't do anything on non-Win32... all those args come from apxs. Right you are. However, I still don't see any reference to include/apr-0/ in your output. For example, on debian the first few lines of the output from make: make[1]: Entering directory `/tmp/mod_python/src' Compiling for DSO. /usr/bin/apxs2 -I/tmp/mod_python/src/include -I/usr/include/apache2 -I/usr/include/python2.3 -c mod_python.c _apachemodule.c requestobject.c tableobject.c util.c serverobject.c connobject.c filterobject.c hlist.c hlistobject.c -L/usr/lib/python2.3/config -Xlinker -export-dynamic -lm -lpython2.3 -lpthread -ldl -lutil -lm /usr/bin/libtool --silent --mode=compile gcc -prefer-pic -pipe -I/usr/include/xmltok -I/usr/include/openssl -Wall -O2 -DAP_HAVE_DESIGNATED_INITIALIZER -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -pipe -I/usr/include/xmltok -I/usr/include/openssl -Wall -O2 -pthread -I/usr/include/apache2 -I/usr/include/apr-0 -I/usr/include/apr-0 -I/usr/include -I/tmp/mod_python/src/include -I/usr/include/apache2 -I/usr/include/python2.3 -c -o mod_python.lo mod_python.c touch mod_python.slo I assume that apxs calls libtool, and provides the -I/usr/include/apr-0 parameter, yet I didn't see that in your output. I don't know if that is significant, just that it's different on the 2 systems. Jim
