-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
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
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,
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
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
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
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
