Peck@RADC-MULTICS.ARPA.UUCP (03/03/87)
Thanks for all the replies about what the major ST PD software
producers are using. I've recently received Pcommand (which is adequate
for a cli I suppose...the price is right.) and I ftp'd make from
su-score. Make seems to be just about what I've been looking for, but I
have ABSOLUTELY no idea where to get any documentation for it. If
anyone has the man file from Un*x for make, could you mail it to me? I
got the beast to run on my machine (1040 w/ one drive (the builtin one)
and a 500k eternal ramdisk.) I had all the bin files in C:\bin\ (the
ram disk) and the libraries on the floppy (they're pretty big and only
needed for linking). Anyway, the make program goes thru fine, and
compiles the files and makes a whole lot of .o programs, then tries to
link them, and finishes linking without errors, then does the relmod
without errors, and results in a make.prg. the problem is that when I
run this new make.prg, NOTHING happens. It loads, then returns to the
cli or the desktop. I remember reading about someone having problems
with make earlier, is this related to that? What was the solution?
Maybe I should compare the sources of my files with the originals...
rodneyPeck@RADC-MULTICS.ARPA.UUCP (03/08/87)
|From: Mark Alexander <sun!drivax!alexande at UCBVAX.BERKELEY.EDU> |>the problem is that when I run this new make.prg, NOTHING happens. |What is is happening is that when you run the new MAKE, it finds |that there is nothing to do (because you recently ran MAKE), so it |exits. Right. Unfortunately, it still doesn't work. If I rename make.prg to m.prg, and run the m.prg program, it will make a new make.prg. If I rename this make.prg, and run it, it will look briefly at drive a: and then return to the cli without saying a char. The version which I didn't compile (x'd from the arc) say's make.prg is up to date when I run it after running it once. this makes sense. The compiled version I made doesn't. I'm using the Alcyon C compiler which got bought last December. What's the story with the patches for this system anyway? I've got a file which has a wildcard expansion patch for the xopen.o file in gemlib, a rewrite of ___bdos which says it corrects a problem where the trap #2 is a noop. I haven't installed either of these, (they're rather confusing) but might the second (the trap 2) explain why I don't get any output?? Do the standard printf functions use this section? I couldn't get printf to work. thanks, for all the help, I'm nearly there...one more round of help should do it. rodney Peck@Radc-Multics.ARPA