 | | Re: help building gcc cross-compiler (long)
|
|
(...) I think the variable sys_time was replaced with the function get_system_up_time between V2.6.09 and V2.6.10 So, I suspect the patch is for V2.6.09 Just guessing. Steve (20 years ago, 12-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: help building gcc cross-compiler (long)
|
|
(...) Great idea, thanks! Now I'm trying to apply Mark Riley's DCC patch to the brickos-0.2.6.10 source. When I try: patch -d ../kernel <kernel.diff I get: patching file dmotor.c patching file systime.c Hunk #6 FAILED at 332. 1 out of 6 hunks FAILED (...) (20 years ago, 12-Oct-04, to lugnet.robotics.rcx.legos, lugnet.trains)
|
| |
| | Lego.NET: An MSIL front-end for gcc
|
|
We are pleased to announce our first release of the LEGO.NET package, which allows to execute Microsoft IL code (as generated from C# and other languages) on the Lego Mindstorm hardware. This environment has a GCC front-end as its core, which (...) (20 years ago, 11-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: help building gcc cross-compiler (long)
|
|
(...) You must not compile the gcc by your own. Why don't you use a ready-to-run rpm? You can find all you need at: (URL) (20 years ago, 11-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | help building gcc cross-compiler (long)
|
|
I'm following Matthias Erhmann's excellent BrickOS Linux Installation HOWTO, and I've hit a snag. When executing the "make" command in step 2.2 to make the gcc cross-compiler, I got the error below. I commented out the first three lines of the (...) (20 years ago, 11-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Respondre el missatge: LNPd problems
|
|
(...) ... (...) ... I uncommented that and recompiled, but nothing different happened. (20 years ago, 10-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | Respondre el missatge: LNPd problems
|
|
I also had a problem with lnpd and solved it. In my case was a problem with the configuration of the serial protocol, but the simptomes seemed like yours, thats I could receive from RCX but not send. I solved it modifiing the file rcxtty.c (or (...) (20 years ago, 8-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNPd problems
|
|
Can anybody help? If not I'll have to think of an alternative :s (20 years ago, 6-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: compiling problmes 2
|
|
(...) I had the same problem when going to newer binutils and gcc. Look at the patch brickos-gcc33.diff at (URL) first part of that patch changes the linker script slightly to avoid this error. (...) I think with the default linker-script the (...) (20 years ago, 7-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: compiling problmes 2
|
|
(...) Hello Jochen, hello everybody, thank you very much. Both of your hints helped a lot. As it were 271 linker-errors before your help, there are just 40 left now. Maybe someone can help me and tell me where the other references are defined and (...) (20 years ago, 7-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | LNPd problems
|
|
I'm having problems with using LNP to transmit to the RCX. I wrote a test program both on the RCX and the PC. Whenever the PC program tries to transmit data, I get the following error: lnp_integrity_write(): Interrupted system call What does this (...) (20 years ago, 2-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: compiling problmes 2
|
|
Hi Rudolf, (...) No. Some _are_ defined in .h-files. And the register sets come via h8300.rcx to boot/brickOS.lds. Is it possible that your compiler chain treats leading underscores different. (...) That is _not_ your problem. Take care of the fact (...) (20 years ago, 28-Sep-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: compiling problmes 2
|
|
(...) Some of the functions are inline functions, that are *defined* in the header files, e.g.cputc_hex is defined in include/conio.h. With gcc you need to compile with optimization on, so that it will inline these functions correctly. Another (...) (20 years ago, 27-Sep-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: compiling problmes 2
|
|
Can't be that the unresolved references are from the code I want to add to BrickOS, because I also tried to compile just the BrickOS-files (without the code I want to add) and the same errors appeared. (...) I looked for some of those references and (...) (20 years ago, 27-Sep-04, to lugnet.robotics.rcx.legos)
|
| |
| | Test
|
|
I think my messages don't make it to the group... Test only... (20 years ago, 27-Sep-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: compiling problmes 2
|
|
(...) Could the unresolved referenced be from the code you are adding to brickOS? From the looks of it, some of the unresoveds are probably defined in a header file (all caps is a hint). Maybe they were implied in the GCC compiler, but I doubt it. (...) (20 years ago, 25-Sep-04, to lugnet.robotics.rcx.legos)
|
| |
| | source install brickos - stdio.h: No such file or directory
|
|
I try to install the source of brickos on debian (kernel 2.6.8) like this : ganymedes:~# apt-get -b source brickos When I do this I receive the following error. I checked if I met all the dependencies and there were no problems. make[1]: Entering (...) (20 years ago, 24-Sep-04, to lugnet.robotics.rcx.legos)
|
| |
| | howto apply usb patch to brickos
|
|
Hi, thanks to some responses from this forum I now know that I need to patch brickos in order to function with the usb ir tower. The problem is...I have no idea how to apply this patch. I already downloaded the patch from sourceforge.net: (...) (20 years ago, 23-Sep-04, to lugnet.robotics.rcx.legos)
|
| |
| | compiling problmes 2
|
|
Hi everybody, as I mentioned in my first question I am trying to use BrickOS. But I am not using the Bricx Command Center or something special for the LEGO RCX to compile it, I am using the HEW (Renases tool for the H8/300L microcontroller which is (...) (20 years ago, 23-Sep-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: compiling problems
|
|
(...) Rudolf, I'm not the one to answer your question, but I can tell you this: You need to provide the list of unresolved references before anyone can help you. Unresolved references are typically because not all files are identified in the (...) (20 years ago, 23-Sep-04, to lugnet.robotics.rcx.legos)
|
