public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: deberryr@hotmail.com (Richard De Berry)
To: help-gcc@gnu.org
Subject: Newbie - gcc apparently not building obj file
Date: Tue, 04 Jan 2000 17:11:00 -0000	[thread overview]
Message-ID: <PKwc4.1195$WM5.26589@dfiatx1-snr1.gtei.net> (raw)

I have Red Hat Linux 5.2 installed, gcc version 2.7.2.3, ELF 32-bit LSB 
executable.  Trying to execute the simple Hello World program as a test on how 
the compiler works, but it doesn't appear to be building an executable.  If I 
enter gcc -o hello hello.c <RET>, then hello <RET>, I get a command not found 
message.  I would really like to know what I'm doing wrong.  I've read all the 
documentation I can find, but to no avail.  A little help, please.  Thanx.
Richard De Berry

WARNING: multiple messages have this Message-ID

From: deberryr@hotmail.com (Richard De Berry)
To: help-gcc@gnu.org
Subject: Newbie - gcc apparently not building obj file
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <PKwc4.1195$WM5.26589@dfiatx1-snr1.gtei.net> (raw)
Message-ID: <20000401000000.Cgn16xqpIG9n5lUfYxVNRRy0EfANPXrIPWWyFKY8szQ@z> (raw)

I have Red Hat Linux 5.2 installed, gcc version 2.7.2.3, ELF 32-bit LSB 
executable.  Trying to execute the simple Hello World program as a test on how 
the compiler works, but it doesn't appear to be building an executable.  If I 
enter gcc -o hello hello.c <RET>, then hello <RET>, I get a command not found 
message.  I would really like to know what I'm doing wrong.  I've read all the 
documentation I can find, but to no avail.  A little help, please.  Thanx.
Richard De Berry

             reply	other threads:[~2000-01-04 17:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-04 17:11 Richard De Berry [this message]
2000-01-05  9:25 ` d_cary
2000-04-01  0:00   ` d_cary
2000-04-01  0:00 ` Richard De Berry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='PKwc4.1195$WM5.26589@dfiatx1-snr1.gtei.net' \
    --to=deberryr@hotmail.com \
    --cc=help-gcc@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).