Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!pa.dec.com!bacchus!mwm From: mwm@pa.dec.com (Mike (My Watch Has Windows) Meyer) Newsgroups: comp.sys.amiga.programmer Subject: Re: SAS C 5.10A has problems Message-ID: Date: 20 Jun 91 15:54:57 GMT References: Sender: news@pa.dec.com (News) Organization: Missionaria Phonibalonica Lines: 48 In-Reply-To: mykes@amiga0.SF-Bay.ORG's message of 20 Jun 91 04:37:18 GMT In article mykes@amiga0.SF-Bay.ORG (Mike Schwartz) writes: Problem #1: BLINK complains about "extern struct Custom custom;" It prints a cryptic error message like "offset too far from A4". I was able to fix it by doing "extern struct Custom far custom;" which may or may not be preferable anyway (I say it is debatable :) Many of the GfxMacros.h macros rely on this custom variable. You found and fixed the bug in your code. If you're building with the small code model (the default), you've got to declare absolute externals as "far". Problem #2: When compiling some sources, I get CXERR: 99, which is NOT documented in the manual. That's an internal compiler error, not an error in your code. There are good reasons for it not being more descriptive (for instance, they can't point at anything in your code and say that that caused the error). You should contact SAS tech support. Problem #3: When compiling various sources, I get "Invalid section type in memory option" error message. I could find no documentation for this error message... I haven't seen this one, but it looks like you're feeding the compiler invalid options. If you post the code (and compiler options and applicable SASCOPTS file), doing a better diagnosis might help. Then again, if you're going to call SAS about #2, you might ask about this on at that time. SAS has the best technical support I've seen in any company large enough to have a receptionist. You paid for it when you bought the compiler; you should us it. Unhappily working in C, I'm unhappy working in C, too - but not as unhappy as when I'm working in assembler. However, I don't assume that every message from the language translator that I can't figure out is a compiler bug.