Jeremy Kloth schrieb:
> GCC's symbol visibility is supposed to address this exact problem. It would
> be nice if -fvisibility=hidden was used to build Python (and its extensions)
> by default on supported platforms/compilers. It shouldn't be much of an
> issue wrt. exported symbols as they alr
Gerhard Häring schrieb:
> Apparently at least gcc on Linux exports all symbols by default that are
> not static.
Correct. Various factors influence run-time symbol binding, though.
> This creates problems with Python extensions that export
> symbols that are also used in other contexts. For examp
On Saturday, September 23, 2006 11:31 am, Gerhard Häring wrote:
> Looks like I don't know C so well after all ...
>
> Apparently at least gcc on Linux exports all symbols by default that are
> not static. This creates problems with Python extensions that export
> symbols that are also used in other
