Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbfsb!cbnewsc!gregg From: gregg@cbnewsc.att.com (gregg.g.wonderly) Newsgroups: comp.sys.amiga.programmer Subject: Re: > SAS gripes (was DICE vs GCC) Message-ID: <1991Apr9.163520.25545@cbnewsc.att.com> Date: 9 Apr 91 16:35:20 GMT References: <1991Apr8.162329.29538@kuhub.cc.ukans.edu> Organization: AT&T Bell Laboratories Lines: 46 From article <1991Apr8.162329.29538@kuhub.cc.ukans.edu>, by markv@kuhub.cc.ukans.edu: > In article , colin_fox@outbound.wimsey.bc.ca (Colin Fox) writes: >> Yes, it is a known bug with BLink that you only have a 256 character command >> line. SO what you should do instead is create a temporary link file, which is >> done like this: >> >> target: obj1.o obj2.o obj3.o >> blink > FROM c.o obj1.o obj2.o obj3.o >> TO target >> smallcode smalldata nodebug >> < >> >> And you don't need to create a link file. > > Huh? I dont recoginize this construct. I've hunted the docs for an > "implict" temp file, but havnt' found it, could you point me at a page > number? Beware that intermediate files have at the end of the lines (left over from MSDOG). Also, there is a limit on the number of libraries that BLINK will accept, but not .o's. I took a program which was 15 or so source files of about 1000 lines each, and shred(1)'d them into separate directories and then compiled them each separately and then combined each group into a library. The result was that blink could not groke all of the libraries, so I had to change some back to .o's. There are numerous other things wrong with larger environments. I understand that a version 6 of the C compiler tools will be forthcomming at the end of '91, with several tools completely rewritten. Also, it is not intended that you do cd's from within one of the implicit temp files. Evidently, LMK has some locks that will cause problems if you try it (don't know why, that is just what they told me). I wanted to have an LMK file that would cd to each directory and make the library there, but had to revert to just using a make(1) program that I picked up somewhere ages ago (not trusting lmk). The problem now with all of the libraries is that I can not compile with DEBUG because the libraries get too big (>256K). I can't compile just the modules that I want to debug with DEBUG either because CPR will barf with some kind of error, evidently confused with only finding some symbols in the symbol table (when it does this it leaves a lock on the executable). -- ----- gregg.g.wonderly@att.com (AT&T bell laboratories)