Results 1 to 3 of 3
Trying to compile a program and am getting the following output:
Code:
/opt/m68k/m68k-elf/lib/libc.a(closer.o): In function `_close_r':
../../../../../newlib-1.14.0/newlib/libc/reent/closer.c:53: warning: _close is not implemented and will always fail
/opt/m68k/m68k-elf/lib/libc.a(fstatr.o): In function `_fstat_r':
...
- 08-18-2009 #1Just Joined!
- Join Date
- Jul 2009
- Posts
- 27
warning: _close is not implemented and will always fail?
Trying to compile a program and am getting the following output:
Code:/opt/m68k/m68k-elf/lib/libc.a(closer.o): In function `_close_r': ../../../../../newlib-1.14.0/newlib/libc/reent/closer.c:53: warning: _close is not implemented and will always fail /opt/m68k/m68k-elf/lib/libc.a(fstatr.o): In function `_fstat_r': ../../../../../newlib-1.14.0/newlib/libc/reent/fstatr.c:62: warning: _fstat is not implemented and will always fail /opt/m68k/m68k-elf/lib/libc.a(makebuf.o): In function `__smakebuf': ../../../../../newlib-1.14.0/newlib/libc/stdio/makebuf.c:96: warning: isatty is not implemented and will always fail /opt/m68k/m68k-elf/lib/libc.a(lseekr.o): In function `_lseek_r': ../../../../../newlib-1.14.0/newlib/libc/reent/lseekr.c:58: warning: _lseek is not implemented and will always fail /opt/m68k/m68k-elf/lib/libc.a(openr.o): In function `_open_r': ../../../../../newlib-1.14.0/newlib/libc/reent/openr.c:59: warning: _open is not implemented and will always fail /opt/m68k/m68k-elf/lib/libc.a(readr.o): In function `_read_r': ../../../../../newlib-1.14.0/newlib/libc/reent/readr.c:58: warning: _read is not implemented and will always fail /opt/m68k/m68k-elf/lib/libc.a(writer.o): In function `_write_r': ../../../../../newlib-1.14.0/newlib/libc/reent/writer.c:58: warning: _write is not implemented and will always fail
My command is this:
Code:make[1]: Entering directory `/cygdrive/c/build' m68k-elf-ld -M -cref -Mex Mex.Mex -T ../Mex.ld -L`m68k-elf-gcc -m68000 --print-libgcc | sed -e "s/libgcc.a//g"` -o Map MexMain.o file1.o file2.o file3.o file4.o file5.o file6.o file7.o file8.o file9.o -lgcc -lc -lnosys -lg
Anyone have any idea how to get rid of the warnings?
- 08-18-2009 #2
Warnings are just that, a warning, your code will compile and run, however you may get undesirable results as outlined by the warning's description. If those functions are never used then it is unnecessary to do anything about the warnings. However, it seems that an easy fix would be to implement those functions even if they have empty bodies.
- 08-18-2009 #3Just Joined!
- Join Date
- Jul 2009
- Posts
- 27
Thanks, I'll try it out!


Reply With Quote