🚀 go-pugleaf

I've recently converted my application to using overlays, and they are
working great!  I'm having problems creating a debugging version of my code.

Here's a summary of what's going on.  My BCC options are:
-2 -c -B -d -H -ml -M -Vs -w -Y -Z [plus a few -w???s]

The -B, -Y and -Vs were suggested by my GUI library vendor (Zinc).  I
don't understand why I need the -B.  It seems to be causing me
problems when it comes to making the debug version of my code -- more
details follow.

My TLINK options are:
/c /s /A=16

I build the whole app w/o debugging code (400K .EXE).  I delete the
three .OBJs that I want to debug, and rebuild by adding -v to the BCC
line and /v to the TLINK line.  I get an "Out of memory" error from
TASM (which was started with the -B).  

OK, so I try it without the -B, and everything compiles, but the
linker gives 3 "No stub for fixup" warnings.  It gives this warning
twice for one of the modules I want to debug, and once for another.

What does the -B have to do with it?  There's not a whole lot of
documentation on what it does, just that it calls the assembler for
inline assembly.  Well there IS NO INLINE ASSEMBLY in my code!

I just got my program compiling in debug mode by using -ETASMX
-Tkh20000 to tell it to use the EMS version of TASM with extra room
for symbols.  So I've got a work-around, but I need to understand what
-B is doing.  Any help would be greatly appreciated.

    	    Phil