From: David T-G <davidtg@bigfoot.com>
To: gcc-help@gcc.gnu.org
Cc: sherry <sherry@zeroknowledge.com>, aaboulhosn@entpm2.prod.fedex.com
Subject: Re: Problem In compiling C++ codes
Date: Thu, 22 Feb 2001 12:18:00 -0000 [thread overview]
Message-ID: <20010222121804.F13744@sector13.org> (raw)
In-Reply-To: <3A9560D8.5AD8AA5A@zeroknowledge.com>
Aref, et al --
It appears that you replied only to Sherry after she replied to you, so
I'm stepping into the discussion late...
...and then sherry said...
% 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.
Actually, the shell's $PATH variable doesn't have to do with your
code's #include directives. In the case above, you should leave off
the <> and just specify something like
#include /path/to/headers/iostream.h
(whereas using <iostream.h> will pick up the *system's* copy of the
header file).
% >
% > 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.
Yep; you probably don't have (and shouldn't have!) '.', or the current
directory, in your path. Instead of typing
a.out
to run your program, simply type
./a.out
to tell the shell to look in the current directory.
%
% >
% >
% > 3) what is the extension for the source file , in C++ and how to compile
% > it ?
%
% man g++ will help you :)
That's probably the best answer :-)
%
% >
% >
% > I know for my C program, example:
% >
% > filename.c
% > To compile : gcc filename.c
% >
% > Thank you
%
% welcome
HTH & HAND
:-D
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6lXP8UScpmrZtnuoRAiHCAJ9H9GvFkWeCw8fp5PIPaK+iQ637BQCeMSLY
oukpqRoo3MNklT4NRgdjrA4=
=GpCO
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-02-22 12:18 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
2001-02-22 12:18 ` David T-G [this message]
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=20010222121804.F13744@sector13.org \
--to=davidtg@bigfoot.com \
--cc=aaboulhosn@entpm2.prod.fedex.com \
--cc=gcc-help@gcc.gnu.org \
--cc=sherry@zeroknowledge.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 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).