Cross gcc Mailing List Archive
[Prev][Next][Index][Thread]

Re: compilation problem

On Fri, 18 Oct 1996, Josef Wolf wrote:

> When compiling binutils-2.7 with the one-source-tree configuration, I get
> the following error:
> 
> [ many many stuff deleted ]
>   /usr/local/spool/maketemp/build/gcc/xgcc -B/usr/local/spool/maketemp/build/gcc/ -idirafter /usr/local/spool/maketemp/build/m68k-unknown-coff/newlib/targ-include -idirafter /usr/local/spool/maketemp/src/newlib/libc/include -nostdinc -c -O2 -fomit-frame-pointer -I. -I../../../src/libiberty/../include   ../../../src/libiberty/choose-temp.c -o pic/choose-temp.o
> /usr/local/spool/maketemp/build/gcc/xgcc -B/usr/local/spool/maketemp/build/gcc/ -idirafter /usr/local/spool/maketemp/build/m68k-unknown-coff/newlib/targ-include -idirafter /usr/local/spool/maketemp/src/newlib/libc/include -nostdinc -c -O2 -fomit-frame-pointer -I. -I../../../src/libiberty/../include  ../../../src/libiberty/choose-temp.c
> ../../../src/libiberty/choose-temp.c:27: sys/file.h: No such file or directory
> make[1]: *** [choose-temp.o] Error 1
> make[1]: Leaving directory `/usr/local/spool/maketemp/build/m68k-unknown-coff/libiberty'
> make: *** [all-target-libiberty] Error 2
> 
> Why do I need a file.h for the target? Where can I get one? Where should
> I put it?

I find that many of these strange "can't find header file" compile errors 
usually happen when you run configure twice in the same directory.  They 
are usually fixed by doing a 'rm -rf *' in the build directory and 
running configure again.


Tim.

> 
> Regards,
>
Follow-Ups: References:
Home | Subject Index | Thread Index