Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!topaz!uwvax!uwmacc!aaron
From: aaron@uwmacc.UUCP (Aaron Avery)
Newsgroups: net.micro.amiga
Subject: Re: printf does not take 10K
Message-ID: <35@uwmacc.UUCP>
Date: Fri, 27-Jun-86 02:21:50 EDT
Article-I.D.: uwmacc.35
Posted: Fri Jun 27 02:21:50 1986
Date-Received: Sat, 28-Jun-86 04:19:02 EDT
References: <8606242147.AA12273@pavepaws> <556@3comvax.UUCP>
Reply-To: aaron@uwmacc.UUCP (Aaron Avery)
Organization: National Magnetic Resonance Facility at Madison
Lines: 21

In article <556@3comvax.UUCP> mykes@3comvax.UUCP (Mike Schwartz) writes:
>OK, so why does Lattice generate such large programs?  Well, the answer
>is simple, and it sux having to deal with it by going around it, but...
>
>The cause is in their c.c, or startup.obj module.  You see, they call exit()
>after the user main() returns, and exit() references a lot of other library
>routines that get dragged in and waste space.  After using Manx for 5 months,
>
>Good luck!

I haven't tried it yet, and I'm probably totally off base, but replacing
the exit() call in c.c with the AmigaDos Exit() call may (will) shorten
things up, but I doubt it would work. People have said that they have used
Astartup.obj and then put amiga.lib before lc.lib in the command line, but
when I do that, I get unresolved variables in lc.lib. If I omit lc.lib
completely, I get unresolved vars in Astartup.obj. I think it doesn't work
if I put lc.lib first, either. Any ideas?

Aaron Avery ({seismo,topaz,caip,allegra,ihnp4}!uwvax!uwmacc!aaron)
            (aaron%maccunix@rsch.wisc.edu)
            (aaron@unix.macc.wisc.edu)