Re: [MacPerl-Porters] Re: gLastMacOSErr?

[Matthew Langford <langfml [at] eng [dot] auburn [dot] edu>]

On Thu, 22 Jun 2000, Peter Prymmer wrote:
> Matthew Langford wrote: Wed, 21 Jun 2000:
> 
> > What should I have {MW68KIncludes} set to?
> > Ditto for {MWPPCIncludes}...
> 
> It could very well be that the test for those variables is incorrect
> in assuming that their presence indicates anything about the quality of
> the MW installation.

Okay.  Here's the scoop:  as of CW Pro5, the variable to look for is
{CWANSIIncludes}, or if an older system of duplicate headers is used,
{MWCIncludes}.  (These are mentioned at the bottom of the standard
MacPerlConfig.mk.)  I can forward you a copy of both my
UserStartup*Metrowerks files, if you wish, to see what env.variables are
getting set.


> Unfortunately, it will take me more than a week to get back to MacPerl
> hacking to offer any advice or fixes as I am in the midst of
> moving/work-stuff/etc.

I can sympathize, since I just finished moving/work-stuff/etc.  Well, the
work-stuff is on-going, but anyway...

> If you can work past the trouble that Configure.MPW is throwing at you
> (that is, hand edit a MacPerlConfig.mk appropriate to your compiler)
> then do a build OK (or at least up to the x2p stuff) then that would
> prove that checking for {MW68KIncludes} and/or {MWPPCIncludes} is
> unnecessary.

Okay, the reason I tried running Configure.MPW in the first place was that
gLastMacOSErr is an undefined identifier, according to the compiler.  I
see places where through various preprocessor gyrations it is declared as
"extern".  Is there someplace where it is defined outright?  How have
others fixed this error, in getting MW to compile MacPerl?

Seems like I've seen an error like this before, but I can't recall what
happened.

--
MattLangford 


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