Welshworrier Posted September 29, 2017 Share Posted September 29, 2017 Currently working on a project that involves linking in the vbcc libraries along with some of the raptor ones. All seems fine in the linking until it tries the output to .abs where it fails with "doesn't know how to handle symbol type error 0x51000000". This is repeated about 20 times. I know I'm going to be doing something wrong but any clues as to where to look? As an aside it wouldn't link in the DSP library of vbcc as unknown type and gave a header indication. This is using the .34 release. Quote Link to comment Share on other sites More sharing options...
JagChris Posted September 29, 2017 Share Posted September 29, 2017 Why not just use vasm and vlink? They work. I don't get why people play with broken toys add wonder why things don't work. Quote Link to comment Share on other sites More sharing options...
Welshworrier Posted September 29, 2017 Author Share Posted September 29, 2017 Perhaps because I'm reporting a potential issue with rln? 3 Quote Link to comment Share on other sites More sharing options...
+CyranoJ Posted September 29, 2017 Share Posted September 29, 2017 You know what. He's not worth arguing with 1 Quote Link to comment Share on other sites More sharing options...
ggn Posted September 29, 2017 Share Posted September 29, 2017 One thing that springs to mind would be checking your output formats when generating the object files. rln mostly supports aout style objects and gnu ar archive libraries. It doesn't support elf object files (although I suppose it wouldn't be that huge a deal to add, it's just that nobody ever needed this) - maybe you have set up vbcc to output elf .o files? Another thing would be to swap vbcc for the gcc used in rb+ - that outputs aout objects that are directly linkable with rln. As a proof just look at rb+ . 4 Quote Link to comment Share on other sites More sharing options...
Welshworrier Posted September 29, 2017 Author Share Posted September 29, 2017 Thanks for that suggestion, will try later. I'd started with the included C compiler but didn't seem to like the code I was feeding it. Will get that bottomed out too. It was curious with the vbcc linking though in that it was happy with two of the .o , just the DSP one it reported an error on. 3 Quote Link to comment Share on other sites More sharing options...
Shamus Posted September 29, 2017 Share Posted September 29, 2017 LOL @ the broken toys reference, best laugh I've had all day—especially considering the source and the broken things it champions. This is odd, because I spent some time making sure that RLN could link against stuff created by VBCC. If you don't mind sending me the project, I could see if it's something I missed. 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.