Cody Pendant has asked for the wisdom of the Perl Monks concerning the following question:

I've written a little utility which I then compiled with pp. The Mac version, a ".command" file, runs just fine on recent Mac OS X machines, but I've got someone complaining of this error on 10.2.8:
/Applications/my.command; exit perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL = (unset), LANG = "en" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). dyld: /Applications/my.command Undefined symbols: _nl_langinfo Trace/BPT trap logout

The application fails at that point. Those warnings shouldn't cause it to fail, should they? And anyway, locale is irrelevant to this app. So it's more likely the line beginning "dyld" that's to blame? Can anyone shed any light on this? Thanks. The version of Perl on 10.2 was pretty ancient. 5.6.1, from memory?



($_='kkvvttuu bbooppuuiiffss qqffssmm iibbddllffss')
=~y~b-v~a-z~s; print

Replies are listed 'Best First'.
Re: pp-compiled script can't run on Mac OS 10.2
by Fletch (Bishop) on Feb 24, 2006 at 23:35 UTC

    I'd guess it's more OS version drift in things like the C library. I'm pretty sure that compiling an app for 10.2 would require special linking mojo if you were using XCode, so I'm not surprised that whatever options pp's using don't work. Best bet would be to find a 10.2 box and pp up a copy there.