|
|
 | | Re: random() compile problems
|
| (...) Yes, it looks like random is in a private library of mine, sorry. With all the exciting networking development happening, count on 0.2.4 being released soon, it will contain random() again. (...) For small amounts of random numbers, you may (...) (25 years ago, 21-Dec-99, to lugnet.robotics.rcx.legos)
| | | | | Re: random() compile problems
|
| (...) Hi Matthew, it lokks like the functions are simply not defined neither in the legOS kernel nor in the libs. Following the comment in include/stdlib.h, they should be in libiberty.a, which is somewhere in the cross-compiler tree. However, (...) (25 years ago, 21-Dec-99, to lugnet.robotics.rcx.legos)
| | | | | Transmission Problems
|
| Hello. I am using legOS-990330 with the transmission handler patch. I have no problems receiving at all, but periodically strange nonsensical data somehow inserts itself into the output stream with no apparent reason, like ~..y~~ Does anybody know (...) (25 years ago, 20-Dec-99, to lugnet.robotics.rcx.legos)
| | | | | random() compile problems
|
| Hi all, We are having troubles compiling code that makes use of the random() (and srandom()). The error messages that occour when we compile are: undefined reference to '_srandom' undefined reference to '_random' Any help will be greatly (...) (25 years ago, 20-Dec-99, to lugnet.robotics.rcx.legos)
| | | | | linux-lnp: select() vs. SIGIO ( was Re: Call for debugging support )
|
| (...) Uuh, there was a little bug in my test program. Once again, i learned i have to read gcc´s warnings carefully. On linux, select() suffers exactly the same thing as SIGIO. If the hardware fifo of the uart is enabled, and there is a stream of (...) (25 years ago, 20-Dec-99, to lugnet.robotics.rcx.legos)
|
|
