public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: llewelly@198.dsl.xmission.com
To: Ashat Safiullin <ashat@nic.sunmoon.ac.kr>
Cc: help-gcc@gnu.org
Subject: Re: how do I execute compile program?
Date: Mon, 27 Dec 1999 22:13:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.9912272311540.17559-100000@198.dsl.xmission.com> (raw)
In-Reply-To: <849k43$7fs$1@usenet.kreonet.re.kr>

On Tue, 28 Dec 1999, Ashat Safiullin wrote:

> May be it is stupid but
> how I can execute program after doing following:
> 
> gcc -o myfile -g -lm  myfile.c
> 
> and command prompt comes again.

$./myfile


by the way, run

$info gcc

to learn about gcc.



WARNING: multiple messages have this Message-ID
From: llewelly@198.dsl.xmission.com
To: Ashat Safiullin <ashat@nic.sunmoon.ac.kr>
Cc: help-gcc@gnu.org
Subject: Re: how do I execute compile program?
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.9912272311540.17559-100000@198.dsl.xmission.com> (raw)
Message-ID: <19991231222400.kE6l1nTuUrD8g6xMY3hhOsljbnM9GXLnIr0acjNaoOk@z> (raw)
In-Reply-To: <849k43$7fs$1@usenet.kreonet.re.kr>

On Tue, 28 Dec 1999, Ashat Safiullin wrote:

> May be it is stupid but
> how I can execute program after doing following:
> 
> gcc -o myfile -g -lm  myfile.c
> 
> and command prompt comes again.

$./myfile


by the way, run

$info gcc

to learn about gcc.



  reply	other threads:[~1999-12-27 22:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-27 22:10 Ashat Safiullin
1999-12-27 22:13 ` llewelly [this message]
1999-12-31 22:24   ` llewelly
1999-12-28  1:40 ` haha
1999-12-31 22:24   ` haha
1999-12-31 22:24 ` Ashat Safiullin
2000-01-02 17:42 ` Thomas Lionel SMETS
2000-04-01  0:00   ` Thomas Lionel SMETS

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=Pine.LNX.4.10.9912272311540.17559-100000@198.dsl.xmission.com \
    --to=llewelly@198.dsl.xmission.com \
    --cc=ashat@nic.sunmoon.ac.kr \
    --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).