 | | 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)
|
