Issues in building cross compiler

[Martin v. Loewis]

> 1)
> checking whether the C compiler (/home/cheon/gnu/gcc-2.95.2-obj/gcc/xgcc
> -B/home/cheon/gnu/gcc-2.95.2-obj/gcc/
> -B/home/cheon/gnu/ppc-eabi/powerpc-eabi/bin/ -g -O2 ) works... no
> configure: error: installation or configuration problem: C compiler
> cannot create executables.

That apparently happens when trying to build libiberty for the
target. Please inspect config.log to see why it failed.

> 2)
> dummy.c:1: sys/types.h: No such file or directory
> dummy.c:8: stdio.h: No such file or directory
> dummy.c:9: time.h: No such file or directory
> dummy.c:10: signal.h: No such file or directory
> gen-params: could not invoke /home/cheon/gnu/gcc-2.95.2-obj/gcc/xgcc
> -B/home/cheon/gnu/gcc-2.95.2-obj/gcc/
> -B/home/cheon/gnu/ppc-eabi/powerpc-eabi/bin/ -I.
> -I../../../gcc-2.95.2/libio -E on dummy.c
> 
> Seems that the dummy.c is a self generated file. What is the use of it ?

It is generated by the gen-params script, which is designed to find
out things about the target library. It will then put this information
into _G_config.h.

> Any clue why those header files are not found ? 

These are the C header files of the target. Most likely they are not
found because you did not provide a C library for the target.

> What is the purpose of xgcc and the corresponding -B option ?

xgcc is the cross compiler that just had been built.

> Does xgcc expect these header files in gcc-2.95.2/libio ?

No, it expects them in the target-specific include path.

> Why are they not in the gcc-2-95.2 source package ?

Because gcc is a compiler, not a C library.

Hope this helps,
Martin