Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
12748 Discussions

warning: unlink is not implemented and will always fail

Altera_Forum
Honored Contributor II
‎02-03-2012 06:22 PM
1,520 Views

I get this message when I build a custom Simple Socket Server project in Nios2 SBT 11.0sp1. The build completes without error, but the app will not run. If I make a change in the app, for example turning on the VFS, it compiles without this message and runs fine. May be something to do with the custom part of the code, but how do I troubleshoot this? 

 

Here is the entire warning message: 

 

 

c:/altera/11.0/nios2eds/bin/gnu/h-i686-mingw32/bin/../lib/gcc/nios2-elf/4.1.2/../../../../nios2-elf/lib\libc.a(lib_a-unlinkr.o): In function `_unlink_r': 

/build/swbuild/SJ/nightly/11.0sp1/208/l32/work/ip/sopc/app/gnu/BUILD/gnu/build-0-newlib.nios2-elf.i686-mingw32/nios2-elf/newlib/libc/reent/../../../../../src/newlib-1.16/newlib/libc/reent/unlinkr.c:54: warning: warning: unlink is not implemented and will always fail 

 

Can anyone shed some light on this form me?
0 Kudos

Link Copied

0 Replies
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.