Lpc2000

ocnek1 wrote:

>
>Thank you!  That worked.  It now compiles with no errors!!  Is this an
>error with newlib?  If you can explain why this happend that would be
>great.  I would like to understand why this problem happend so I will
>be prepared the next time it shows up.
>
>  
>
Not an error.  AFAICT, needs certain functions linked into it when 
compiled as having stubs: --disable-newlib-supplied-syscalls.  By 
disabling syscalls, you will have to provide the missing functionality 
with your own code.  Probably the most common of these are the file 
stream functions: open_r.c, lseek_r.c, write_r.c, sbrk_r.c, ...

In your case, and mine, we used some library calls (functions) which 
caused newlib to see if the target stream is a TTY (console device).  I 
am not sure, but a console device may cook the data in its' driver 
code.  By telling newlib via isatty.c that it is not a console, we would 
get raw data (uncooked)?  I didn't follow the code to see why the 
isatty() call was needed.

Anyhow, you will run into more of this as you go along.  Look into the 
newlib sources at: <newlib_sources>/newlib/libc/reent/ for most of these 
needed stubs.  HINT: you will see what params will be passed to your 
functions via these "stubs".


Regards,

TomW



-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------