ELF vs. a.out and Python 2.0 build

[Martin von Loewis]

kent at tiamat.goathill.org (Kent Polk) writes:

> Evidently there's a problem with the symbol naming mechanism to be
> used when building shared modules for a.out. I compared configure
> options with Python 1.5.2 and can't determine how this should be
> fixed for a.out with Python 2.0. (Tried a number of possibilities)
> 
> Any suggestions? Thanks

I guess your system uses dynload_shlib.c? Well, it them probably comes from

	/* ### should there be a leading underscore for some platforms? */
	sprintf(funcname, "init%.200s", shortname);

The problem apparently is that there is no compile-time way to find
out whether to use an underscore or not, on your system, is there?  If
it is possible to tell at compile time whether the compiler is
generating an a.out file (e.g. via an #ifdef), then please submit a patch
to sourceforge.net/projects/python to correct that error.

Regards,
Martin