On Mon, Jan 25, 2010 at 10:14:35AM -0800, Collin Winter wrote: > I'm working on a patch to completely remove all traces of C++ with > configured with --without-llvm. It's a straightforward change, and > should present no difficulties.
Great to hear that, thanks for caring. > For reference, what are these "obscure platforms" where static > initializers cause problems? I've had serious trouble on AIX 5.3 TL 04 with a GCC toolchain (apparently the IBM xlc toolchain is better for that instance). The problem seems to be that gcc stores the initialisation code in a section (_GLOBAL__DI IIRC) which the system loader does not execute. Altough this was involving dlopen() from a C main() which U-S would not need AFAIK, having a C++ main() might make the loader do the right thing. I must also note that on more recent versions (TL 07) this was no problem at all. But you don't always have the luxury of being able to use recent OSes. Regards Floris PS: For completeness sake this was trying to use the omniorbpy module with Python 2.5. -- Debian GNU/Linux -- The Power of Freedom www.debian.org | www.gnu.org | www.kernel.org _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
