 | | display driver data segment
|
|
hi folks ! can anyone explain me how the lcddata segment is used in legos ! it seems to me there are some routines which use the rom and some which dont. especially i dont get that the conio.c accesses with the dlcd_* functions the lower lcd data (...) (21 years ago, 26-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | realloc in legos(brickOS)
|
|
can someone please help this guy? ive been out of the loop for some time and really dont know if anyone has made any realloc functions for legos (working in 0.2.6). below is the email he sent me. his email address is: renespanw@hotmail.com regards (...) (21 years ago, 23-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Error linking c++ with gcc 3.3
|
|
No, I'm sorry, it doesn't seem to quite work. But it does get rid of the 3 errors at the bottom - Now it's just the operator new/delete stuff. I replaced the stub.c with the thing below, made libc++.a, and just make in lib/c++, and then go to demo (...) (21 years ago, 19-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Error linking c++ with gcc 3.3
|
|
(...) You should add -fno-rtti -fno-exceptions to the CXXFLAGS in Makefile.common. To get rid of the operator new/delete errors you can replace lib/c++/stub.c with a stub.cpp containing the following. Don't forget to update the Makefile. This works (...) (21 years ago, 18-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
(...) The only time(s) I encountered this type of issue were when I compiled the .srec with different set of compiler settings (or with a different set of header files) than what was used for compiling the Demo/Application code. For instance, if I (...) (21 years ago, 17-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
(...) As for this one, I thought I linked the library statically so you wouldn't require it. Oh well, I'll fix that and let people know when I've updated it. You shouldn't need to install the libraries to use the tools. Michael (Zapp not van der (...) (21 years ago, 17-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
(...) <<snipped>> (...) <<snipped>> (...) I've gotten the same error with gcc 3.2.3 that I compiled and gcc 3.2.2 that the other Michael compiled. I couldn't get gcc 3.3 to compile on my machine. Running gcc -v I get the following responses: (my (...) (21 years ago, 17-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
(...) No, they aren't problems in your end, and no, they're also not gcc's fault. LegOS uses a now unsupported extension to C: multi-line strings. The way they can be made to work is by inserting \n\ on the end of the offending lines. I did this to (...) (21 years ago, 17-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
In lugnet.robotics.rcx.legos, Rich Warren wrote: ... (...) Well, it must be something weird then, what compiler *is* Michael's compiler? (gcc 3.2.3? what?) After all, all cross-compilers should work about the same.... It's a different compiler to (...) (21 years ago, 17-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
You know, it doesn't matter how long I wait before sending out a question... I figured out the trouble with firmdl3. I'd assumed the black plug in the USB port was the IR Tower, which I'd plugged in earlier today. However, my wife had been (...) (21 years ago, 16-Jun-03, to lugnet.robotics.rcx.legos)
|
