Hi all, I've been checking out the archives in an attempt to find an already-published answer to my problem and have only found one thread which comes close to describing what I'm seeing. When run 'configure', there are no problems. Once I try making things, I get strange errors which I suppose are probably python-related: slimemold[52]:/tmp/Zope-2.9.1% ./configure --prefix=/usr/local/bin/zope Configuring Zope installation Testing for an acceptable Python interpreter... Python version 2.4.1 found at /usr/bin/python Python version 2.4.1 found at /usr/bin/python2 Python version 2.4.1 found at /usr/bin/python2.4 Python version 2.4.2 found at /usr/local/bin/python The optimum Python version (2.4.2) was found at /usr/local/bin/python. slimemold[53]:/tmp/Zope-2.9.1% make /usr/local/bin/python install.py -q build In file included from Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeModuleTemplate.c:335, from Dependencies/BTrees-Zope-2.9.1/BTrees/_fsBTree.c:70: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeItemsTemplate.c: In function âgetBucketEntryâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeItemsTemplate.c:238: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeItemsTemplate.c:242: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeItemsTemplate.c:249: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeItemsTemplate.c:252: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness In file included from Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeModuleTemplate.c:336, from Dependencies/BTrees-Zope-2.9.1/BTrees/_fsBTree.c:70: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function â_bucket_getâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:93: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âBucket_maxminKeyâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:713: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âbucket_keysâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:829: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âbucket_valuesâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:867: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âbucket_itemsâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:907: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:911: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âbucket_byValueâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:955: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:961: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âbucket_getstateâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:1134: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:1140: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:1151: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness In file included from Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeModuleTemplate.c:337, from Dependencies/BTrees-Zope-2.9.1/BTrees/_fsBTree.c:70: Dependencies/BTrees-Zope-2.9.1/BTrees/SetTemplate.c: In function âset_itemâ: Dependencies/BTrees-Zope-2.9.1/BTrees/SetTemplate.c:266: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness In file included from Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeModuleTemplate.c:338, from Dependencies/BTrees-Zope-2.9.1/BTrees/_fsBTree.c:70: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c: In function âBTree_getstateâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c:953: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c: In function âBTree_maxminKeyâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c:1390: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c: In function âBTree_byValueâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c:1641: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c:1647: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/ExtensionClass-Zope-2.9.1/ExtensionClass/_ExtensionClass.c: In function âPyExtensionClass_Export_â: Dependencies/ExtensionClass-Zope-2.9.1/ExtensionClass/_ExtensionClass.c:768: warning: cast from pointer to integer of different size Dependencies/AccessControl-Zope-2.9.1/AccessControl/cAccessControl.c: In function âmodule_aq_validateâ: Dependencies/AccessControl-Zope-2.9.1/AccessControl/cAccessControl.c:2155: warning: âinstâ may be used uninitialized in this function Dependencies/AccessControl-Zope-2.9.1/AccessControl/cAccessControl.c:2155: warning: âobjâ may be used uninitialized in this function Dependencies/AccessControl-Zope-2.9.1/AccessControl/cAccessControl.c:2155: warning: ânameâ may be used uninitialized in this function Dependencies/AccessControl-Zope-2.9.1/AccessControl/cAccessControl.c:2155: warning: âvâ may be used uninitialized in this function Dependencies/AccessControl-Zope-2.9.1/AccessControl/cAccessControl.c:2155: warning: âvalidateâ may be used uninitialized in this function Dependencies/persistent-Zope-2.9.1/persistent/TimeStamp.c: In function âTimeStamp_rawâ: Dependencies/persistent-Zope-2.9.1/persistent/TimeStamp.c:221: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/persistent-Zope-2.9.1/persistent/TimeStamp.c: In function âTimeStamp_laterThanâ: Dependencies/persistent-Zope-2.9.1/persistent/TimeStamp.c:264: warning: pointer targets in passing argument 1 of âTimeStamp_FromStringâ differ in signedness ------- I have tried specifying the --with-python=/usr/local/bin/python option as well. I've also attempted some of the suggestions in the one thread that seemed to pertain to what I was seeing: http://www.gossamer-threads.com/lists/zope/users/179040?search_string=%2Bmak... slimemold[54]:/tmp/Zope-2.9.1% make -v GNU Make 3.80 slimemold[55]:/tmp/Zope-2.9.1% uname -a Linux slimemold.xxxxxxxxx.org 2.6.14-1.1637_FC4 #1 Wed Nov 9 19:01:56 EST 2005 x86_64 x86_64 x86_64 GNU/Linux I compiled the python 2.4.2 rather than used an rpm as part of the troubleshooting process. Does anyone have any ideas why there errors are popping up upon 'make'? Thanks in advance! Chris ---- Some people wear Superman pajamas. Superman wears Chuck Norris pajamas.
These are warnings coming from GCC (as opposed to errors, which would prevent compilation from finishing). GCC 4.X emits these pointer signedness warnings whereas earlier GCC versions did not. This issue has been fixed on the Zope trunk, I believe (the codebase which will become Zope 2.10). - C On Mar 20, 2006, at 9:23 PM, a blob of green gelatin wrote:
Hi all,
I've been checking out the archives in an attempt to find an already-published answer to my problem and have only found one thread which comes close to describing what I'm seeing.
When run 'configure', there are no problems. Once I try making things, I get strange errors which I suppose are probably python- related:
slimemold[52]:/tmp/Zope-2.9.1% ./configure --prefix=/usr/local/bin/ zope
Configuring Zope installation
Testing for an acceptable Python interpreter...
Python version 2.4.1 found at /usr/bin/python Python version 2.4.1 found at /usr/bin/python2 Python version 2.4.1 found at /usr/bin/python2.4 Python version 2.4.2 found at /usr/local/bin/python
The optimum Python version (2.4.2) was found at /usr/local/bin/python.
slimemold[53]:/tmp/Zope-2.9.1% make /usr/local/bin/python install.py -q build In file included from Dependencies/BTrees-Zope-2.9.1/BTrees/ BTreeModuleTemplate.c:335, from Dependencies/BTrees-Zope-2.9.1/BTrees/ _fsBTree.c:70: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeItemsTemplate.c: In function âgetBucketEntryâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeItemsTemplate.c:238: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeItemsTemplate.c:242: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeItemsTemplate.c:249: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeItemsTemplate.c:252: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness In file included from Dependencies/BTrees-Zope-2.9.1/BTrees/ BTreeModuleTemplate.c:336, from Dependencies/BTrees-Zope-2.9.1/BTrees/ _fsBTree.c:70: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function â_bucket_getâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:93: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âBucket_maxminKeyâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:713: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âbucket_keysâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:829: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âbucket_valuesâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:867: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âbucket_itemsâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:907: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:911: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âbucket_byValueâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:955: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:961: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c: In function âbucket_getstateâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:1134: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:1140: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BucketTemplate.c:1151: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness In file included from Dependencies/BTrees-Zope-2.9.1/BTrees/ BTreeModuleTemplate.c:337, from Dependencies/BTrees-Zope-2.9.1/BTrees/ _fsBTree.c:70: Dependencies/BTrees-Zope-2.9.1/BTrees/SetTemplate.c: In function âset_itemâ: Dependencies/BTrees-Zope-2.9.1/BTrees/SetTemplate.c:266: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness In file included from Dependencies/BTrees-Zope-2.9.1/BTrees/ BTreeModuleTemplate.c:338, from Dependencies/BTrees-Zope-2.9.1/BTrees/ _fsBTree.c:70: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c: In function âBTree_getstateâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c:953: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c: In function âBTree_maxminKeyâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c:1390: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c: In function âBTree_byValueâ: Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c:1641: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/BTrees-Zope-2.9.1/BTrees/BTreeTemplate.c:1647: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/ExtensionClass-Zope-2.9.1/ExtensionClass/ _ExtensionClass.c: In function âPyExtensionClass_Export_â: Dependencies/ExtensionClass-Zope-2.9.1/ExtensionClass/ _ExtensionClass.c:768: warning: cast from pointer to integer of different size Dependencies/AccessControl-Zope-2.9.1/AccessControl/ cAccessControl.c: In function âmodule_aq_validateâ: Dependencies/AccessControl-Zope-2.9.1/AccessControl/ cAccessControl.c:2155: warning: âinstâ may be used uninitialized in this function Dependencies/AccessControl-Zope-2.9.1/AccessControl/ cAccessControl.c:2155: warning: âobjâ may be used uninitialized in this function Dependencies/AccessControl-Zope-2.9.1/AccessControl/ cAccessControl.c:2155: warning: ânameâ may be used uninitialized in this function Dependencies/AccessControl-Zope-2.9.1/AccessControl/ cAccessControl.c:2155: warning: âvâ may be used uninitialized in this function Dependencies/AccessControl-Zope-2.9.1/AccessControl/ cAccessControl.c:2155: warning: âvalidateâ may be used uninitialized in this function Dependencies/persistent-Zope-2.9.1/persistent/TimeStamp.c: In function âTimeStamp_rawâ: Dependencies/persistent-Zope-2.9.1/persistent/TimeStamp.c:221: warning: pointer targets in passing argument 1 of âPyString_FromStringAndSizeâ differ in signedness Dependencies/persistent-Zope-2.9.1/persistent/TimeStamp.c: In function âTimeStamp_laterThanâ: Dependencies/persistent-Zope-2.9.1/persistent/TimeStamp.c:264: warning: pointer targets in passing argument 1 of âTimeStamp_FromStringâ differ in signedness
-------
I have tried specifying the --with-python=/usr/local/bin/python option as well. I've also attempted some of the suggestions in the one thread that seemed to pertain to what I was seeing:
http://www.gossamer-threads.com/lists/zope/users/179040? search_string=%2Bmake%20%2Berrors;#179040
slimemold[54]:/tmp/Zope-2.9.1% make -v GNU Make 3.80
slimemold[55]:/tmp/Zope-2.9.1% uname -a Linux slimemold.xxxxxxxxx.org 2.6.14-1.1637_FC4 #1 Wed Nov 9 19:01:56 EST 2005 x86_64 x86_64 x86_64 GNU/Linux
I compiled the python 2.4.2 rather than used an rpm as part of the troubleshooting process.
Does anyone have any ideas why there errors are popping up upon 'make'?
Thanks in advance!
Chris ----
Some people wear Superman pajamas. Superman wears Chuck Norris pajamas. _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris McDonough wrote:
These are warnings coming from GCC (as opposed to errors, which would prevent compilation from finishing).
GCC 4.X emits these pointer signedness warnings whereas earlier GCC versions did not. This issue has been fixed on the Zope trunk, I believe (the codebase which will become Zope 2.10).
The fix is actually on the ZODB branches / trunk, but not yet propagated to the svn:externals in Zope (which are pinned to specific revisions of their respective ZODB branches). Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEH/nO+gerLs4ltQ4RAlt8AJ9tTmgAyRycVpYDHSoe6TZO7lWsMwCgs6pw VHINSCU7qpZaYyLb4B///X4= =k5B7 -----END PGP SIGNATURE-----
On Tue, 21 Mar 2006, Chris McDonough wrote:
These are warnings coming from GCC (as opposed to errors, which would prevent compilation from finishing).
GCC 4.X emits these pointer signedness warnings whereas earlier GCC versions did not. This issue has been fixed on the Zope trunk, I believe (the codebase which will become Zope 2.10).
Thanks for the answer! I went ahead and continued then with my installation. after running 'make install' with no problems, I created an instance via the /usr/local/bin/zope/bin/mkzopeinstance.py script. The script ran fine with no errors. Following the INSTALL.txt file in the Zope directory, my next step would be to head over to my installed instance and run the zopectl script to get things going. When I ran it, I get the following: slimemold[62]:/home/jello/zope/bin% ./zopectl start Traceback (most recent call last): File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 316, in ? main() File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 274, in main options.realize(args) File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 91, in realize ZDOptions.realize(self, *args, **kw) File "/usr/local/bin/zope/lib/python/zdaemon/zdoptions.py", line 273, in realize self.load_schema() File "/usr/local/bin/zope/lib/python/zdaemon/zdoptions.py", line 321, in load_schema self.schema = ZConfig.loadSchema(self.schemafile) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 31, in loadSchema return SchemaLoader().loadURL(url) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 65, in loadURL return self.loadResource(r) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 159, in loadResource schema = ZConfig.schema.parseResource(resource, self) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 27, in parseResource xml.sax.parse(resource.file, parser) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/__init__.py", line 31, in parse parser.parse(filename_or_stream) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/expatreader.py", line 109, in parse xmlreader.IncrementalParser.parse(self, source) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/xmlreader.py", line 123, in parse self.feed(buffer) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/expatreader.py", line 216, in feed self._parser.Parse(data, isFinal) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/expatreader.py", line 311, in start_element self._cont_handler.startElement(name, AttributesImpl(attrs)) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 99, in startElement getattr(self, "start_" + name)(attrs) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 475, in start_schema keytype, valuetype, datatype = self.get_sect_typeinfo(attrs) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 201, in get_sect_typeinfo datatype = self.get_datatype(attrs, "datatype", "null", base) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 194, in get_datatype return self._registry.get(dtname) File "/usr/local/bin/zope/lib/python/ZConfig/datatypes.py", line 398, in get t = self.search(name) File "/usr/local/bin/zope/lib/python/ZConfig/datatypes.py", line 423, in search package = __import__(n, g, g, component) File "/usr/local/bin/zope/lib/python/Zope2/Startup/datatypes.py", line 20, in ? from ZODB.config import ZODBDatabase File "/usr/local/bin/zope/lib/python/ZODB/__init__.py", line 20, in ? from persistent import TimeStamp File "/usr/local/bin/zope/lib/python/persistent/__init__.py", line 19, in ? from cPersistence import Persistent, GHOST, UPTODATE, CHANGED, STICKY ImportError: /usr/local/bin/zope/lib/python/persistent/cPersistence.so: undefined symbol: PyUnicodeUCS2_AsEncodedString I configured this to use /usr/local/bin/python (2.4.2 compiled) instead of the default /usr/bin/python (2.4.1 package). I searched the archives to look for something here, and I've found one similar thread: http://www.gossamer-threads.com/lists/zope/users/163264?search_string=%2Bzop... which mentions some possibilities: "Ah. uhm.. sorry. This traceback can only occur when cPersistence.so wasnt compiled yet, has been deleted, is for the wrong python version or is otherwise unavailable. It is usually generated thru installation/compilation. I'd check paths for INSTANCE_HOME, SOFTWARE_HOME etc; which python version is used (and if its different to the version you installed with) " So far with this installation, the only (as far as I can tell) modification from the vanilla installation is that I'm using a seperate python instance on the box. Otherwise it's a simple configure/make/make install from the /tmp directory. I installed zope to /usr/local/bin/zope and given my regular user write permissions (via group) to that directory so that my 'make install' didn't require a sudo. I installed the instance to /home/jello/zope and ran the /home/jello/zope/bin/zopectl start command (as referenced above) with the aforementioned output. I'm thinking it must be something really simple because I'm not seeing it in the archives and I'm not really deviating from what's in the doc/INSTALL.txt file. (I didn't see anything different in the Zope book either. It's all pretty straightforward from what I'm reading. http://www.plope.com/Books/2_7Edition/InstallingZope.stx#2-6) Anyone have ideas? I'd appreciate it! Thanks in advance! -Chris ---- Some people wear Superman pajamas. Superman wears Chuck Norris pajamas.
a blob of green gelatin wrote:
On Tue, 21 Mar 2006, Chris McDonough wrote:
These are warnings coming from GCC (as opposed to errors, which would prevent compilation from finishing).
GCC 4.X emits these pointer signedness warnings whereas earlier GCC versions did not. This issue has been fixed on the Zope trunk, I believe (the codebase which will become Zope 2.10).
Thanks for the answer!
I went ahead and continued then with my installation.
after running 'make install' with no problems, I created an instance via the /usr/local/bin/zope/bin/mkzopeinstance.py script. The script ran fine with no errors.
Following the INSTALL.txt file in the Zope directory, my next step would be to head over to my installed instance and run the zopectl script to get things going.
When I ran it, I get the following:
slimemold[62]:/home/jello/zope/bin% ./zopectl start Traceback (most recent call last): File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 316, in ? main() File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 274, in main options.realize(args) File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 91, in realize ZDOptions.realize(self, *args, **kw) File "/usr/local/bin/zope/lib/python/zdaemon/zdoptions.py", line 273, in realize self.load_schema() File "/usr/local/bin/zope/lib/python/zdaemon/zdoptions.py", line 321, in load_schema self.schema = ZConfig.loadSchema(self.schemafile) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 31, in loadSchema return SchemaLoader().loadURL(url) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 65, in loadURL return self.loadResource(r) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 159, in loadResource schema = ZConfig.schema.parseResource(resource, self) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 27, in parseResource xml.sax.parse(resource.file, parser) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/__init__.py", line 31, in parse parser.parse(filename_or_stream) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/expatreader.py", line 109, in parse xmlreader.IncrementalParser.parse(self, source) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/xmlreader.py", line 123, in parse self.feed(buffer) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/expatreader.py", line 216, in feed self._parser.Parse(data, isFinal) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/expatreader.py", line 311, in start_element self._cont_handler.startElement(name, AttributesImpl(attrs)) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 99, in startElement getattr(self, "start_" + name)(attrs) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 475, in start_schema keytype, valuetype, datatype = self.get_sect_typeinfo(attrs) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 201, in get_sect_typeinfo datatype = self.get_datatype(attrs, "datatype", "null", base) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 194, in get_datatype return self._registry.get(dtname) File "/usr/local/bin/zope/lib/python/ZConfig/datatypes.py", line 398, in get t = self.search(name) File "/usr/local/bin/zope/lib/python/ZConfig/datatypes.py", line 423, in search package = __import__(n, g, g, component) File "/usr/local/bin/zope/lib/python/Zope2/Startup/datatypes.py", line 20, in ? from ZODB.config import ZODBDatabase File "/usr/local/bin/zope/lib/python/ZODB/__init__.py", line 20, in ? from persistent import TimeStamp File "/usr/local/bin/zope/lib/python/persistent/__init__.py", line 19, in ? from cPersistence import Persistent, GHOST, UPTODATE, CHANGED, STICKY ImportError: /usr/local/bin/zope/lib/python/persistent/cPersistence.so: undefined symbol: PyUnicodeUCS2_AsEncodedString
I configured this to use /usr/local/bin/python (2.4.2 compiled) instead of the default /usr/bin/python (2.4.1 package).
I searched the archives to look for something here, and I've found one similar thread:
http://www.gossamer-threads.com/lists/zope/users/163264?search_string=%2Bzop...
which mentions some possibilities:
"Ah. uhm.. sorry. This traceback can only occur when cPersistence.so wasnt compiled yet, has been deleted, is for the wrong python version or is otherwise unavailable. It is usually generated thru installation/compilation.
I'd check paths for INSTANCE_HOME, SOFTWARE_HOME etc; which python version is used (and if its different to the version you installed with) "
So far with this installation, the only (as far as I can tell) modification from the vanilla installation is that I'm using a seperate python instance on the box. Otherwise it's a simple configure/make/make install from the /tmp directory.
I installed zope to /usr/local/bin/zope and given my regular user write permissions (via group) to that directory so that my 'make install' didn't require a sudo. I installed the instance to /home/jello/zope and ran the /home/jello/zope/bin/zopectl start command (as referenced above) with the aforementioned output.
I'm thinking it must be something really simple because I'm not seeing it in the archives and I'm not really deviating from what's in the doc/INSTALL.txt file. (I didn't see anything different in the Zope book either. It's all pretty straightforward from what I'm reading. http://www.plope.com/Books/2_7Edition/InstallingZope.stx#2-6)
Anyone have ideas? I'd appreciate it!
Thanks in advance!
-Chris -
Blob, FWIW, Maybe PyUnicodeUCS2_AsEncodedString is the culprit?. Found this via google (http://www.egenix.com/files/python/mxODBC-Zope-DA.html): *Python Unicode versions:* If you get errors mentioning "unresolved symbol PyUnicodeUCS2_AsEncodedString" during loading of the mxODBC Zope DA product, you are likely using a Linux distribution which ships with a UCS4-build (4-byte Unicode) of Python. RedHat 9 and SuSE 9 and later ship with UCS4 builds of Python and Zope, so please download the UCS4 versions of the product. To find out which Python Unicode you have, please run the following command using the Python interpreter used by your Zope installation: |python -c "import sys; print (sys.maxunicode < 66000) and 'UCS2' or 'UCS4'"| David
On Tue, 21 Mar 2006, David wrote:
undefined symbol: PyUnicodeUCS2_AsEncodedString Blob,
FWIW,
Maybe PyUnicodeUCS2_AsEncodedString is the culprit?.
Found this via google (http://www.egenix.com/files/python/mxODBC-Zope-DA.html): *Python Unicode versions:* If you get errors mentioning "unresolved symbol PyUnicodeUCS2_AsEncodedString" during loading of the mxODBC Zope DA product, you are likely using a Linux distribution which ships with a UCS4-build (4-byte Unicode) of Python.
RedHat 9 and SuSE 9 and later ship with UCS4 builds of Python and Zope, so please download the UCS4 versions of the product.
To find out which Python Unicode you have, please run the following command using the Python interpreter used by your Zope installation: |python -c "import sys; print (sys.maxunicode < 66000) and 'UCS2' or 'UCS4'"|
Hi David. Thanks for the input! When you it says, "...so please download the UCS4 version of the product." Do they mean the egenix product or the zope product? It seems as if the egenix product costs $120 for a license according to the link you sent, so I'm not sure I want to go down that road. For a simple installation like mine, isn't there a built-in database/ODBC to be used?
From the command it offered, I can see I'm running the UCS4 version, so perhaps there is something to that line about "PyUnicodeUCS2_AsEncodedString"... I'll try googling around based off of that (hadn't thought to google that phrase.. it's a good idea).
Cheers! Chris aka Blob :) ---- Some people wear Superman pajamas. Superman wears Chuck Norris pajamas.
On Wed, 22 Mar 2006, a blob of green gelatin wrote:
Maybe PyUnicodeUCS2_AsEncodedString is the culprit?.
RedHat 9 and SuSE 9 and later ship with UCS4 builds of Python and Zope, so please download the UCS4 versions of the product.
To find out which Python Unicode you have, please run the following command using the Python interpreter used by your Zope installation: |python -c "import sys; print (sys.maxunicode < 66000) and 'UCS2' or 'UCS4'"|
Hi again David (and jens 'n anyone else reading this thread), I've solved the problem thanks to both of your input. I don't think this is a bug on anyone's part, but I do think it'd be something to add to a FAQ or the INSTALL.txt document in case others run into it like I do. I found this URL (via googling for the PyUnicodeUCS2_AsEncodedString message) : http://www.initd.org/tracker/psycopg/ticket/88 and these lines basically hit the nail on the head: "this appears to revolve around the fact that suse 10 comes with python built as UCS4, and it appears that a default build of python is UCS2. since i would like to have suse maintain python installs i normally have yast update it. however, zope 3 wants 2.4.2 and suse build atm is at 2.4.1. thus i installed in local 2.4.2. (also this may be an issue with redhat from what i found on the egenix site) the problem is that with one python doing UCS2 and the other doing UCS4 you can get in a situation where mx and psycopg are built oriented to, say for example UCS2 if you used the default build of 2.4.2. since the build doesn't check to see if the UCS is one or the other or that your using a different python this time for the install, then what python was used with current build. after you do the build once if you install for a 2nd python it uses the prior build and merrily installs the UCS2 oriented lib into the UCS4 python." Now, I'm using Fedora Core 4 rather than SUSE, but it sure seemed appropriate. Funnily enough, the command you gave me to run and check the UCS I had run only on the system version, not the compiled version of python. I ran the command on my compiled version and sure enough, it showed UCS2 rather than UCS4 (which my system python had shown)! So I had to recompile python 2.4.2 to include UCS4 support: (./configure --enable-unicode=ucs4) then recompile zope and voila! I'm now back on the INSTALL.txt roadmap! :) One note: The python README file for the 2.4.2 tarball states: Red Hat Linux: Red Hat 9 built Python2.2 in UCS-4 mode and hacked Tcl to support it. To compile Python with Tkinter on these systems, you will need to pass --enable-unicode=ucs4 flag to ./configure. This is no longer needed in Fedora Core. I'm probably reading it wrong (though I did have to install a tkinter rpm at some point a long time ago), but I can read it as saying you wouldn't need to pass this flag to 'configure' for fedora core because FC already enables UCS4. I specified the flag anyway and it seems to have done the trick. Thanks again everyone! Cheers, Chris ----- Some people wear Superman pajamas. Superman wears Chuck Norris pajamas.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22 Mar 2006, at 02:16, a blob of green gelatin wrote:
slimemold[62]:/home/jello/zope/bin% ./zopectl start Traceback (most recent call last): File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 316, in ? main() File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 274, in main options.realize(args) File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 91, in realize ZDOptions.realize(self, *args, **kw) File "/usr/local/bin/zope/lib/python/zdaemon/zdoptions.py", line 273, in realize self.load_schema() File "/usr/local/bin/zope/lib/python/zdaemon/zdoptions.py", line 321, in load_schema self.schema = ZConfig.loadSchema(self.schemafile) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 31, in loadSchema return SchemaLoader().loadURL(url) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 65, in loadURL return self.loadResource(r) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 159, in loadResource schema = ZConfig.schema.parseResource(resource, self) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 27, in parseResource xml.sax.parse(resource.file, parser) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/ __init__.py", line 31, in parse parser.parse(filename_or_stream) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/ expatreader.py", line 109, in parse xmlreader.IncrementalParser.parse(self, source) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/ xmlreader.py", line 123, in parse self.feed(buffer) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/ expatreader.py", line 216, in feed self._parser.Parse(data, isFinal) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/ expatreader.py", line 311, in start_element self._cont_handler.startElement(name, AttributesImpl(attrs)) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 99, in startElement getattr(self, "start_" + name)(attrs) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 475, in start_schema keytype, valuetype, datatype = self.get_sect_typeinfo(attrs) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 201, in get_sect_typeinfo datatype = self.get_datatype(attrs, "datatype", "null", base) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 194, in get_datatype return self._registry.get(dtname) File "/usr/local/bin/zope/lib/python/ZConfig/datatypes.py", line 398, in get t = self.search(name) File "/usr/local/bin/zope/lib/python/ZConfig/datatypes.py", line 423, in search package = __import__(n, g, g, component) File "/usr/local/bin/zope/lib/python/Zope2/Startup/datatypes.py", line 20, in ? from ZODB.config import ZODBDatabase File "/usr/local/bin/zope/lib/python/ZODB/__init__.py", line 20, in ? from persistent import TimeStamp File "/usr/local/bin/zope/lib/python/persistent/__init__.py", line 19, in ? from cPersistence import Persistent, GHOST, UPTODATE, CHANGED, STICKY ImportError: /usr/local/bin/zope/lib/python/persistent/ cPersistence.so: undefined symbol: PyUnicodeUCS2_AsEncodedString
I configured this to use /usr/local/bin/python (2.4.2 compiled) instead of the default /usr/bin/python (2.4.1 package).
You have the Pythons confused it seems. You're saying it's using /usr/ local/bin/python, while some of the paths in that traceback point to the system python. Either you built it with the system Python or you ran it with the system Python now. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEIRoFRAx5nvEhZLIRArS/AKCXH7D5nAoGZZr3NqbN8JtaMs06IwCfR1SM tfgco5Hxz5UxhtqGsBdSlh8= =sUyl -----END PGP SIGNATURE-----
On Wed, 22 Mar 2006, Jens Vagelpohl wrote:
slimemold[62]:/home/jello/zope/bin% ./zopectl start Traceback (most recent call last): File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 316, in ? main() File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 274, in main options.realize(args) File "/usr/local/bin/zope/lib/python/Zope2/Startup/zopectl.py", line 91, in realize ZDOptions.realize(self, *args, **kw) File "/usr/local/bin/zope/lib/python/zdaemon/zdoptions.py", line 273, in realize self.load_schema() File "/usr/local/bin/zope/lib/python/zdaemon/zdoptions.py", line 321, in load_schema self.schema = ZConfig.loadSchema(self.schemafile) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 31, in loadSchema return SchemaLoader().loadURL(url) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 65, in loadURL return self.loadResource(r) File "/usr/local/bin/zope/lib/python/ZConfig/loader.py", line 159, in loadResource schema = ZConfig.schema.parseResource(resource, self) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 27, in parseResource xml.sax.parse(resource.file, parser) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/__init__.py", line 31, in parse parser.parse(filename_or_stream) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/expatreader.py", line 109, in parse xmlreader.IncrementalParser.parse(self, source) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/xmlreader.py", line 123, in parse self.feed(buffer) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/expatreader.py", line 216, in feed self._parser.Parse(data, isFinal) File "/usr/lib64/python2.4/site-packages/_xmlplus/sax/expatreader.py", line 311, in start_element self._cont_handler.startElement(name, AttributesImpl(attrs)) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 99, in startElement getattr(self, "start_" + name)(attrs) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 475, in start_schema keytype, valuetype, datatype = self.get_sect_typeinfo(attrs) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 201, in get_sect_typeinfo datatype = self.get_datatype(attrs, "datatype", "null", base) File "/usr/local/bin/zope/lib/python/ZConfig/schema.py", line 194, in get_datatype return self._registry.get(dtname) File "/usr/local/bin/zope/lib/python/ZConfig/datatypes.py", line 398, in get t = self.search(name) File "/usr/local/bin/zope/lib/python/ZConfig/datatypes.py", line 423, in search package = __import__(n, g, g, component) File "/usr/local/bin/zope/lib/python/Zope2/Startup/datatypes.py", line 20, in ? from ZODB.config import ZODBDatabase File "/usr/local/bin/zope/lib/python/ZODB/__init__.py", line 20, in ? from persistent import TimeStamp File "/usr/local/bin/zope/lib/python/persistent/__init__.py", line 19, in ? from cPersistence import Persistent, GHOST, UPTODATE, CHANGED, STICKY ImportError: /usr/local/bin/zope/lib/python/persistent/cPersistence.so: undefined symbol: PyUnicodeUCS2_AsEncodedString
I configured this to use /usr/local/bin/python (2.4.2 compiled) instead of the default /usr/bin/python (2.4.1 package).
You have the Pythons confused it seems. You're saying it's using /usr/ local/bin/python, while some of the paths in that traceback point to the system python. Either you built it with the system Python or you ran it with the system Python now.
jens
Hi Jens. First off, thanks for the reply! I admit I can't be sure of what python's being used, but I can be sure I followed the instructions given in the doc/INSTALL.txt and the configure --help . If I specify the non-system python (2.4.2 in /usr/local/bin/python) in the configure, do I need to also add it into the zope.conf somewhere? I had looked for a reference in the conf file but didn't find one. Perhaps there is a command-line switch for zopectl to specify the non-system python? I didn't see anything listed with the --help for zopectl. So perhaps when I run the zopectl it'll revert to the system python rather than the build-time location specified? Does anyone know? Oh, and I didn't notice where you had seen the reference to the system python in the traceback. Could you point out which line you saw with it? Cheers! :) -Chris ---- Some people wear Superman pajamas. Superman wears Chuck Norris pajamas.
participants (5)
-
a blob of green gelatin -
Chris McDonough -
David -
Jens Vagelpohl -
Tres Seaver