News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

Open descriptor errs on sdk.h

Started by Pecan, July 15, 2006, 04:03:50 AM

Previous topic - Next topic

Pecan

ubuntu 510 svn 2750

On two files, I get fdopen errs on #include <sdk.h>.
Files: Filepathpanel.cpp and genericselectpath.cpp get his error.

I deleted both /devel and /output and /.objs
I also did a build clean, then a rebuild.
All other files using sdk.h compile just fine.

If I replace the sdk.h include with an #include <sdk_common.h>, all compiles ok.

Any ideas?


-------------- Build: Scripted wizard in Code::Blocks - Unix ---------------
Compiling: plugins/scriptedwizard/buildtargetpanel.cpp
Compiling: plugins/scriptedwizard/compilerpanel.cpp
Compiling: plugins/scriptedwizard/filepathpanel.cpp
plugins/scriptedwizard/filepathpanel.cpp:1:17: error: calling fdopen: Bad file descriptor
Process terminated with status 1 (103 minutes, 35 seconds)
1 errors, 5 warnings


thanks
pecan

Ceniza

I got a problem like that once. It seems it was caused by re-inclusion of the precompiled header.

BTW... isn't 103 minutes a lot of time to build Code::Blocks?

mandrav

Ceniza is right:
Never, ever, include a precompiled header in a header file (*.h). Only in implementation files (*.cpp)...
Be patient!
This bug will be fixed soon...

Pecan

#3
Quote from: mandrav on July 15, 2006, 08:38:48 AM
Ceniza is right:
Never, ever, include a precompiled header in a header file (*.h). Only in implementation files (*.cpp)...


Now wait a moment, I get this error without making any mods to the svn update. So where is the extra include comming from?

I only changed the include in the .cpp files to get around the error.

Are you saying that svn should not include the <sdk.h> or that sdk.h is doing the double include. I'm confused here.

@Ceniza
  103 minutes to the error. 4Hrs to do a full "clean" build. I'm doing it on my old  333mhz laptop.


killerbot

Quote4Hrs to do a full "clean" build.
now that's nearly a real nightly/daily build ;-)

Raijinsetsu

When using GCC, you never have to directly include a precompiled header anyways.

Quote from: GCC.orgFor instance, if you have #include "all.h", and you have all.h.gch in the same directory as all.h, then the precompiled header file will be used if possible, and the original header will be used otherwise.
Here's the link: http://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html