 | | 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 (...) (26 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) currently i believe there is some really subtle bug in malloc(), that shows up only under special circumstances. I experience similar problems with a fat kernel/application that disappear after adding one cputw(), making the binary a little (...) (26 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) Or worse, MacOS. I use and love my Macs, but lord they sure don't have much crash protection right now. I just wish there was a way to avoid having to reload the firmware every time it breaks, but I suppose that without an MMU, that's a bit (...) (26 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
Are you using gcc-2.95 or the earlier egcs? What's your host machine? I'm running an Intel Pentium (pre-MMX) and Linux and had to specify the additional parameter: --host=i586-pc-linux Not sure whether BeOS is supported where linux is specified (...) (26 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) I'm afraid that mysterious hangs may be a permanent part of the life of a legOS user- in almost any serious program that I have written, perfectly legitimate code- simple code!- has occasionally caused weird hangs and needed hard reboots. (...) (26 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
