mqh@batcomputer.TN.CORNELL.EDU (Mike Hojnowski) (09/26/86)
Hello,
I have the Developers C, and I'm having trouble with link68. I just
paid $20 for the new release of the C compiler, and I thought that the
"path names" bug was supposed to be fixed in it. Either it isn't, or
I'm doing something wrong. What I want to do is:
link68 [options] x.68K=a:\lib\gemstart.o,x.o,a:\lib\gemlib...
This doesn't work. Am I doing something wrong, or wasn't it fixed?
I think someone posted a zap to the linker program to fix this bug.
I didn't grab it 'cause my check was in the mail, and I didn't think
I needed it. If link68 really is still busted, can someone please send
me that zap?
--
Mike Hojnowski (Hojo) {ihnp4,rochester}!cornell!batcomputer!mqh
(607) 257-1389 (h) mqh@tcgould.tn.cornell.edu
(607) 255-4812 (w) mqh%batcomputer@crnlcs.bitnet
"..Oh, that's disgusting, isn't it?" - Brundlefly, The FlyLynn%PANDA@SUMEX-AIM.STANFORD.EDU (Lynn Gold) (09/27/86)
Return-Path: <@SUMEX-AIM,@SU-SCORE.ARPA:info-atari16-request@score.stanford.edu>
Received: from SUMEX-AIM by PANDA with Cafard; Fri 26 Sep 86 20:52:52-PDT
Received: from SU-SCORE.ARPA by SUMEX-AIM.ARPA with TCP; Fri 26 Sep 86 20:34:55-PDT
Received: from ucbvax.Berkeley.EDU by SU-SCORE.ARPA with TCP; Fri 26 Sep 86 07:43:05-PDT
Received: by ucbvax.Berkeley.EDU (5.53/1.17)
id AA16309; Fri, 26 Sep 86 07:12:13 PDT
Received: from USENET by ucbvax.Berkeley.EDU with netnews
for info-atari16@score.stanford.edu (info-atari16@score.stanford.edu)
(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 26 Sep 86 04:18:51 GMT
From: mqh@tcgould.tn.cornell.edu (Mike Hojnowski)
Organization: Theory Center, Cornell U., Ithaca NY
Subject: LINK68 doesn't take path names .. Wasn't this fixed?
Message-Id: <1105@batcomputer.TN.CORNELL.EDU>
Sender: info-atari16-request@score.stanford.edu
To: info-atari16@score.stanford.edu
Hello,
I have the Developers C, and I'm having trouble with link68. I just
paid $20 for the new release of the C compiler, and I thought that the
"path names" bug was supposed to be fixed in it. Either it isn't, or
I'm doing something wrong. What I want to do is:
link68 [options] x.68K=a:\lib\gemstart.o,x.o,a:\lib\gemlib...
This doesn't work. Am I doing something wrong, or wasn't it fixed?
I think someone posted a zap to the linker program to fix this bug.
I didn't grab it 'cause my check was in the mail, and I didn't think
I needed it. If link68 really is still busted, can someone please send
me that zap?
--
Mike Hojnowski (Hojo) {ihnp4,rochester}!cornell!batcomputer!mqh
(607) 257-1389 (h) mqh@tcgould.tn.cornell.edu
(607) 255-4812 (w) mqh%batcomputer@crnlcs.bitnet
"..Oh, that's disgusting, isn't it?" - Brundlefly, The Fly
*******
The linker reads backslashes as comment characters.
Looks like THAT bug didn't get fixed with this release...
--Lynn
-------sansom@trwrb.UUCP (Richard Sansom) (09/27/86)
Here's the "zap" you requested: >Trying to overcome the problem with LINK68 not accepting pathnames I found >a scanner control table starting at file-offset 0x8144. >The command scanner of LINK68 uses a byte entry of this table indexed by an >input character as a control pattern specifying the character class. > >The backslash entry at file-offset 0x81A0 has the value 0x02 which is a >separator pattern. >Patching it to value 0x04 puts the backslash into the number class. >After this fix LINK68 treats the backslash as a normal identifier character >but GEMDOS still sees a pathname. > > Konrad Hahn > Techn. University Darmstadt > Dept. of Computer Science (Datentechnik) > Merckstr. 25, D-6100 Darmstadt, W.-Germany __________ ______ ____ _____ ___ /_________//___ ||__|/____|/__/ Richard E. Sansom ___ ____/ / ____________ TRW Electronics & Defense Sector / / / /\ < | /| / One Space Park Drive, R3/1028 / / / / \ \ | / | / Redondo Beach, CA 90278 /__/ /__/ \__\|__/ |__/ {...decvax,ucbvax,ihnp4}!trwrb!sansom