ioctl.h is an include file that I assume is brought in by a line in your software that says something like:
#include <ioctl.h> the ioctl.h file is normally a part of the system libraries; I can't check now where it resides in a MSP430 cross-compile environment. Normally, it defines a bunch of macros and constants for the ioctl() system call, so it may be actually unnecessary---I doubt that you use ioctl() calls on your embedded system. Try commenting it out or creating an empty ioctl.h file, and recompiling. If there are no errors, you just need to test your software; otherwise you'll have to look at your source code to see what does it use ioctl() for, and figure out where to find it in your rtems/cross-compile runtime environment, or how to emulate it. On 10/30/07, 张天雷 <[email protected]> wrote: > > recently, I am working on a porting task, the os is rtems and the target > cpu is msp430, but I have encountered a problem when compiling: > the toolchain told me some of my files cannot be found and the message is > like the following : > ioctl.h: no such file or directory... > I don't know how to do, any body help me > thanks a lot! > Smart > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > >
