NetBurner Community Forum

Here's a minimal code snippet that produces the error:

------------------------------------------------------------
#include <stdio.h> // decl for fopen()
#include <unistd.h> // decl for unlink()

extern "C" {void UserMain(void * pd);}

void doTest_01(void ){
FILE* fp = fopen("MyFile.txt", "w ...

Tod:

rnixon's post reminded me about a problem I would sometimes see. If you use other development tools like MinGw that modify the "path" environment variable that can screw up things. I know that Borland's C++ Builder can also cause this. The fix is to move all the c:\nburn\.... path entries to ...

I could only find these two references to the file unlinkr.c:

* Separate _link_r() from _unlink_r()
* libc:reent package

And you're right, they both appear to be associated with the Cygwin implementation. So why does the linker report a problem with a file that's not even supposed to be there ...

Our app does not need wireless capability at this time, so the rtl8711 is out (Thanks).

For now, I can achieve error-free linkage using the following work-around in my app:

// -----------------------------------------------------------------------------
// WARNING! Bogus Code Ahead ...

Okay, after going through the usual steps to resolve name mangling there is one linker error that refuses to go away:

c:/nburn/gcc-m68k/bin/../lib/gcc/m68k-elf/4.2.1/../../../../m68k-elf/lib/m5206e\libc.a(lib_a-unlinkr.o): In function `_unlink_r':
unlinkr.c:(.text+0x10): undefined reference to ...

Right. I tried the extern "C" { ... } for all of the relevant files.

I also renamed all of the Lua *.c and *.h files to *.cpp and *.hpp, respectively. This was suggested by the Lua web site. I also revised the corresponding #include statements accordingly (#include lua.h -> #include lua.hpp)

Still ...

Running NBEclipse 2.5.0 to build a MOD5272 app.

The specific compiler (or linker) can be specified via the IDE menu: Right-click on project Properties. Then {C/C++ Build}->{Settings}->{GNU C/C++ Linker}. Enter the compiler of choice in the Command text box.

I've tried both m68k-elf-g++ and m68k ...

Is it possible I've got the wrong version of libc.a? The default linker in NBEclipse generates the following errors on my code:

C:\nburn\gcc-m68k\m68k-elf\lib\m5206e\libc.a(lib_a-system.o): In function `_system_r':
system.c:(.text+0xe): undefined reference to `_system'

C:\nburn\gcc-m68k\m68k-elf ...

Tod: Yeah, I was also wondering about the fact that AutoUpdate ever worked at all -- and in fact had worked for several weeks before it suddenly failed. That's why I focused things that had changed recently (like my code) rather than anything else on the system. Go figure.

Funny thing: I got kicked ...

Tod:

Bingo! The firewall thing did the trick. All fixed now and AutoUpdate is running like a charm.

Many thanks.