On Wed, 19 Nov 2008 23:24:52 +0100, Ingo Weinhold said: > That's wrong. It's compiling libgcc2.c for the target, so it must use > the > target's headers. Maybe I'm getting senile, but I thought I wrote as > much > when the problem was reported originally. I stand corrected. Thanks for the explanation. I just asusmed it was simply building the native compiler. > The build/scripts/build_cross_tools script copies Haiku's headers to > the > temporary directory <generated>/cross-tools-build/sysincludes. The > GCC > build system runs them through fixincludes and copies them to another > location in the output directory tree. Looking at the compile line > I'd say > that would be the "-I./include", but you can verify this by having a > look > at the build output. So, assuming that the headers aren't there, all > you > have to do is check which of the two involved steps fails to copy the > headers correctly and understand why. So it is very likelly that there is a previous error that he missed. Dustin, can you double check? -Bruno