This is the mail archive of the crossgcc@sourceware.org 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] |
oh, man. i just figured out why i couldn't cross-compile a source file with my newly-generated toolchain. from the source tree i inherited, i had a source file that included #include <errno.h> ok, that looks reasonable enough. but i hadn't noticed that the actual compile command included the option "-I./include", where that local include directory included (you guessed it) a file called "errno.h", whose entire contents are: #ifndef __ERRNO_H__ #define __ERRNO_H__ #define EOVERRUN 2001 #define EUNDERRUN 2002 #define ERROR 2003 #endif argh. so obviously this was the errno.h file picked up by the preprocessor (right?), therefore, pretty much *all* of the standard errno macros would have gone missing if they had been used (that explains the undefined EINVAL). how the *heck* did this ever work in the first place? rday ------ 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] |