Grex Info Conference

View Responses

Grex Info Item 227: Help me compile now or DIE!
Entered by orinoco on Mon Apr 10 16:13:00 UTC 1995:

ok,i need help on how to compile stuff....mailed popcorrn andshe said to 
enter an item here.....so...
HOW DO YOU COMPILE???
thonk you,
  orinoco

18 responses total.

#1 of 18 by robh on Tue Apr 11 00:18:19 1995:

Well, I was going to answer, but the item text and topic are
far too rude in their current state.  Forget it.

#2 of 18 by davel on Tue Apr 11 11:30:47 1995:

I agree, but ... you *could* always try     man -k compile   to see if you
can find any relevant man pages.  Then read them.  It's going to depend on
what you want to compile, at the very least, so you're in a better position
than any of us are now to get answers.

#3 of 18 by anemone on Tue Apr 11 12:53:19 1995:

c'mon, robh, be a good sport.
I think the title was kinda' cute!
But, if you insist, I will phrase the question for orinoco in a more polite
manner.  Here goes:

"orinoco has been trying to find out how to compile a program for a long time.
When he talked to popcorn, she told him to ask all of you on the info .cf.
Will anybody here tell poor, poor orinoco how to compile?"

Was that better?

#4 of 18 by popcorn on Tue Apr 11 13:20:58 1995:

This response has been erased.

#5 of 18 by orinoco on Tue Apr 11 15:25:01 1995:

I am trying to compile the strfile program....it has the .c suffix so i assume
that it's in C.... it's on grex..... Here's what I tried, tell me what i'm
doing wrong.... cc /usr/local/grexsrc/strfile/strfile.c -o/u/orinoco/strfile.o

according to the manual that *should* compile the program
/usr/local/grexsrc/strfile/strfile.c and pu the results in the file
/u/orinoco/strfile.o

#6 of 18 by remmers on Tue Apr 11 23:33:14 1995:

Try
    cc /usr/local/grexsrc/strfile/strfile.c -o /u/orinoco/strfile

In other words, exactly what you tried, but leave off the final ".o".

#7 of 18 by remmers on Tue Apr 11 23:35:01 1995:

And also note that there's a space after the "-o".

#8 of 18 by davel on Wed Apr 12 01:26:43 1995:

At a guess, that still won't do it.  It's likely to choke on including
strfile.h, unless orinoco's working dir contains a copy.  Orinoco,
I'm sure there's a way to make cc look in /usr/local/grexsrc/strfile
for strfile.h, but you'll have to read the man yourself to find it.  I'd
honestly suggest copying the thing temporarily, since this is something
small.

#9 of 18 by srw on Thu Apr 13 07:34:30 1995:

man cc wil yield a lot of info. If you want to save it to a file for viewing
in the editor (as I often do), you should strip off the formatting characters.
This can be done by piping it through col -b

man cc | col -b >yourcopy

Just delete it when you don't need it any more.

Hmm I would have suggested Jellyware rather than info for this question.

#10 of 18 by orinoco on Sat Apr 15 19:41:57 1995:

well, i got the program compiled, but i'm still having problems...read tem 128
for info...

#11 of 18 by coyote on Sat Aug 17 00:22:42 1996:

I'm having problems executing C programs once they've been compiled.  I've
got a silly little 'Hello World' file in /u/coyote/c/hello.c as a test.  The
computer just won't run the a.out file, no matter what I do.  I've been using
the gcc compiler.  I used to be able to compile, using the exact same method
as describes above, but now it just doesn't work.  Any help?

#12 of 18 by mdw on Sat Aug 17 02:21:43 1996:

I'm having a *lot* of trouble reading your screen from here.  My eyes
just aren't good enough to pick out the really tiny error message that
scrolled off your tube hours ago, and has only left a *very* faint
phosphorescent glow for me to read by now.

#13 of 18 by coyote on Sat Aug 17 03:28:33 1996:

????????? There were no error messages during compiling, if that's what you're
getting at, and the error message that I get when I try to run it goes like
this "a.out: Command not found"

#14 of 18 by ajax on Sat Aug 17 03:39:25 1996:

  I think that was Marcus' way of requesting more info on the error :-).
Type "./a.out", which specifies which directory to run the file from.
If you just type "a.out", it looks for a.out in /usr/local/bin and other
directories on your search path, but not in the current directory.

#15 of 18 by coyote on Sat Aug 17 03:57:29 1996:

Yah, that worked.  I had thought my c directory was in my path, but I guess
it wasn't.  Human error, not the Unix's fault.  <Coyote apologizes to the
Unix>

#16 of 18 by mdw on Mon Aug 19 08:15:05 1996:

I've had to debug programs that that had coyote's error message
philosophy.  Not fun.  Even more scarily, I've met people who have
actively advocated the philosophy that programs should *never ever*
print error messages.  Supposedly, this is part of being "user
friendly".  Personally, I consider it "user hostile".

#17 of 18 by davel on Mon Aug 19 12:52:16 1996:

Nonsense.  The word "error" just scares the user, Marcus.  Your program is
supposed to run so perfectly that you don't *need* error messages, anyway.

(I'd put in a smiley except that I, too, have met this philosophy seriously
advocated.  Bah, humbug.)

#18 of 18 by remmers on Mon Aug 19 13:11:00 1996:

Right, to admit the possibility of errors is to accept liability
for them.

Response not possible - You must register and login before posting.