At 3:48 PM -0400 10/22/05, John E. Malmberg wrote: >Craig A. Berry wrote: >>At 2:19 PM -0400 10/22/05, John E. Malmberg wrote: >> my_chdir is a macro that will have an extra argument for interpreter >>context in the case of building with threads enabled, but will be >>identical to Perl_my_chdir for a non-threaded build. > > >Ok, it sounds like I (and others?) need to work on a vmsinternals.pod to >remind me not to make the same mistakes over again, and hopefully help others.
How thread context (or, more properly, interpreter context) is passed around is not VMS-specific and is pretty well covered in perlguts.pod. > >And that actually may help me with create a threaded rsync that is more >acceptable to the current maintainers. Hmm. I'm not sure I see how, but it sounds interesting. >>The linker doesn't want them, not so much these macros as the >>prototypes further down. They were getting in the symbol vector >>option and causing link failures. Just stick them back in when they >>actually point to something. > >Interesting, I can not find any linker diagnostic information in my build >logs. I wonder why? You were doing a non-thread build, so PERL_IMPLICIT_CONTEXT was not defined, so those prototypes were not visible to the compiler. They will need to be put elsewhere when they are put back in so they'll be visible for all types of builds. BTW, a couple of them had typos with missing semicolons at the end. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
