Re: [MacPerl-Porters] What can MacPerl bring to Mac OS X (Server)?

[Matthias Neeracher <neeri@iis.ee.ethz.ch>]

In article <000224132833.be30@forte.com>, PVHP@forte.com writes:
> Jefferson R. Lowrey wrote:
>> At 9:32 PM +0100 2/24/00, Matthias Neeracher wrote:
>> <snip>
>> > - Specifically, last year I ported some of the MacOS Toolbox modules as
>> >   dynamic libraries on MacOS X with Carbon and ran them WITH THE STANDARD
>> >   BSD-style perl version shipping with MacOS X. This worked quite well
>> >   (considering my total inexperience at the time).
>> 
>> Do you have any notes you can make available from this experiment?

I'll probably repeat it soon to see what has changed since then.

> I think you are missing these types of files from e.g. perl 5.5.600:

> $ grep rhapsod MANIFEST
> ext/DynaLoader/dl_rhapsody.xs   Rhapsody implementation
> hints/rhapsody.sh       Hints for named architecture

> it should build out of the box unless recent changes to the perl source have
> mucked up the port (which is possible).

Not only does perl itself build out of the box, it is shipped pre-installed.
What we're discussing here is the Mac:: hierarchy of modules.

Matthias

-- 
Matthias Neeracher   <neeri@iis.ee.ethz.ch>   http://www.iis.ee.ethz.ch/~neeri
  "And that's why I am going to turn this world upside down, and make
   of it a fire so *bright* that someone real will notice"
                                -- Vernor Vinge, _Tatja Grimm's World_

==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-porters-request@macperl.org