To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.legosOpen lugnet.robotics.rcx.legos in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / legOS / 3808
3807  |  3809
Subject: 
Re: compiling problmes 2
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Sat, 25 Sep 2004 00:47:19 GMT
Viewed: 
12974 times
  
In lugnet.robotics.rcx.legos, Rudolf Rüssel wrote:
> 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
> included in the LEGO RCXs) and the free compiler Kpit GNUH8 [ELF] Toolchain. I
> am doing this, because I have some other files which need this compiler. If I
> didn't use this compiler I would need to write a lot of assembler code again and
> would spend a lot of time (which I don't have).
> During the compiling phase there are no errors appearing, but during the linker
> phase there appear several "undefined reference" errors (see them below). I
> searched the whole brickOS-folder by text-search, but I didn't find any of the
> references (that means that those definitions of the references are not included
> to BrickOS). Does the Bricx Command Center include some assembler files or does
> the BrickOS need some more assembler files which are not included in the packet?
> Does BrickOS use some predefined assembler files on the RCXs? Or where can I get
> the assembler code of the definitions of those references?
> 
> 
> Below you can see the undefined reference errors:

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.

<snip>

> ..\brickos-0.2.6.10.6\kernel/vis.c:59: undefined reference to `_AD_C_H'
> ..\vis.o(.text+0x2a):..\brickos-0.2.6.10.6\kernel/vis.c:62: undefined reference
> to `_AD_B_H'
> ..\vis.o(.text+0x38):..\brickos-0.2.6.10.6\kernel/vis.c:65: undefined reference
> to `_AD_A_H'
> ..\vis.o(.text+0x67):..\brickos-0.2.6.10.6\kernel/vis.c:72: undefined reference
> to `_cputc_hex_0'
> ..\vis.o(.text+0x71):..\brickos-0.2.6.10.6\kernel/vis.c:74: undefined reference
> to `_cputc_0'
> Phase Linker finished
> 
> 
> Thank you.
> Rudolf

Rudolf,

  Did you also look at header files for these missing unresolveds?  cputc_0
might be a macro.  I dunno.

  It is clear there are some files missing, but if you have searched all the
possible source files, I don't know what else to recommend.

  Have you examined the Makefiles that came with brickos, to see if they can
help find those missing files?

  I wish you luck.

Kevin (I sometimes really hate Makefiles) Clague



Message has 1 Reply:
  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 (...) (22 years ago, 27-Sep-04, to lugnet.robotics.rcx.legos)

Message is in Reply To:
  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 (...) (22 years ago, 23-Sep-04, to lugnet.robotics.rcx.legos)

7 Messages in This Thread:


Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR