This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> ../../gcc/libgcc2.c:41: stdlib.h: No such file or directory > ../../gcc/libgcc2.c:42: unistd.h: No such file or directory I don't know anything about mingw32, but since everybody else seem to be away, I'll toss a thought around: mingw32 probably comes with some libraries and header files, which you'll need to install in $prefix/$target. See the numerous FAQ and past posts about that. > Since stdlib.h and unistd.h are fairly normal include files to expect > to have (well, stdlib.h anyway), I would think it's related to the > famed GCC fixincludes script, but I really have no idea. Does anyone > have anything to suggest? fixincludes will only fix header files that are not GNU-friendly. It doesn't save you from having the headers in the first place. I don't know if mingw32's headers are GNU-friendly, but considering mingw stands for "Minimalist Gnu for Windows" I'd expect it to be. You probably don't need to use it. HTH, Y. ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |