Re: [Mailman-Users] Where's Korea? (recurring problem)
Ashley M. Kirchner wrote:
Mark Sapiro wrote:
It looks like the
#include Python.h
near the beginning of _koco.c is failing. Is there a python2.4 directory
in /usr/include?
That was it. python-devel was not installed on this machine. Would
be nice if the configure script checked for all the necessary header
files prior to compiling/installing.
In off list communication, we discovered that the RedHat FC5 'python'
package contains a full distutils module, but does not contain the
necessary header files for compiling/installing Python packages with C
language extensions.
A patch to configure.in (which is processed by autoconf to make
configure) which makes configure test explicitly for the header files
is attached and will be included in Mailman 2.1.10.
It installed now...though the
bazillion errors were still there:
src/_koco_uhc.h:3008: warning: pointer targets in initialization differ
in signedness
src/_koco_uhc.h:3008: warning: pointer targets in initialization differ
in signedness
src/_koco_uhc.h:3008: warning: pointer targets in initialization differ
in signedness
snip
I was able to duplicate these warnings by giving the -pedantic option
to gcc. They are not fatal, and the installed korean codecs will still
work.
Also, the configure in Mailman 2.1.10 will have a great deal more in it
than the ones in 2.1.9 and previous versions. This is not because of
any configure.in changes, but rather because it is generated with
autoconf 2.59 which adds a bunch more stuff than autoconf 2.13 (which
generated the Mailman 2.1.9 configure) did.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
=== modified file 'configure.in'
--- configure.in2006-12-29 21:56:04 +
+++ configure.in2007-09-21 22:12:14 +
@@ -1,4 +1,4 @@
-# Copyright (C) 1998-2006 by the Free Software Foundation, Inc.
+# Copyright (C) 1998-2007 by the Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
@@ -101,7 +101,14 @@
except distutils.errors.DistutilsPlatformError:
res = no
else:
-res = yes
+# some RedHat packages put distutils in python, but the C headers
+# are in python-devel so check for headers too.
+import os.path
+pdothpath = distutils.sysconfig.get_config_var('CONFINCLUDEPY')
+if os.path.isfile(os.path.join(pdothpath, Python.h)):
+res = yes
+else:
+res = no
fp = open(conftest.out, w)
fp.write(%s\n % res)
fp.close()
@@ -117,7 +124,8 @@
* Distutils is not available or is incomplete for $PYTHON
* If you installed Python from RPM (or other package manager)
* be sure to install the -devel package, or install Python
-* from source. See README.LINUX for details])
+* from source. See sec. 15.1 of the Installation Manual for
+* details])
fi
AC_MSG_RESULT($havedistutils)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Where's Korea? (recurring problem)
Mark Sapiro wrote: I don't see these here. Perhaps it's some difference between gcc versions or configurations. Would you like to see a full log of the compile, maybe that'll shed some light? -- A -- W | It's not a bug - it's an undocumented feature. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Imaging . 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Where's Korea? (recurring problem)
Ashley M. Kirchner wrote: Mark Sapiro wrote: I don't see these here. Perhaps it's some difference between gcc versions or configurations. Would you like to see a full log of the compile, maybe that'll shed some light? You could send me the compile log off list. I think I understand what all the warnings are about, and I also think that the results of the compilation would actually work despite the warnings, but the log may be interesting. What I am more interested in is why configure succeeded when you didn't have the python-devel package installed. There are tests in configure for the presence of a full distutils package which should identify a missing python-devel. See the configure script around lines 1432-1475 and the corresponding results in config.log. Possibly, your packages are split differently with distutils in the python package, but the header files in the python-devel package, but this doesn't seem like good packaging. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Where's Korea? (recurring problem)
Mark Sapiro wrote: It looks like the #include Python.h near the beginning of _koco.c is failing. Is there a python2.4 directory in /usr/include? That was it. python-devel was not installed on this machine. Would be nice if the configure script checked for all the necessary header files prior to compiling/installing. It installed now...though the bazillion errors were still there: src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3009: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3009: warning: pointer targets in initialization differ in signedness In file included from src/_koco.c:121: src/euckr_codec.h: In function ‘euc_kr_encode’: src/euckr_codec.h:127: warning: format ‘%04x’ expects type ‘unsigned int’, but argument 3 has type ‘Py_UNICODE’ In file included from src/_koco.c:122: src/cp949_codec.h: In function ‘cp949_encode’: src/cp949_codec.h:151: warning: format ‘%04x’ expects type ‘unsigned int’, but argument 3 has type ‘Py_UNICODE’ In file included from src/_koco.c:123: src/koco_stream.h: In function ‘__euc_kr_decode’: src/koco_stream.h:42: warning: pointer targets in assignment differ in signedness src/koco_stream.h:43: warning: pointer targets in assignment differ in signedness src/koco_stream.h: In function ‘__cp949_decode’: src/koco_stream.h:135: warning: pointer targets in assignment differ in signedness src/koco_stream.h:136: warning: pointer targets in assignment differ in signedness -- H | It's not a bug - it's an undocumented feature. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Imaging . 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Where's Korea? (recurring problem)
Ashley M. Kirchner wrote: Mark Sapiro wrote: It looks like the #include Python.h near the beginning of _koco.c is failing. Is there a python2.4 directory in /usr/include? That was it. python-devel was not installed on this machine. Would be nice if the configure script checked for all the necessary header files prior to compiling/installing. You're right. I'll look into that. It installed now...though the bazillion errors were still there: I don't see these here. Perhaps it's some difference between gcc versions or configurations. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Where's Korea? (recurring problem)
This seems to be a recurring problem, based on a Google search: No module named korean. I'm moving lists from one server running Mailman 2.1.9 to another server. I picked one list domain to move and test, so I grabbed the 'archives', 'data', 'lists', 'logs' and 'qfiles' folders and moved them over to the new server. Paths are all identical. Next I untarred Mailman 2.1.9, run configure and hit make...it ran till it hit the following: Compiling /home/mailman/lists.pcraft.net/Mailman/i18n.py ... Compiling /home/mailman/lists.pcraft.net/Mailman/mm_cfg.py ... Compiling /home/mailman/lists.pcraft.net/Mailman/versions.py ... Traceback (most recent call last): File bin/update, line 46, in ? import paths File /home/mailman/lists.pcraft.net/bin/paths.py, line 60, in ? import korean ImportError: No module named korean make: *** [update] Error 1 Looking in /pythonlib/ I only see an 'email' folder, nothing else. The system is running FC5 with Python 2.4.3. -- W | It's not a bug - it's an undocumented feature. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Imaging . 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Where's Korea? (recurring problem)
Ashley M. Kirchner wrote: I'm moving lists from one server running Mailman 2.1.9 to another server. I picked one list domain to move and test, so I grabbed the 'archives', 'data', 'lists', 'logs' and 'qfiles' folders and moved them over to the new server. Paths are all identical. Next I untarred Mailman 2.1.9, run configure and hit make...it ran till it hit the following: Compiling /home/mailman/lists.pcraft.net/Mailman/i18n.py ... Compiling /home/mailman/lists.pcraft.net/Mailman/mm_cfg.py ... Compiling /home/mailman/lists.pcraft.net/Mailman/versions.py ... Traceback (most recent call last): File bin/update, line 46, in ? import paths File /home/mailman/lists.pcraft.net/bin/paths.py, line 60, in ? import korean ImportError: No module named korean make: *** [update] Error 1 Presumably, this is from make install and not just make Looking in /pythonlib/ I only see an 'email' folder, nothing else. What is in the misc/ directory of the untarred distribution. In particular are all of JapaneseCodecs-1.4.11.tar.gz, KoreanCodecs-2.0.5.tar.gz and email-2.5.8.tar.gz there. Note that they must be the *.gz files because that's what the makefile looks for. Does misc/Makefile contain EMAILPKG= email-2.5.8 JACODECSPKG=JapaneseCodecs-1.4.11 KOCODECSPKG=KoreanCodecs-2.0.5 PACKAGES= $(EMAILPKG) $(JACODECSPKG) $(KOCODECSPKG) and install-packages: for p in $(PACKAGES); \ do \ gunzip -c $(srcdir)/$$p.tar.gz | (cd $(PKGDIR) ; tar xf -); \ (cd $(PKGDIR)/$$p ; umask 02 ; PYTHONPATH=$(PYTHONLIBDIR) $(PYTHON) $(SETUPCMD)); \ done (allowing for folded lines above)? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Where's Korea? (recurring problem)
Mark Sapiro wrote: Presumably, this is from make install and not just make Sorry, you're correct. What is in the misc/ directory of the untarred distribution. $ ls -l misc total 1728 drwxr-xr-x 2 mailman mailman 4096 Sep 14 20:28 ./ drwxr-xr-x 14 mailman mailman 4096 Sep 14 20:28 ../ -rw-r--r-- 1 mailman mailman 1139795 Jul 25 2006 email-2.5.8.tar.gz -rw-r--r-- 1 mailman mailman 3049 Dec 7 2000 gnu-head-tiny.jpg -rw-r--r-- 1 mailman mailman 288814 Nov 28 2004 JapaneseCodecs-1.4.11.tar.gz -rw-r--r-- 1 mailman mailman 260762 Dec 29 2003 KoreanCodecs-2.0.5.tar.gz -rw-r--r-- 1 mailman mailman 1696 Aug 26 2005 mailman.in -rw-r--r-- 1 mailman mailman 2022 Dec 7 2000 mailman.jpg -rw-r--r-- 1 mailman mailman 6150 Dec 7 2000 mailman-large.jpg -rw-r--r-- 1 mailman mailman 2838 Jul 25 2006 Makefile.in -rw-r--r-- 1 mailman mailman 281 Feb 1 2002 mm-icon.png -rw-r--r-- 1 mailman mailman 2677 Dec 30 2005 paths.py.in -rw-r--r-- 1 mailman mailman 945 Dec 7 2000 PythonPowered.png -rw-r--r-- 1 mailman mailman 14114 Aug 26 2005 sitelist.cfg In particular are all of JapaneseCodecs-1.4.11.tar.gz, KoreanCodecs-2.0.5.tar.gz and email-2.5.8.tar.gz there. Note that they must be the *.gz files because that's what the makefile looks for. That's what they show... Does misc/Makefile contain EMAILPKG= email-2.5.8 JACODECSPKG= JapaneseCodecs-1.4.11 KOCODECSPKG= KoreanCodecs-2.0.5 PACKAGES= $(EMAILPKG) $(JACODECSPKG) $(KOCODECSPKG) EMAILPKG= email-2.5.8 JACODECSPKG= JapaneseCodecs-1.4.11 KOCODECSPKG= KoreanCodecs-2.0.5 PACKAGES= $(EMAILPKG) $(JACODECSPKG) $(KOCODECSPKG) and install-packages: for p in $(PACKAGES); \ do \ gunzip -c $(srcdir)/$$p.tar.gz | (cd $(PKGDIR) ; tar xf -); \ (cd $(PKGDIR)/$$p ; umask 02 ; PYTHONPATH=$(PYTHONLIBDIR) $(PYTHON) $(SETUPCMD)); \ done install-packages: for p in $(PACKAGES); \ do \ gunzip -c $(srcdir)/$$p.tar.gz | (cd $(PKGDIR) ; tar xf -); \ (cd $(PKGDIR)/$$p ; umask 02 ; PYTHONPATH=$(PYTHONLIBDIR) $(PYTHON) $(SETUPCMD)); \ done See anything missing? Now, one thing I have to bring up though. When I hit 'make install', I do get a bazillion errors like these: src/_koco_uhc.h:3007: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3007: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3007: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3007: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3007: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness ...etc., etc... And at one point it fails when working in the misc folder: src/_koco.c:53: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token src/_koco.c:57: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token src/_koco.c: In function ‘error_type’: src/_koco.c:82: error: ‘NULL’ undeclared (first use in this function) src/_koco.c:82: error: (Each undeclared identifier is reported only once src/_koco.c:82: error: for each function it appears in.) src/_koco.c:82: warning: implicit declaration of function ‘strcmp’ src/_koco.c:92: warning: implicit declaration of function ‘PyErr_Format’ src/_koco.c:92: error: ‘PyExc_ValueError’ undeclared (first use in this function) src/_koco.c: At top level: src/_koco.c:99: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token In file included from src/_koco.c:121: src/euckr_codec.h:29: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token src/euckr_codec.h:100: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token In file included from src/_koco.c:122: src/cp949_codec.h:29: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token src/cp949_codec.h:121: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token In file included from src/_koco.c:123: src/koco_stream.h:32: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token src/koco_stream.h:125: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token src/koco_stream.h:262: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token src/koco_stream.h: In function ‘streaminfo_destroy’: src/koco_stream.h:295: warning: implicit declaration of function ‘PyMem_Del’ src/koco_stream.h: At top level: src/koco_stream.h:300: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token src/koco_stream.h:352:
Re: [Mailman-Users] Where's Korea? (recurring problem)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ashley M. Kirchner wrote: Now, one thing I have to bring up though. When I hit 'make install', I do get a bazillion errors like these: src/_koco_uhc.h:3007: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3007: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3007: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3007: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3007: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness ...etc., etc... And at one point it fails when working in the misc folder: src/_koco.c:53: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token src/_koco.c:57: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token snip src/_koco.c:164: warning: implicit declaration of function ‘Py_FatalError’ error: command 'gcc' failed with exit status 1 make[1]: *** [install-packages] Error 1 make[1]: Leaving directory `/home/mailman/mailman-2.1.9/misc' ...right there. It looks like the #include Python.h near the beginning of _koco.c is failing. Is there a python2.4 directory in /usr/include? Of course, another option is to copy everything but email from the old system's pythonlib and then run Mailman's bin/update which is the only part of 'make install' that didn't complete - -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFG62EbVVuXXpU7hpMRAhuaAJ9aNvEaJZOl1XEekduetRdKkGuSJgCdE0sq VfzQGlt5pe9Pa5qUYoSJTBg= =6067 -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
