its icon indicating copy to clipboard operation
its copied to clipboard

Build of EAK;TS BEAR gives errors in FSCOPY

Open eswenson1 opened this issue 2 years ago • 3 comments

I didn’t notice errors on ES building EAK;TS BEAR, but the GitHub build shows 3 undefined variables.

eswenson1 avatar Nov 19 '23 03:11 eswenson1

I used an older version of EAK;FSCOPY 38 and this one allows EAK;BEAR 9 to assemble cleanly. However, there are quite a few differences between EAK;FSCOPY 38 and EAK;FSCOPY 46 (and EAK;FSCOPY 41) and it seems there are some bugfixes in EAK;FSCOPY 46 as well as changes. So I'm not sure what the best thing to do here is.

I note that the version of FSCOPY in SYSENG is the same as the one in EAK;FSCOPY 46.

eswenson1 avatar Mar 10 '24 02:03 eswenson1

I don't see any FSCOPY in SYSENG. I also don't see anything else using FSCOPY than BEAR.

Maybe a solution could be to move FSCOPY 46 to SYSENG. DUMP mentions that there should be a copy there. And then EAK could have FSCOPY 38 and have BEAR use that.

larsbrinkhoff avatar Mar 10 '24 10:03 larsbrinkhoff

I had FSCOPY 46 in SYSENG on ITS. It probably got there from the PI distribution or I put it there ages ago because some program’s assembly required it.

However, assembling any program that includes FSCOPY 46 gets three undefined references: KL10, BVAL, and EVAL. I don’t know why. I reverted to an old version of FSCOPY in EAK and now BEAR assembles cleanly. I’ll commit that change soon.

eswenson1 avatar Mar 10 '24 15:03 eswenson1