 | | Re: Directions to compile GCC
|
|
Luis Villa <liv@duke.edu> : (...) box (...) for (...) Wow Thanks! Here is the error I am getting-> loading cache ./config.cache checking if compiler cc1obj has been built... yes checking for gcc... h8300-hitachi-hms-gcc checking whether the C (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
I've also been struggling with building the cross compiler. I'm trying to create a DJGPP hosted version. Once I am successful, we will be able to use Markus's legOS on DOS/Windows as-is. Currently, I have to rewrite Makefile.Common, Makefile.Kernel, (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
(...) This may not be the case- the cross-compiler will try to compile something, but at least with the directions most of us use, there is no standard C library created and so the compiler thinks it doesn't work. The trick (then) is to use Markus's (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
"Markus L. Noga" <markus@noga.de> : (...) Thanks! In one of the sections under this document there is a short paragraph explaining that cross compilers may not like having 32 bit ints (Like BeOS uses) turn into 16 bit ints (Like I bet the RCX uses) (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
Jim Jackson <jjackson@jnjackson.com> : (...) GCC-2.95.2 (...) --host=i586-pc-beos (...) This gave me the Idea to tell the configure that I was running a Linux box (instead of a bebox) It almost worked too. At the end of the make the machine says I (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
