At 22.48 -0500 1998.12.20, Arved Sandstrom wrote: >This came up in connection with an XS build. I have a module which >successfully went through all the stages, and for a change I even followed >the approved procedure. :-) The BuildProgram successfully produced my >shared library, and Check Syntax for a test Perl script is OK. > >However, when I run the thing, I get an error 12 - unimplemented core >routine (well, after MacPerl implodes...). This has me a bit perplexed - >how do I find out what's not implemented? The linker didn't emit a peep. > >I checked my procedures by producing a really simple XSUB from scratch, >and this works fine. > >Any ideas? The XS code is actually a wrapper itself, for a whole mass of >straight C generated by Flex and Bison. Makefile.PL is modified to handle >the separate compiles, so as to keep the Perl #defines of yacc-related >stuff from mixing up with mine (the files in SQL::Statement give a rough >idea of what I'm doing, sort of). The C parser code is tested as an >application and works OK. I mention this because I'm sure the problem is >related, although I wouldn't have expected this particular error message. > >Thanks for any guidance. (The only reason I know what error 12 is because >I've got this great little MacErrors utility. :-) ) No thoughts here. In my limited experience with Mac programming (other than higher-level scripting with Perl and AppleScript, etc.), I've noticed that Macs can be a pain to work with in C. Uninformative crashes and bombs that make you restart each time. Bleah. -- Chris Nandor mailto:pudge@pobox.com http://pudge.net/ %PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10 1FF77F13 8180B6B6']) ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch