| standard include paths not recognized [message #157317] |
Sat, 05 November 2005 11:00  |
Eclipse User |
|
|
|
Originally posted by: gentoo.aloetscher.ch
Hi
I have installed eclipse cdt 3.0 with eclipse 3.1 on gentoo linux. When
I make a new c++-project (managed or standard), no include path appear.
When I type the following code:
#include <iostream>
using namespace std;
int main() {
cout << "Hello world" << endl;
}
the project is compiled successfully, but in the first line "#include
<iostream>" appears a "?" with the following message:
"C/C++ Indexer Problem: Preprocessor Inclusion not found: iostream in
file: /path/to/workspace/path_to_project/hello.cpp".
Also, the binary is created successfully, but is not recognized as a
binary. I have tried all binary parsers, especially the ELF parser, but
no of them recognizes the binary.
Surprisingly, i can however run the binary file with "Run as ..." -->
"Run as Local C/C++ Application".
Is there someone, who could imagine, what's going wrong with my eclipse
cdt installation? Maybe I have to set some environment variables, but I
don't know which of them.
In my gentoo installation, the includes are found in the following path:
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/include/g++-v3.
Thank you a lot for your help.
Adrian
|
|
|
|
| Re: standard include paths not recognized [message #158332 is a reply to message #158108] |
Thu, 17 November 2005 22:53  |
| Eclipse User |
|
|
|
Originally posted by: gentoo.aloetscher.ch
Hi Ruben
Unfortunately, I couldn't solve the problem. But perhaps, I have found,
in which code line the parser is configurated.
In the file ".cdtproject" I have noticed the following line:
<runAction useDefault="true" command="gcc" arguments="-E -P -v -dD
${plugin_state_location}/${specs_file}"/>
But I don't know, how I can find out, witch value the variables
${plugin_state_location} and ${specs_file} have. Perhaps you or someone
else can help me.
When I type the command "gcc -E -P -v -dD" on the bash shell, I receive
the following information, which seems to be okay.
gcc -E -P -v -dD
Lese Spezifikationen von /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/specs
Konfiguriert mit: /var/tmp/portage/gcc-3.3.6/work/gcc-3.3.6/configure
--prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.3.6
--includedir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/includ e
--datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.6
--mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.6/man
--infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.6/info
--with-gxx-include-dir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3. 3.6/include/g++-v3
--host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec
--enable-nls --without-included-gettext --with-system-zlib
--disable-checking --disable-werror --disable-libunwind-exceptions
--disable-multilib --enable-java-awt=gtk
--enable-languages=c,c++,java,f77 --enable-shared --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu
Thread-Modell: posix
gcc-Version 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8)
Regards,
Adrian
Ruben Jenster wrote:
> Hi Adrian,
> I have the same problem with eclipse and the c++ indexer.
> Have you allready solved the indexer problem?
>
> Regards,
> Ruben
>
|
|
|
| Re: standard include paths not recognized [message #159791 is a reply to message #158332] |
Fri, 02 December 2005 13:01 |
| Eclipse User |
|
|
|
Originally posted by: _spaaam_usenet.laliluna.de_spaam_
The solution to the problem is to add the directory where the iostream etc
are located.
under my linux this is
/usr/include/c++/4.0.2/iostream
open the project properties
-> c/c++ build -> Tool Setting --> GCC C++ Compiler --> Directories
and simple add your path.
Best Regards
Sebastian
Tutorials and Seminars for Java
http://www.laliluna.de
|
|
|
| Re: standard include paths not recognized [message #159823 is a reply to message #157317] |
Sat, 03 December 2005 11:06 |
| Eclipse User |
|
|
|
Originally posted by: void.void.com
See also the post "Preprocessor inclusion not found" from 11/22/2005.
This is a bug in the indexer which has been around for a long time now
(I have seen it filed on bugzilla several times now, but it looks as if
it isn't being classified high priority for the devs, unfortunately).
Regards,
Matthias
|
|
|
Powered by
FUDForum. Page generated in 0.05946 seconds
] 
Search
Help
Register
Login
Home
