[Mailman-Users] Mailman complie errors again
msapiro at value.net
Sat Dec 10 06:23:14 CET 2005
Carl Zwanzig wrote:
>In a flurry of recycled electrons, Elvis Fernandes wrote:
>> I am compiling mailman-2.1.5 on Solaris10 (SPARC) with gcc 3.3.2
>> When I do make install, I get the following fatal error:
>Mailman compiles itself. Are you compiling -python-? (That's what it looks
>like.) Sort of out of scope for this list, but you might want to take a
>> /usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t"
>> /usr/include/sys/siginfo.h:437: error: parse error before '}' token
>> In file included from /usr/include/sys/procset.h:24,
>> from /usr/include/sys/wait.h:25,
>> from /usr/include/stdlib.h:22,
>> from /usr/local/include/python2.4/Python.h:39,
>> from src/_japanese_codecs.c:12:
Actually, this comes from the installation of the japanese codecs in
mailman. The src/_japanese_codecs.c file is in the Mailman 2.1.5
distribution in the misc/JapaneseCodecs-1.4.10 directory.
This is one of several compilations of c programs/modules in the
Mailman make install process.
Note however that Mailman 2.1.5 is not fully compatible with Python
2.4. I don't know if it would fix this problen, but if you're running
Python 2.4 (or even if you're not) you would do well to install
Mailman 2.1.6 or later.
I see from a later post, Elvis 'fixed' the problem by falling back to
Solaris 8. It's hard to say what's really going on in the case that
fails, but it looks like there is some compatibility issue between the
header files in /usr/include/sys/ and gcc 3.3.2 on Solaris 10.
Presumably, the Python header file
/usr/local/include/python2.4/Python.h is included in many Python
modules and thus this whole include path was exercised during the
original compile of Python for Solaris 10 (maybe with some other c
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users