On Apr 26, 2013, at 6:15 PM, alex lupu wrote: > I'm respectfully looking forward to any kind words > addressing the following situation and/or questions. > > SITUATION > As part of the annual spring cleaning updates, I did > > 1. Compile and Install Python-2.7.4, configured with > "--enable-unicode=ucs4". > > 2. Attempt to compile Glib-2.34.3 > Here, the compile fails ignominiously with the notorious > symbol, "PyUnicodeUCS2_DecodeUTF8", undefined. > > 3. Recompile and Reinstall Python-2.7.4 configured withOUT > "--enable-unicode=ucs4" (i.e., configured with ucs2). > > 4. Compile and Install Glib-2.34.3 successfully. End of story. > > QUESTIONS > 1. If I stay at ucs2, any problems now and in the future? > > 2. Is there a way for me to be sure the system is _clean_ on ucs2 > without any "remnant" pockets of utc4 hiding somewhere? > > 3. Is there, somewhere, some software lurking around assuming > it were on ucs4 and rearing their ugly head at the worst > possible time? > > 3. Other? > > Thanking in advance, > -- Alex > -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page
Greetings, check this thread for a discussion of a possible reason for your thread. http://mail.python.org/pipermail/python-dev/2008-July/080892.html Sincerely, William Harrington -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
