Mark responded: >I understand that. It is more subtle than that. It has to do with the >Python version that runs the Setup.py for the Korean codecs.
It is getting me really pissed off. As far as I can tell, it is running the 2.5.2 version of Python. I tried --includedir with configure. Didn't help. I tried changing the "Python.h" to <Python.h>. Didn't help. I tried adding the -I to the Korean directory Makefile CFLAGS. Didn't help. With the above Makefile change, I tried changing the "Python.h" to <Python.h>. Didn't help. Why are the actual gcc command lines not visible in the make output? I'm used to seeing the actual command lines so that debugging of a problem is made a little easier. Is there any way to not use the Korean/Japanese stuff and still get mailman to work? MB -- e-mail: [EMAIL PROTECTED] /~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there. Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email ------------------------------------------------------ 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
