| | Re: Linking failure when 'making' an lx file
|
|
(...) Sorry about the extra stuff, the linking problem was due to the compiler trying to find the above link "___ucmpsi2". When I used h8300-hitachi-hms-nm I could see all the methods and links in my code, and this was the only strange looking one. (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
|
| | Linking failure when 'making' an lx file
|
|
Hi Can anyone tell me why I'm getting a linking failure when trying to compile my C code, in the standard way. The linker is failing to find a fucntion I have defined in my source: /usr/local/crossgcc/...chi-hms-ld -T ../boot/legOS.lds -relax (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
|
| | Re: Blockin LNP calls
|
|
(...) I guess I'm using lnp_logical_write then? That is, I include the standard lib_lnp.h file into my code and then link my app with liblnp.so.....does this answer your question? Is there a way in which I can call lnp_logical_write directly to test (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
|
| | Re: Blockin LNP calls
|
|
(...) No, I meant lnp_logical_write, which is called from lnp_addressing_write. lnp_logical_write is not within the file lnp.c, which I guess you link into your app. This function is supposed to actually write to the serial device communicating with (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
|
| | Re: Blockin LNP calls
|
|
(...) Sorry, I was using an unsigned char variable, this was just a remnant of some testing I did..... I tried a lot of variations ;-) (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|