Re: [MacPerl-Porters] New MacPerl build system now available!

[Prymmer/Kahn <pvhp@best.com>]

On Thu, 27 Apr 2000, Matthias Ulrich Neeracher wrote:

> Prymmer/Kahn <pvhp@best.com> writes:
> >Report on the kit that was posted:
> >
> > In installing GUSI and SFIO I apparently made the mistake of 
> > double clicking on the Install_{product}.MPW script which set
> 
> Hmm, I'll have to guard against that possibility.
> 
> > Correct approach(?): I guess I should have directory'ed to the
> > GUSI dir then run the script then directory'ed over to SFIO and
> > run that script (?).
> 
> Yes, that was the idea.

OK.  It could be that a documentation clarification is
all that is needed.

> >where I noted that even if I had removed 68K and PPC from the 
> >MacPerlConfig.mk file the first line spat out by dmake is a
> >MWLInk command for the MW build portion - odd.
> 
> I forgot about the build of Unpreload. That tool is so trivial that I'd
> best replace it with a shell script.
> 
> >(It does BTW look like the MacPerlConfig.mk could be generated by an
> >MPW script :-)
> 
> That's the eventual plan. I vaguely remembered your effort to write a
> configuration script and thought I'd write something that could potentially be
> machine generated.

Yes that one is simple.  I don't think my build got far enough to
generate Config.pm though.  It is considerably tougher keeping
a non Bourne shell config.sh generator in sync with Configure.
It should be quite straightforward to have an MPW script write
MacPerlConfig.mk.

> >At any rate, if I select from either the SC portion on down or the MrC 
> >portion on down of the dmake output the compilers warn
> >with messages such as these from MrC:
> >
> >}
> >^
> >File ":SubLaunch.c"; line 243 #Warning 30: implied return at closing '}' of Va
> lidateFeatures does not return value
> 
> I sometimes write sloppy code...
> 
> >}
> >^
> >File ":crypt.c"; line 317 #Warning 30: implied return at closing '}' of permut
> e does not return value
> >#-----------------------
> 
> .. but then, so does UCB :-)
> 
> >#Standard input; Line 2; ### Rez - Warning: No resources read by include state
> ment from file "miniperl.SC".
> 
> Yeah, only the MW build uses data resources. The warning is harmless.
> 
> >### MPW Shell - Command "UnPreload" was not found.
> 
> That's the tool where I only had a MW build. You can safely replace it with an
> empty text file.
> 
> >miniperl -e 'printf("%s %vd\n",$^O,$^V)'
> >MacOS 5.6.0
> >
> >Whoo hoo!
> 
> Cool! Did you ever try the old build system?

I had tried it on a quadra (that is now out of commission).  Unfortunately
I never had all the pieces of MW + MPW environment set up properly to
get very far in the build.  The new kit is _amazingly_ simple though.

> >This was BTW Mac OS 9, MPW Gold Master from Feb 2000, BuildCommands and 
> >BuildProgram scripts replaced with the ones included in the dmake kit.
> 
> Oh yes, I should have mentioned that.

It is mentioned in the README for dmake.  I mentioned it on this list in
order to help others.  BTW I noted a problem with a second double forward
slash in the README.html that was included with the kit, and while
exploring the ftp site I noted that the XL.info and GUSI.info files might
be of interest to folks who want to build at home.  Hence I have a revised
README.html at:

  http://www.best.com/~pvhp/mac/macperl5.6.0/README.2.html

but the latest GUSI and XL packages apparently ought to be picked up
from the macos/src/mpw_c/ directory ftp://sunsite.cnlab-switch.ch/
(which was where I obtained my versions) but the *.info files
are in the /mw_c/ directory.  Perhaps those introductory/informational
files could be copied or linked over to the mpw_c directory?

> >I had not set the MPW memory to anything.  That isi,B I simply left it at
> >the default.
> 
> That works for miniperl, but might fail for perl itself.

Thanks for the tip.  I did note that there was trouble with a space
in the volume name as handled by the makefile.mk.  I think that it
was the handling of the {PWD} variable at the very top of the Makefile.
I worked around it by renaming my drive from 'Jellyfish HD' to
'Jellyfish'.  I think that adding the proper quotation marks to {PWD}
will help, but I have yet to try that out with a test build.

Peter Prymmer



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