an eddy in the bitstream
Maker of lunches.
Teller of stories.
Singer of songs.
Crafter of code.
Kicker of darkness.
I recently reactivated my free yahoo.com email account so that I could test something for $work. I signed up for it 12 years ago, but stopped using it a couple of years later when I got my own domain @peknet.com. So yahoo finally deactivated it. All I had to do was click a couple of buttons to reactivate account, so that was painless. All my mail was, understandably, deleted.
Within 60 seconds of reactivating it, while I watched, I got one new message. In my Spam bucket. Hilarious.
I’d been keeping an email with a link to Ovid’s journal article about reviewing Perl Training websites. Now I’ve deleted the email. But the link was worth keeping here.
What a dramatic subject line. These spam scams are getting more desperate.
I just wasted many hours trying to figure out why libswish3 failed to pass all tests on 10.6.
This link explains what I figured out to be true the hard way:
10.6 is now a mainsream 64bit OS !
10.5 a 64bit capable 32bit OS !
If I forced 32bit compile all is well:
CFLAGS=”-m32 -O2 -g” ./configure && make test
While I would like to figure out how to compile as a native 64bit app, my MacBook has too many libs from before the 10.5 to 10.6 upgrade to trust that all the dep chain is 64bit compat.
The error I was seeing was the noxious BAD_ADDRESS error which traced back to some libxml2 hash features. Red herring. Of course, I had to recompile libxml2 with the -m32 as well so that everything was 32bit compatible. Took me hours before I noticed that the older working version on the same box was about half the size of the new version… which triggered the ol’ 32-vs-64-bit thing in my brain.
Update: In the end this was a bug in libswish3 with confusing naming of some variables. But the 64-bit thing was a Good Thing To Realize.
© 2024 peknet
Theme by Anders Noren — Up ↑