From: sherry <sherry@zeroknowledge.com>
To: aaboulhosn@entpm2.prod.fedex.com, gcc-help@gcc.gnu.org
Subject: Re: Problem In compiling C++ codes
Date: Thu, 22 Feb 2001 10:56:00 -0000 [thread overview]
Message-ID: <3A9560D8.5AD8AA5A@zeroknowledge.com> (raw)
In-Reply-To: <OFD8570FFF.DDD367A3-ON862569FB.0066800D@prod.fedex.com>
aaboulhosn@entpm2.prod.fedex.com wrote:
> I appreciate your response.
>
> 1) I Tried to put the whole path in my C++ program like this:
> #include <path directory for my header file/iostream.h>
>
> and tried to compile, it does not work.
> is there any other way, to include the path name ?
Check the PATH environment variable:
echo $PATH should give you that , you can modify it also.
If you are using bash like me and type env at console then you can
see all variables and path is there.
else check the man pages for your shell
>
>
> 2) If I have an : a.out execuatble file
> when I type: a.out It does not find the link library
this problem can be related to the path also.
>
>
> 3) what is the extension for the source file , in C++ and how to compile
> it ?
man g++ will help you :)
>
>
> I know for my C program, example:
>
> filename.c
> To compile : gcc filename.c
>
> Thank you
welcome
next parent reply other threads:[~2001-02-22 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFD8570FFF.DDD367A3-ON862569FB.0066800D@prod.fedex.com>
2001-02-22 10:56 ` sherry [this message]
2001-02-22 12:18 ` David T-G
2001-02-23 17:33 ` llewelly_nospam_
2001-02-23 10:13 aaboulhosn
2001-02-23 10:43 ` sherry
2001-02-23 17:43 ` llewelly_nospam_
-- strict thread matches above, loose matches on Subject: below --
2001-02-23 10:12 aaboulhosn
2001-02-22 9:37 aaboulhosn
2001-02-22 10:36 ` sherry
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=3A9560D8.5AD8AA5A@zeroknowledge.com \
--to=sherry@zeroknowledge.com \
--cc=aaboulhosn@entpm2.prod.fedex.com \
--cc=gcc-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).