Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!ogicse!intelhf!ichips!iwarp.intel.com!gargoyle!chinet!miroc!caw From: caw@miroc.Chi.IL.US (Christopher A. Wichura) Newsgroups: comp.sys.amiga.programmer Subject: Re: > SAS gripes (was DICE vs GCC) Message-ID: Date: 8 Apr 91 06:47:42 GMT References: <9104021420.AA10848@thunder.LakeheadU.Ca> <1991Apr4.034920.16298@marlin.jcu.edu.au> <1991Apr4.180217.19773@nntp-server.caltech.edu> <1991Apr5.030228.28756@marlin.jcu.edu.au> <1991Apr5.173845.4404@nntp-server.caltech.edu> Lines: 54 In article <1991Apr5.173845.4404@nntp-server.caltech.edu> tll@nntp-server.caltech.edu (Tal Lewis Lancaster) writes: >cpca@marlin.jcu.edu.au (Colin Adams) writes: >Well the main reason is I am creating object files greater than 32K (actually >some are around 80K). SAS and Aztec can not handle object files > 32K. Or to >be more precise a function call to another function in the same object file must >be < 32K apart. What version of SAS are you using? I could have sworn that one of the recent ones fixed this. I specifically remember that one of the README files said the compiler would automatically generate a 32bit reference to functions that were >32k away and in the same object file. >For example, if you have the following dependency > >fish.o: spam.h > >LMK will try to compile spam.c. So you are forced to use > >fish.o: fish.c spam.h True, that one's anoying. >Also, if you have the macro > >OBJ= [ lots of files total length > 255] > >and try > >fish: $(OBJ) > blink FROM $(OBJ) ... > >This will lock up your computer and maybe even trash your hard-drive. >So you are forced to duplicate the contents of OBJ into a blink file. But you can have the LMK file do this for you easily. You'd use something like: GIFMachine: $(OBJS) BLink CAW Christopher A. Wichura Multitasking. Just DO it. caw@miroc.chi.il.us (my amiga) ...the Amiga way... u12401@uicvm.uic.edu (school account)