Right. I've implemented a specific check for linker errors and it's currently in the trunk (revision 63). I'm not going to be releasing another build yet (the work I've done towards the next batch of new features is strictly backend stuff), so if you could check out and try running an example from the trunk, *hopefully* the error message will change and I'll be able to find out exactly what's going on.
Right. I've implemented a specific check for linker errors and it's currently in the trunk (revision 63). I'm not going to be releasing another build yet (the work I've done towards the next batch of new features is strictly backend stuff), so if you could check out and try running an example from the trunk, *hopefully* the error message will change and I'll be able to find out exactly what's going on.