Google
 

Trailing-Edge - PDP-10 Archives - SRI_NIC_PERM_FS_1_19910112 - c/kcc5/buglnk.txt
There are no other files named buglnk.txt in the archive.
 2-May-88 15:00:36-PDT,569;000000000011
Mail-From: MIMI created at  2-May-88 14:14:38
Date: Mon, 2 May 88 14:14:37 PDT
From: Mimi Recker <Mimi@SRI-NIC.ARPA>
Subject: linker/cc question
To: klh@SRI-NIC.ARPA
Message-ID: <12395186788.27.MIMI@SRI-NIC.ARPA>

Ken, I have a .cmd file called <nicprog>hstreg.cmd that i just "take"
to compile the hstreg program.  I works fine if I am connected to nicprog:
but if I am connected elsewhere with another (local) version of hstreg.c
and "take nicprog:hstreg.cmd" I get a linker error:  
	%LNKCOF  Cannot open file DSK:IDBSUP.REL

do you know why?
-------
 2-May-88 16:06:28-PDT,745;000000000001
Mail-From: KLH created at  2-May-88 15:06:26
Date: Mon, 2 May 88 15:06:26 PDT
From: Ken Harrenstien <KLH@SRI-NIC.ARPA>
Subject: Re: linker/cc question
To: Mimi@SRI-NIC.ARPA
cc: KLH@SRI-NIC.ARPA
In-Reply-To: <12395186788.27.MIMI@SRI-NIC.ARPA>
Message-ID: <12395196222.40.KLH@SRI-NIC.ARPA>

It looks like KCC is not passing along the "n:" part of the args when it
gives them to LINK.  In general, MACRO and LINK cannot handle directory
names, which is why KCC doesn't bother.  But they do use logical names
(the crock DEC invented to make TOPS-10 software work on TOPS-20) and
I guess KCC should understand that.  For the time being you'll have
to connect to the directory those .REL files are in; I'll fix the
bug later.
-------