Subject:
|
Re: OS X Complier problems solved--now struggling with BrickOS
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Tue, 17 Jun 2003 05:39:10 GMT
|
Viewed:
|
3031 times
|
| |
|
|
In lugnet.robotics.rcx.legos, Rich Warren wrote:
...
> I'm still having some trouble compiling BrickOS. Also with the C++ demos. Is
> this the same problem you had, Michael? Does anyone have any suggestions?
>
> I edited the configure file to include the path to my cross compiler. I then
> ran the configure. Afterwards, I edited both Makefile (deleting utils from
> the list of subdirectories) and Makefile.common (adding the proper prefix
> and the -no-cpp-precomp to CC). I also had to copy Michael's utilities into
> the utility folder.
>
> With that setup, I'm getting the following error.
>
>
> /sw/brickos/bin/h8300-hitachi-hms-g++ -DCXX -O2 -fno-builtin
> -fomit-frame-pointer -Wall -I/sw/brickos/source/brickos-0.2.6.10/include
> -I/sw/brickos/source/brickos-0.2.6.10/include/lnp -I.
> -I/sw/brickos/source/brickos-0.2.6.10/boot -c c++.cpp -o c++.o
> In file included from
> /sw/brickos/source/brickos-0.2.6.10/include/conio.h:53,
> from c++.cpp:34:
> /sw/brickos/source/brickos-0.2.6.10/boot/config.h:124:8: warning: multi-line
> string literals are deprecated
> /sw/brickos/bin/h8300-hitachi-hms-ld -T ../boot/brickOS.lds -relax
> -L/sw/brickos/source/brickos-0.2.6.10/lib c++.o -lc -lmint -lfloat -lc++ -o
> c++.dc1 --oformat coff-h8300 -Ttext 0xb000
> c++.o(.text+0x30):c++.cpp: undefined reference to `operator new(unsigned)'
> c++.o(.text+0x42):c++.cpp: undefined reference to `operator delete(void*)'
> <<numerous duplicate errors snipped>>
> c++.o(.rodata+0x18):c++.cpp: undefined reference to `vtable for
> __cxxabiv1::__si_class_type_info'
> c++.o(.rodata+0x1e):c++.cpp: undefined reference to `vtable for
> __cxxabiv1::__si_class_type_info'
> c++.o(.rodata+0x40):c++.cpp: undefined reference to `vtable for
> __cxxabiv1::__class_type_info'
> make[1]: *** [c++.dc1] Error 1
> rm c++.o
> make: *** [all] Error 2
>
> It seems to be a problem with the linker. But I'm not familiar enough with
> the commands to be sure. Playing around with making some of the demos by
> hand, I got namespace errors, if that helps (the variables from
> dmotor.h--fwd and so forth--created problems in Motor.H).
>
> I'm getting close. I can smell it. I'd really like to have c++ working,
> since I'm much more comfortable writing c++ code than c code. Any help (from
> Michael or others) would be greatly appreciated.
>
> -Rich-
Hmm... I just read your thing, and I realised I'm posting exactly the same
error, different platform (Linux). Are you using g++-3.3? Or is it another
compiler?
Michael (van der Kolff, not Zapp :) )
|
|
Message is in Reply To:
12 Messages in This Thread:
  
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
