Path: utzoo!mnetor!uunet!oresoft!rick From: rick@oresoft.UUCP (Rick Lahrson) Newsgroups: comp.sys.amiga Subject: Re: Lattice C routine Message-ID: <146@oresoft.UUCP> Date: 10 May 88 16:55:23 GMT References: <197@dsacg2.UUCP> <199@dsacg2.UUCP> Reply-To: rick@oresoft.UUCP (Rick Lahrson) Organization: Oregon Software, Portland OR Lines: 29 Keywords: wont go Summary: Lattice library assumes -b, here's a workaround In article <199@dsacg2.UUCP> nor1675@dsacg2.UUCP (Michael Figg) writes: >but I keep getting an error on the compile saying > option conflict. -b option ignored >even though I am not using the -b option at all. This message is followed >later by a linkage error stating: >Error 510: _IntuitionBase symbol - Reference to unmerged data item > First Reference in Unit cxovf.o at offset 00000c20 in file 'LIB:lc.lib' > to Unit swing1.o at offset 00000010 in file 'swing1.o' >in checking the Lattice manual for this error I found a five word explanation >that said much less than what was on the screen. I don't have the manual >with me but I think it said something about an unrecognized symbol. I did >find that cxovf.o is a stack handler routine so I tried uping the stack to >20000. No go. Does this look like a problem with the library or what. And >do I have any control over this? I'm probably making myself look like a >fool again (or still) but inquiring minds want to know. I want to know. First, the -b option is now the default for compiles, so to get rid of the warning, use -b0 . The linker error message comes from the fact that cxovf (from Lattice's library) was compiled with -b. If you have the "nb" libraries on your compiler distribution disks, use them whenever you use the -b0 option. Otherwise, take a look in the source subdirectory, and you'll find cxovf.c . You can compile it with -b0, and include the result in the link. That works for me. -- Rick Lahrson ...{tektronix|uunet}!oresoft!rick Disclaimer: If I ever speak for anyone but me, I'll warn you in advance.