SAS/C HELP.ME
10 messages in this thread
Hey Now,
We just got the new SAS/C 6.0 here at Oxxi. I am excited and have begun
compiling SBase4 under 6.0. Already, I have fixed several problems
involved in `porting' C programs between 5.0 and 6.0. I like the new
options, very very nemonic {spelling?}. I like the scmsg idea, but for me
it is still just an idea. I have not been able to get it to work `worth
beans'.
I use CED version 2.12 from CygnusSoft. I know, I know, most people
reading this realize that Oxxi publishes TurboText… Why don't I use a
product that we sell? Stubbornness, I refuse to switch from the editor
that was the best at the time I started working with the Amiga.
Anyway, I want to use a function key to hit which will allow me to
recompile my project and interactively edit bugs. SAS has included some
sample scripts which I cannot seem to implement correctly.
Does anybody else out there have a CED <-> SAS/C interface running? If
you do please help me, it would make my work much easier.
Thanks,
Mike Uman
Tech Support
[]xxi, Inc. >>>
running under AutoPilot
Mike,
I'm using SAS/C with ttx, but have the same problem as you! It's my
belief that scmsg doesn't check env:sc/ files like it's supposed to. I
bet if you cd your cli before invoking your editor (from that cli), it
will build your files correctly. I've left a message to sas.c on a
user-unfriendly bbs and am waiting for some kind of response from
him/them. I'm surprised that you're the only other guy that has noticed
this glaring problem. I thought it might be my system
(A3000/OS3.0/WShell), but I don't know what's causing this problem. If
you find a cure, feel free to spread it!
// I'm gonna wait for
\X/ the A5000! <G> -RSL-
Which BBS did you leave a message on?
I've looked at the source, and I cannot find a path that does not
open the ENV:SC/SCMSG file. It does work on my system. The only
problem is that the AUTOEDIT option appears to be ignored if it's
in the options file; other than that, all options work.
Whenever you hit Right-Amiga-B to build from within SCMSG, it
reads the file ENV:SC/SCMSG and CDs to that directory. Again,
from looking at the code, there is absolutely no way that it
forks SMAKE without having read this file. Therefore, it must
be the CD command that is failing. I don't really know why that
command would fail. Can you read the contents of the ENV:SC/PROJDIR
file and let me know what's in it?
The SMAKE utility sets ENV:SC/PROJDIR any time you invoke SMAKE
from WorkBench's Build icon or from the CLI. Also, the TTX macros
set it. It sounds like there is some problem with this file.
As I said, please let me know what's in it and I'll try to
reproduce the problem.
–Doug
Doug,
I left numerous messages on B*X <g>.
I tried Right-Amiga-B to build from within SCMSG. The SMake window
came up, eventually ending with :
Error: No files to compile
Hit RETURN to exit
I checked ENV:SC/PROJDIR and it had the correct directory. I'm
including the SnoopDos output which shows that SCMSG does open
ENV:SC/PROJDIR, but the process fails at a point:
SnoopDos V1.5. Copyright Eddy Carroll, July 1992. Freely distributable.
Process name Func Filename Mode Res.
———— —- ——– —- —-
sc:c/scmsg Open env:sc/projdir OLD Okay
Background CLI Open * NEW Okay
ARexx Open sc:c/smake OLD Okay
Background CLI Load sc:c/smake Okay
sc:c/smake Open sc:c/smake.info OLD Fail
sc:c/smake Open * OLD Okay
sc:c/smake Open con:0/0/640/199/SMake/CLOSE NEW Okay
sc:c/smake Open * NEW Okay
sc:c/smake Open smake.def OLD Fail
sc:c/smake Open build OLD Fail
sc:c/smake Open smakefile OLD Fail
sc:c/smake Open lmkfile OLD Fail
sc:c/smake Open lmkfile.smk OLD Fail
sc:c/smake Open smk OLD Fail
sc:c/smake Open makefile OLD Fail
sc:c/smake Open lmkfile OLD Fail
sc:c/smake Open lmkfile.lmk OLD Fail
Background CLI Load sc Okay
sc Open * OLD Okay
<continued>
sc Open * OLD Okay
I cannot detect a CD being performed during this process. So far the
only way to have a TurboText macro build successfully, I have to CD to the
project's directory before invoking turbotext (a kludge, but workable).
If you have any suggestions, I would REALLY apreciate it! (BTW, I
checked the projdir file for extraneous newlines, or other characters, but
it is identical to the projdir generated by a successful Build by clicking
on the directory's own Build icon).
Thanks!!!
// I'm gonna wait for
\X/ the A5000! <G> -RSL-
Please post the contents of the ENV:SC/PROJDIR file. I have no
idea what is happening, but again from looking at the code there
is absolutely no code path in which the file is opened and
read successfully but no CD is done. And there is no code
path which submits the SMAKE command but does not read the
file.
Is the file locked or read protected or something?
–Doug
Doug,
The ENV:SC/PROJDIR is rather short, it is:
Zone:temp/
It isn't locked nor read protected. BTW Zone:temp is the directory
that has hello.c in it. I've tried to re-install SAS/C without any
change, I've also turned my A3000 into a vanilla version (in software
atleast) without any change either.
// I'm gonna wait for
\X/ the A5000! <G> -RSL-
Well, this has obviously gone farther than I can debug via
once-a-week messages on CompuServe. I would advise you to
contact SAS/C technical support, either by phone, mail,
or EMITS electronic mail.
–Doug
Doug:
What is EMITS electronic mail?
// -Mike Schiller
\X/ AMIGA! On AutoPilot in sunny Fort Lauderdale
EMITS is a system that allows you to send normal USENET or
INTERNET mail to support@unx.sas.com in a prespecified
format. The system automatically replies with a tracking
number that you can use in future contacts to get updates.
Tech support will contact you when the problem has been
resolved (by email again).
Details and more information on how to use it are
in the SAS/C V6.0 User's Guide, in the chapter on
"Getting Help".
–Doug
p.s. I apologize for several doubled postings, I must have
confused the offline reader somehow.