public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Chris Garrett <cgarrett@degarrah.com>
To: gcc@gcc.gnu.org
Subject: GCC 4.0.1 - iostream: No such file or dir....
Date: Sat, 06 Aug 2005 04:52:00 -0000	[thread overview]
Message-ID: <42F44205.3070608@degarrah.com> (raw)

I finally got 4.0.1 built in msys. I must have screwed up my msys/gcc 
setup because a clean install of msys and gcc-3.4.1 worked. I started 
with a simple test:

main.cpp:
~~~~~~~~~~~~~~~~~~~~~~~~~~
#include <iostream>

int main()
{
        cout << "Hello\n";
        return 0;
}


then I try and build it:
~~~~~~~~~~~~~~~~~~~~~~~~~~
chris@NEPTUNE /d/tmp/simple$ g++ main.cpp -o main
main.cpp:1:20: error: iostream: No such file or directory
main.cpp: In function 'int main()':
main.cpp:5: error: 'cout' was not declared in this scope

I looked thru in /mingw/include/c++/4.0.1 and iostream exists in that 
directory. Is there something I'm missing? Do you need to specify gcc's 
include directories explicitly now?

Thank you

Chris


My system details:
WinXP Pro
GCC 3.4.1
Msys


config cmd:
~~~~~~~~~~~~~~~~~~~~~~~~~~
../gcc-4.0.1/configure \
        --prefix=/mingw \
        --with-gcc \
        --with-gnu-ld \
        --with-gnu-as \
        --enable-threads \
        --disable-shared \
        --disable-nls \
        --enable-languages=c,c++,f95 \
        --disable-win32-registry \
        --with-gmp=/usr/local/gmp-4.1.4


make cmd:
~~~~~~~~~~~~~~~~~~~~~~~~~~
make \
        CFLAGS="-O2 -march=i686 -fomit-frame-pointer" \
        CXXFLAGS="-mthreads -O2 -march=i686 -fomit-frame-pointer" \
        LIBCFLAGS="-O2" \
        LIBCXXFLAGS="-O2 -fno-implicit-templates" \
        LDFLAGS="-s" \
        bootstrap






             reply	other threads:[~2005-08-06  4:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-06  4:52 Chris Garrett [this message]
2005-08-06 15:49 dank
2005-08-07 20:19 ` Chris Garrett
2005-08-08  4:10   ` Mike Stump
2005-08-08 17:40     ` Chris Garrett

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=42F44205.3070608@degarrah.com \
    --to=cgarrett@degarrah.com \
    --cc=gcc@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).