Thread View: comp.sys.amiga.tech
3 messages
3 total messages
Started by markv
Wed, 05 Dec 1990 18:29
SAS 5.1 Bugs
Author: markv
Date: Wed, 05 Dec 1990 18:29
Date: Wed, 05 Dec 1990 18:29
22 lines
1583 bytes
1583 bytes
I have found a bug/problem with the 5.10 BLink. (Havn't yet had the
time to call SAS yet).
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.
I've also noticed another problem that I can't realiably reproduce,
but LMK 5.1 seems to occasionally truncate command line args to 80
chars and then try to execute the leftovers as another command.
(AmigaDOS doesn't know what to make of "BUFSIZE 1024 VERBOSE NODEBUG" :-).
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Re: SAS 5.1 Bugs
Author: Jean-Michel Forgeas
Date: Fri, 07 Dec 1990 11:46
Date: Fri, 07 Dec 1990 11:46
24 lines
1651 bytes
1651 bytes
In article <27258.275ce81c@kuhub.cc.ukans.edu>, markv@kuhub.cc.ukans.edu writes:
> 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
Note that I link with lib:astartup.obj (not c.o) and with amiga.lib
before lcnb.lib
Do you link with lc.lib before amiga.lib? If yes perhaps the problem is
into lc.lib?
--
\___/
Jean-Michel Forgeas \-/
cbmvax!cbmehq!cbmfra!swinjm!forgeas | The Software Winery
-^-
And, where is the universe ?
Re: SAS 5.1 Bugs
Author: markv
Date: Mon, 10 Dec 1990 17:20
Date: Mon, 10 Dec 1990 17:20
41 lines
2338 bytes
2338 bytes
>> 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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads