'I don't believe it is the case'-- trust me, it is the case. As to why it hasn't shown up, at a guess, the company in question doesn't use much (if any) external XS. I'm told that it wasn't left out intentionally. Of course the person who said that also didn't know the symbol in question<sigh> The perlapi.h seems fine, although I could diff it with the AS copy which is known to work. You said 'edit the appropriate makefile', could you be a little more explicit. I need all of the info I can get if I'm going to talk these guys through it (I can't do it hands on, I'm an outside contractor, so nix that idea). Thanks!

--hsm

    Which makefile?

For win32 platforms, it's the one in the win32 directory. Do a dir README* in your toplevel perl source directory to see all the numerous README's there are. The one of interest to you will be README.win32. All you need to know is contained in the README for your platform, or as comments in the Makefile for your platform.

I don't know what you mean by "external XS", but many of the core modules use XS and , like Compress::Zlib and Data::Dumper, and practically all XS modules #include "XSUB.h" which does #include "perlapi.h".

I urge you to getyourself a copy of perl, and try to basically replicate what they did (cause it sounds very fishy).

 


______crazyinsomniac_____________________________ Of all the things I've lost, I miss my mind the most. perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"

Sounds as though it is more of a question of how did they manage to build a version without rather than a version with. Well, if nothing else you've defined my homework for the next several largish time units. Guess I've put off going all the way with perl long enough! Thanks again.

--hsm

"Never try to teach a pig to sing...it wastes your time and it annoys the pig."