Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!uokmax!servalan!epmooch!ben From: ben@epmooch.UUCP (Rev. Ben A. Mesander) Newsgroups: comp.sys.amiga.tech Subject: BLINK problems with SAS/C 5.10? Message-ID: Date: 18 Dec 90 21:08:21 GMT Lines: 14 I'm working on a program that has 135 source modules. When I compile it with SAS/C 5.10, with no compiler options it will link just fine. When I compile it with the -d5 option turned on, so I can debug the sucker, BLINK is reporting certain modules are not found... What's the deal?? Is the -b0 required? I thought the linker would automagically insert ALVS wherever required to get to routines that were >64K away from the caller? Is that what the problem is here? Anyone else seen this behavior? -- | ben@epmooch.UUCP (Ben Mesander) | The compiler crawls | ben%servalan.UUCP@uokmax.ecn.uoknor.edu | Like a senile snail | !chinet!uokmax!servalan!epmooch!ben | I whine loudly. (From "The Ben of Programming")