From: Chris Webb <chrisw@nmr.ion.bpmf.ac.uk>
To: help-gcc@gnu.org
Subject: gcc-2.95.2 and solaris 7
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <38746C13.B4E5B107@nmr.ion.bpmf.ac.uk> (raw)
Message-ID: <20000401000000.CHJKIHeruBI0MU3c9MD8dSDOInkLmdT2Y_A9zERaH-4@z> (raw)
I have installed gcc-2.95.2 on a solaris 7 box. I used the tar.gz source
file, the configuration and make process seem to work ok. The include
directories are as follows:
prefix = /usr/local
includedir = ${prefix}/include
oldincludedir = /usr/include
gxx_include_dir=${prefix}/include/g++-3
When I try to compile a simple helloworld program I get the following
error:
test.c:1: iostream.h: No such file or directory
The iostream.h file is present in the gxx_include_dir path, the program
will compile if this file is moved to the includedir path. This is of
course little help, I am dealing with large programs, written over many
files, utilizing large numbers of libraries. Has anyone heard of this
problem, or have a solution?
Incidentally, I have installed the same gcc package under a linux os and
it works fine.
--
Chris Webb
Email: c.webb@ion.ucl.ac.uk
coffee@dircon.co.uk
next reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-06 3:55 Chris Webb [this message]
2000-04-01 0:00 ` Chris Webb
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=38746C13.B4E5B107@nmr.ion.bpmf.ac.uk \
--to=chrisw@nmr.ion.bpmf.ac.uk \
--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).