CompuServe Thread

#Laticce C Patch 5.10B

9 messages in this thread
#18704From: John ParkerJan 4, 1992 8:12 PM
I am trying to patch my Lattice version 5.10a to 5.10b using the patch SAS51B.LZH. The patch gets most of the way through but hangs up with the following: patching lc:/compiler_headers/stddef.h lcompact: unknown command failed return code 10 Looking at the install_hd script, this is the first location where "lcompact" is mentioned. I am having abit of trouble following through to see what the problem is. I do not recall having a directory of that name used by the compiler. Any thoughts ?
#18711From: John Toebes/SYSOPJan 4, 1992 9:24 PM
You should have a copy of Lcompact in your LC: directory. If not, go back to your original 5.xx disks and grab a copy of lcompact off disk 1 and put it in LC:. I would suspect that you might have deleted it one time by accident or you could have encountered a problem in one of the updates along the way. John A. Toebes, VIII – via Whap!
#18778From: Shawn RandolphJan 6, 1992 10:49 PM
I don't think so, I am haveing the same problem and what I get is lcompact is not an object module. The problem here is that I need the infamous "EXECUTE" statement, but when I tried to execute lcompact it bombs with the same statement. I think this is a bug from SAS because my patch disks come directly from them and I get a similar error. The biggest pain is that the patch has already run its course on most of you major executeables so when you try to run the patch again, big bomb out it the beginning because an incorrect version has been detected ("I wonder why")….. Any other ideas??? Shawn >>>—Manassas—>>
#18782From: Don Curtis/SYSOPJan 7, 1992 12:23 AM
Shawn, you cannot EXECUTE LCOMPACT since lcompact isn't a script file. lcompact is an executable file. Try listing it (LIST LC:LCOMPACT) and it should have it's execute bit set. Don
#18805From: John ParkerJan 7, 1992 7:26 PM
Ahhh…I discovered the problem. I do have lcompact in my directory but the problem was this. I was running the update from ClickDos II and I discovered that when I start a shell internal to ClickDos, the original path is not used, so as far as the system knew, lc: did not exist. When I ran the update using a Workbench shell, everything went fine. When i do a "path show" using ClickDos, only c: comes up. Thanks
#18809From: John Toebes/SYSOPJan 7, 1992 8:28 PM
Great. I am glad to see that you got it resolved. John A. Toebes, VIII – via Whap!
#18811From: Shawn RandolphJan 7, 1992 8:49 PM
You're definitly right, lccompact is not an executeable, However, I am not running the update from ClickDos II and I still suffer from the same "Unable to load lcompact: file is not an object module." I misunderstood what this was saying. Unfortunatly after my 3rd reload of all of Lattice C once again everything still fails, even with the "e" bit set and a copy of lcompact residing in virtirually every location I could think it would look for it…..Oh well it looks like another call to SAS is in order, or maybe you have some idea what is the prob? Shawn >>>>—–Manassas—>>
#18823From: John Toebes/SYSOPJan 8, 1992 6:44 AM
Have you tried running it from a normal shell? One thing that you can try is to BOOT from the SAS/C disks and see if you can run the update that way. If not, it does seem that a call to SAS/C tech support is the best method. John A. Toebes, VIII – via Whap!
#18881From: Shawn RandolphJan 9, 1992 9:35 PM
Thanks but I suceeded in patching my compiler by patching a copy of my system diskettes and then reinstalling my files. Kind of a goofy way to go about fixing a hd install program, but it works so way complain (right?)…… Thanks anyway Shawn >>>—Manassas—>>