In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Kevin Michael Vail) wrote:
I *know* I'm missing something, I just don't know what.
OK, thanks to Rick and Jerry for pointing out that what I was missing
was the boat. ;-) I remembered too far back. DYLD_ALLOW_MULTISYMS is
out, patches to
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Ken Williams) wrote:
In the documentation for modules like Mac::Resources and Mac::Memory,
there's always a warning that says I need to look at Inside Macintosh,
and reminds me that this has been a Warning. Is the material from IM
now part
On Tuesday, December 17, 2002, at 02:54 AM, Wilfredo Sánchez wrote:
what I was thinking was that there might be an application which embeds
perl and therefore links against the perl library. A new system update
with a new perl may require that application to relink as well, if it
uses API
At 11:54 PM -0800 12/16/02, Wilfredo Sánchez wrote:
As pointed out here, if Apple upgrades perl, you have probably to
upgrade XS modules. But what I was thinking was that there might be
an application which embeds perl and therefore links against the
perl library. A new system update with a
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Sherm Pendley) wrote:
You were right. The CamelBones framework is linked against libperl, and
I've received numerous reports that CB apps continue to work untouched
after an upgrade to 5.6.1, which is binary-compatible.
An excellent reason
Mac::Carbon 0.03 is on the CPAN (er, on its way there, anyway) and
SourceForge.net.
http://sf.net/projects/macperl/
http://www.cpan.org/authors/id/C/CN/CNANDOR/
It fixes the bugs with AEDesc, POD, xsubpp, building on Mac OS X
10.1/gcc2/etc. A binary distribution for perl 5.6 is
