Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!apple!oliveb!amiga!cbmvax!valentin
From: valentin@cbmvax.commodore.com (Valentin Pepelea)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Sample printer driver
Keywords: rkm manx printer driver
Message-ID: <9388@cbmvax.commodore.com>
Date: 19 Jan 90 08:39:53 GMT
References: <25ea02JB80q901@amdahl.uts.amdahl.com>
Reply-To: valentin@cbmvax.commodore.com (Valentin Pepelea)
Organization: Commodore, West Chester, PA
Lines: 24

In article <25ea02JB80q901@amdahl.uts.amdahl.com> dwl10@uts.amdahl.com
(Dave Lowrey) writes:
>
>        XREF    _PrinterSegmentData
>
>The linker can't resolve this reference. Since the code makes no
>reference to this label, I just took out the XREF.

Either this will not hurt at all, or you forgot add a file to the compilation
process.

>Second, I am using Manx to compile the C code. What compile flags
>do I need to use? I have use +p +B +D +C, and all I get is a visit
>from the GURU (codes 0000000A or 00000004). The Lattice flags
>that they say to use are -b0 -d0 -v.

-b0:	Use absolute addressing. (full 32-bit pointers for all data references)
-d0:	Don't add any debugging information
-v:	Don't add any stack checking code

If you don't set the equivalent of -v and -b0 with the Manx compiler, you are
guaranteed to get Guru's all the time.

Valentin