From: Andrew Pinski <pinskia@gcc.gnu.org>
To: "Long Fei" <lfei@ecn.purdue.edu>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: Gcc installation problem
Date: Sat, 16 Aug 2003 15:08:00 -0000 [thread overview]
Message-ID: <6F375138-CFFB-11D7-B919-000393A6D2F2@gcc.gnu.org> (raw)
In-Reply-To: <002801c36407$3ff5fc20$2c7b2e80@ee271dpc5>
What errors are you receiving?
Is your program a c++ program, if it is make sure that you are using
right namespace?
For an example:
#include <iostream>
int main(){cout<<"Hello World\n";}
Should be become
#include <iostream>
int main(){std::cout<<"Hello World\n";}
Also this is not the right mailing list, use gcc-help@ instead.
I moved it to there.
Thanks,
Andrew Pinski
On Saturday, Aug 16, 2003, at 11:01 US/Eastern, Long Fei wrote:
>
> I followed the instructions in the manual and successfully built and
> installed gcc3.3. Problem occurred when I tried to compile C/C++ src
> with gcc3.3. Details are given below:
>
> System: Red Hat Linux 7.2, P4 server
> Because this version of linux ships with the defective gcc 2.96, I
> tried
> to install gcc3.3 for myself. So the new gcc is not installed in the
> default /usr/local directory since I don't have root privillege. I
> installed gcc in a directory different from the gcc source directory,
> as
> recommended in the installation manual.
>
> I strictly followed the steps in the manual. Successfully built &
> installed gcc.
>
> The new gcc can now compile some simple programs without header files.
> When I tried some real programs, a lot of errors reported in compiling
> process. Most of them were reporting that there are errors in the
> header
> files. I found those incompatible header files were in /usr/include, so
> I guess they were the header files of gcc2.96.
>
> I then tried -I/-I- directives to give the specific path of the new gcc
> include directory. I also put the new gcc paths in the beginning of
> PATH
> env varible. But the problems remained. The new gcc was still unable
> to
> find the correct include files.
>
> Could anybody tell me what I need to do to properly configure gcc3.3
> after installation ? Especially how to solve this header file problem.
>
> Thanks a lot!
>
>
>
next parent reply other threads:[~2003-08-16 15:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002801c36407$3ff5fc20$2c7b2e80@ee271dpc5>
2003-08-16 15:08 ` Andrew Pinski [this message]
[not found] <002a01c36409$72d08fa0$2c7b2e80@ee271dpc5>
2003-08-16 15:30 ` Andrew Pinski
2003-08-16 15:14 Long Fei
[not found] <616BE6A276E3714788D2AC35C40CD18D6BFC5C@whale.softwire.co.uk>
2002-07-01 1:01 ` gcc " Rupert Wood
-- strict thread matches above, loose matches on Subject: below --
2002-06-30 21:11 yt wang
2001-04-05 18:08 GCC Installation problem kyamada
2001-04-05 19:05 ` Alexandre Oliva
2000-10-20 1:34 GCC Installation Problem TEO Poh Kwee
2000-04-05 23:22 gcc installation problem Gilad Even-Tzur
1999-10-08 11:58 gcc:installation problem oupegt
1999-10-08 14:43 ` Paul D. Smith
1999-10-11 12:54 ` oupegt
1999-10-11 14:12 ` Paul D. Smith
1999-10-31 13:57 ` Paul D. Smith
1999-10-31 13:57 ` oupegt
1999-10-31 13:57 ` Paul D. Smith
1999-10-31 13:57 ` oupegt
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=6F375138-CFFB-11D7-B919-000393A6D2F2@gcc.gnu.org \
--to=pinskia@gcc.gnu.org \
--cc=gcc-help@gcc.gnu.org \
--cc=lfei@ecn.purdue.edu \
/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).