Vidiot wrote: >I'm not sure that everyone looked at the posting that I did very clearly. >The error I posted is totally different that the error discussed in this >posting: > >http://mail.python.org/pipermail/mailman-users/2007-February/055640.html > >That was a result of the install "finding" the Sun installed python. That is >not my problem. To wit, here is the python greps out of the configure log: > > configure:1311: checking for --with-python > configure:1330: checking for python > configure:1348: found /usr/local/bin/python > configure:1361: result: /usr/local/bin/python > configure:1370: checking Python interpreter > configure:1388: result: /usr/local/bin/python > configure:1393: checking Python version > configure:1434: checking that Python has a working distutils > ac_cv_path_with_python=/usr/local/bin/python > PYTHON='/usr/local/bin/python' > with_python='/usr/local/bin/python' > >As can be seen, the local version was found in all cases. > >Take a look at the make output again: > > (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib > /usr/local/bin/python setup.py --quiet install --install-lib > /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib > --install-data /usr/local/mailman/pythonlib); \ >done >/usr/local/lib/python2.5/distutils/dist.py:247: UserWarning: 'licence' >distribution option is deprecated; use 'license' > warnings.warn(msg) >src/hangul.c:33: error: syntax error before numeric constant >src/hangul.c:34: error: syntax error before numeric constant >error: command 'gcc' failed with exit status 1 >*** Error code 1 >make: Fatal error: Command failed for target `install-packages' >Current working directory /usr/local/src/mailman-2.1.11rc2/misc > >Notice that the correct python is being used. It isn't python that is bailing, >it is gcc.
The Korean and Japanese codecs are installed by Python distutils using a setup.py built somewhere else. It doesn't get everything from configure. Your problem is the hangul.c file that is not compiling contains #include "Python.h" (and Python.h inturn includes a bunch of other stuff) gcc is not finding this header file. That is the underlying cause of the compile error. Yes, the error in your case is different, because in your case the compile is finding a working compiler, but the root problem is the same. I confess, I don't fully understand the details, but Hank appears to and he says the issue is with the order of things on your PATH. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
