> I just hit the following compilation error and I wonder if this is some > sort of bug in the APE libraries and how to trace down what is really > wrong:
I had a similar situation when compiling the entire userland. I hacked each as seemed appropriate, but somebody ought to go in there with a shovel... Thing is, BSD isn't very consistent either and sometimes socket_t * is preferable to uint *, whereas sometimes void * is better than char *. A shovel, indeed. >From memory, don't call me a liar :-) ++L
