[Pythonmac-SIG] dynload_next

[Marcel Prastawa]

On Sat, 26 Jan 2002, Steven Majewski wrote:
> Marcel -- I kept getting error trying to apply the patch, but it
> was just like one of the things I had already tried which wasn't
> working for me.  Actually I tried two variations -- one the same
> as yours and another also setting  NSLINKMODULE_OPTION_PRIVATE.
>  version 1 didn't fix the problem for me.
>  version 2 didn't work.

Hi Steve,

NSLINKMODULE_OPTION_PRIVATE breaks VTK. The wrapper is made of a set of
flat namespace bundles that have undefined symbols (defined in other
bundles). A global symbol table is needed for this case, the module init
function does not export C/C++ functions and classes.

Is the PRIVATE flag really necessary? I think we could just keep it
disabled.

> Did you change the link options to get it to work for you ?
> ( two-level-namespace ? )

I am not sure I understand the problem. How exactly did it fail?

> (Also, I believe you used my NSLinkEditError patch, which I'm sorry to say
>  was very sloppily done for debugging purposes. All those strcat()'s
>  onto an existing constant string were a big mistake! )

Oh, it was still very useful. I have spent a lot of time doing guesswork
with the cryptic "Failure linking new module" error message. Maybe we
could just use a large string buffer and strncat() for now? Some message
is better than nothing.

Marcel