what I do for thus error "fatal error iostream.h no such file or directory"

Question

3.00/5 (1 vote)

See more:

when i compile my code

XML

#include <iostream>

int main(int, char **) {
  std::cout << "Hello World!" << std::endl;

  return 0;
}

this error "fatal error iostream.h no such file or directory"

Posted 9-Oct-14 3:09am

mohamed sabri

Add a Solution

Comments

[no name] 9-Oct-14 9:16am

What do you do? You read the documentation for whatever IDE you are using and provide the appropriate path to your files in your project settings.

enhzflep 9-Oct-14 9:24am

Your error message and supplied code appear to be a mismatch.

Older compilers like TurboC used to require the use of iostream.h, while newer ones require the use of iostream (no extension). The error message you show is the same one I'd get with MinGW if I tried to include iostream.h. But as I mentioned, this appears inconsistent with your code, which includes the extension-less iostream.

Which compiler (and version) are you using?

CPallini 9-Oct-14 9:34am

My virtual 5.

enhzflep 9-Oct-14 9:36am

Thank-you. :)

KarstenK 9-Oct-14 13:14pm

write it as answer to close the question.

enhzflep 9-Oct-14 13:39pm

Thanks for the suggestion, but since it's not an answer, I'll have to decline your invitation. It's a comment combined with a question aimed at attempting to retrieve enough information to diagnose the problem.
You're perfectly welcome to post my comment as a solution if you wish. :)

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)