Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!spool.mu.edu!news.cs.indiana.edu!msi.umn.edu!cs.umn.edu!ux.acs!vx.acs.umn.edu!dhoyt
From: dhoyt@vx.acs.umn.edu (DAVID HOYT)
Newsgroups: comp.sys.mac.programmer
Subject: Re: undefined __MAIN (MacApp 2.0, C++ 3.1, MPW 3.2b8)
Message-ID: <3328@ux.acs.umn.edu>
Date: 22 Feb 91 15:56:42 GMT
References: <SCOTTH.91Feb15140128@rocco.labs.tek.com> <1991Feb18.002215.16373@jhereg.osa.com>
Sender: news@ux.acs.umn.edu
Reply-To: dhoyt@vx.acs.umn.edu
Distribution: na
Organization: University of Minnesota, Academic Computing Services
Lines: 12
News-Software: VAX/VMS VNEWS 1.3-4

>In article <SCOTTH.91Feb15140128@rocco.labs.tek.com> scotth@rocco.labs.tek.com (Scott Herzinger) writes:
>I've just gotten back into a MacApp/C++ project. MABuild has started
>to terminate due to a linker error, complaining that I haven't provided
>an entry point and that __MAIN isn't defined. This started after I first
>used MPW Shell 3.2b8 and the interfaces on the System 6.0 beta CD. But
>the problem doesn't go away when I switch back to MPW 3.1.

  I have seen this problem when -AutoBuild has been choosen.  My workaround
is to MABuild -AutoBuild to compile all of the Pascal stuff, then use
-NoAutoBuild to compile (and/or link) the application.

david | dhoyt@vx.acs.umn.edu | dhoyt@umnacvx.bitnet