[Python-bugs-list] please resolve 191.. (PR#195)

[guido@CNRI.Reston.VA.US]

> Guido van Rossum scribbled this message on Jan 31:
> > > I have found out that I need to add -Xlinker -export-dynamic to the gcc
> > > command to compile a program linked w/ the libpython.a library... if you
> > > do not specify this option, all unreferenced symbols will be discarded...
> > > 
> > > please document this requirement in the documentation, and after that has
> > > happened, close this bug report...
> > 
> > I read your bug report 191 and I think it may be platform specific, or
> > a bug in how you link with Python, since I cannot reproduce this here
> > on Solaris.
> 
> I would try it under Solaris, but I don't have the time right now to
> compile up the latest GNU ld on solaris, to make sure that it is compiler
> specific...
> 
> > Until we are clear on this we can't fix the documentation, sorry.
> 
> I would think that you would want to document such a behavior considering
> just how many people happen to use gcc...  I am using gcc 2.7.2.3 and GNU
> ld 2.9.1, and considering the number of people that are using GNU ld 2.9.1,
> I would assume you'd want to document it so that people like myself, don't
> run into this problem...
> 
> the -Xlinker -export-dynamic happens to be a GNU ld specific solution,
> but the bug that python doesn't force include all the symbols should be
> documented so that people don't encounter the problem...

This (that it's GNU ld specific) is information that you didn't
explain first.  I am probably not using GNU ld, which may explain why
I couldn't reproduce your problem.

If you want to save me the most time, please suggest the exact patch
for the documentation, using the latest version of the docs from the
CVS tree.  (python.org/download/cvs.html)

To save me at least some time, write a paragraph of text and give me
at least a hint on which section of which document it should be
inserted into, and we'll figure it out from there.

--Guido van Rossum (home page: http://www.python.org/~guido/)