From: Mark Gallagher <mark@cyberfuddle.com>
To: "Sridhar J (june end)" <sridharj.hyd@cxknetworks.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Reg:gcc
Date: Wed, 26 Jun 2002 23:07:03 +1000 [thread overview]
Message-ID: <3D19BC77.2040402@cyberfuddle.com> (raw)
In-Reply-To: F4D3DB9A18752A4F99FD880ABC5407179D15BA@ccdc-exchg.careercommunity.com
Sridhar J (june end) wrote:
> Hello
>
> Thanks to all of you who replied promptly to my question. I would like to
> clarify one thing. When I compiled the program using gcc, I tried typing
> a.out. When that didn't work, I did a ls -l which showed me a file called
> a.out*.
>
> Doesn't it mean that a.out is in the current directory? So why I should go
> to a parent directory as in ./a.out to execute it?
You aren't going to a parent directory in doing that. "." is your
present directory, and ".." is a parent. So if you're in a child of the
directory with a.out in it, then you'd use ../a.out. If you're in the
actual directory it's in, then use ./a.out.
--
Mark Gallagher
http;//cyberfuddle.com/infinitebabble/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-06-26 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 12:26 Reg:gcc Sridhar J (june end)
2002-06-26 12:57 ` Reg:gcc Jos Lemmerling
2002-06-26 13:07 ` Mark Gallagher [this message]
2002-06-26 13:45 ` Reg:gcc Brian Bilbrey
2002-06-26 14:22 ` Reg:gcc Gavin Laking
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=3D19BC77.2040402@cyberfuddle.com \
--to=mark@cyberfuddle.com \
--cc=linux-newbie@vger.kernel.org \
--cc=sridharj.hyd@cxknetworks.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.