Hello Olin & PIC.ers, >jsand wrote: >>> If you put macros in a separately assembled file, then how did you >>> not get assembly errors in the other source files every time you >>> tried to use a macro? > >> >> Sure, I had errors all over the place. > >Argh! > > >You neglected to mention this little tidbit when asking for help regarding >linker problems. If you had bothered to chase down just one of those >errors, you would have found the problem. > >NEVER IGNORE COMPILE/ASSEMBLY ERRORS. These must always be >fixed first. >Asking 2000 people why there was nothing in the linker output when you had >assembly errors "all over the place" is not only stupid, but so >irresponsible as to be rude. > ..er.. Olin, I certainly didn't intend to be rude or irresponsible at all. There is a lot I _didn't_ include in my original query. If I had been more comprehensive, the query would have grown to an unreadable size & attracted endless complaints about verbosity. The quantity of errors showing in the output -and their apparant diversity- gave me little clue as to the cause (& I _did_ spend immense unsatisfactory time trying to `chase them down'). I wouldn't expect you or any other lister to pore over these and spend their own valuable time trying to solve my problems. I was merely looking for directions, and did receive valuable ones. This BTW after trawling through every piclist.com FAQ, uchip forum, private pic.ery archives and old listings, dead-tree library, the lot. In the original query I did indeed post an output screen that showed _no_ errors at all. I should elaborate here for clarity, because if _I_ could get caught by this, I s'pose a lot of other people will too. Well, just maybe everyone out there already knows all this obvious linker and relocatable code stuff so didn't bother to reply to such a trivial query. In the event it was only the heavy hitters who came up with any leads. When I compiled with 3 source files, namely Main.asm Maths.asm macros.asm I was shown: `no errors' - `build succeeded' etc. However, the .map and .lst files were full of emptiness. Any attempt to replace the macro.asm file with in-source macros (in main.asm or maths.asm) just created a welter of errors - hundreds, such as Warning[207] C:\SERVCDAT\PICSORCE\PAT2001\CUBE&BEAM\MONITOR\C&B_MON.ASM 2860 : Found label after column 1. (WRITE_LCD) Error[116] C:\SERVCDAT\PICSORCE\PAT2001\CUBE&BEAM\MONITOR\C&B_MON.ASM 2860 : Address label duplicated or different in second pass (WRITE_LCD) .. ad nauseam Hitting them with repairs just sent me round in circles for hours. It couldn't solve the problem - and the problem pointed to the existence of macros. Now with the benefit of hindsight (always 20/20) I can tell you all this. Before I slew the lion, I couldn't have provided it without blizzarding the poor list members. They'd really have loved it. Which brings me to my remaining point, I _could_ have just thanked the contributors for their assistance - "thanks guys" and just moved on. I wrote my last mail detailing what I had so painfully discovered, in the belief that it ought to be included in a FAQ (James, are you out there?). That way, this thread could become a net-sum-gain for the pic community as a whole. My SA 2 cents worth. best regards, John email from the desk of John Sanderson. JS Controls, PO Box 1887, Boksburg 1460, Rep. of S. Africa. Tel/Fax 011 893 4154, Cell 082 741 6275, web http://www.jscontrols.co.za Manufacturer & purveyor of laboratory force testing apparatus & related products & services. -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics