[KinoSearch] ORQuery dislikes Perl Compiler classes

[Marvin Humphrey]

On Sat, May 30, 2009 at 02:42:21PM -0700, webmasters at ctosonline.org wrote:
> > Thanks for the test.  This has been fixed by 4631.
> 
> When I try this on an Intel Mac, it still gives me a bus error. 

My primary dev machine is a Core Duo MacBook Pro.  I can't duplicate this
report with either 4639 or 4666 (trunk at the moment, passes test_valgrind).
I'm using a manually compiled vanilla Perl 5.10.0, not the stock OS X Perl
5.8.8 with ithreads, but I wouldn't think there would be a difference.

> When I  run it on a G3, this reduced test works, but my original script
> still  gives me a bus error. I’m going to try and reduce it again. The only
> problem is that the G3 is *so* slow, which makes debugging take  longer...
> :-(

FWIW, I have a G4 mac mini, and I'm installing XCode on it now so that I can
run these tests. 

> BTW, I’m using 4639 now.
> 
> Anyway, in case this is helpful, here is the perl -V output for both  
> machines (the only real difference I see being the byte order):

Looks like the stock OS X Perl for 10.5 Leopard, right?  I used to use that,
but once Apple stepped in the trap set by the stupid Scalar::Util XS/pure-Perl
bifurcation and shipped the pure-Perl Scalar::Util (minus weaken()), I've
gotten a little more serious about not messing with the system Perl.

Before we go farther, standard KS trunk-hacking checklist:

  * Make sure you "svn up" for all of trunk/ and not just trunk/perl.
  * Run "./Build distclean", then "perl Build.PL", "./Build test".

Marvin Humphrey