🚀 go-pugleaf

>> I have found a bug/problem with the 5.10 BLink.
>>
>> I have a program that uses the _custom data object.  (taken from
>> amiga.lib).  The problem is if I link with BLINK 5.1, I get
>> an error that "_custom" is unresolved with either the 2.0 or 1.3
>> amiga.lib.  If I link with BLINK 5.05 all is well eith either amiga.lib.
>>
>> Mark Gooderum                 /\     \ | /     H a p p y
> 
> I don't think its a problem with blink since I tried to access custom
> and did not have any error nor warning. Here are compiler options I use:
>     lc -s -b0 -ccstq -v -qRAM -HLCI:includes.q

Hmm.  I am using -b1 -rr -ccfiq -v.  Maybe LCX is having progblems
generating references to _custom in b1.  I'll try modifying
graphics/gfx.h to declare "extern struct custom __far custom".

> Note that I link with lib:astartup.obj (not c.o) and with amiga.lib
> before lcnb.lib

Hmm.   I can't do this because I am using lattice stdio and FILEs so
lcr.lib has to come before amiga.lib (I also put in lc.lib to catch
any std C functions that I missed prototypes for...).

> Do you link with lc.lib before amiga.lib? If yes perhaps the problem is
> into lc.lib?

Doubtfule.  lcxxx.lib shoulnd't effect this error since.  I suspect it
is either lc or blink.  

For now,

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mark Gooderum                 /\     \ | /     H a p p y  
Academic Computing Services  / v\   -- * --         H o l i d a y s ! :-)
University of Kansas        /v  v\   / | \    ///
                           /__v___\   Only  ///  /|         __    _  
Bitnet:   MARKV@UKANVAX       ||     \\\  ///  /__| |\/| | | _   /_\  makes it
Internet: markv@kuhub.cc.ukans.edu     \/\/  /    | |  | | |__| /   \ possible
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~