On Mon, 19 Aug 2013 17:30:52 +0200 lu...@proxima.alt.za wrote: > > 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 > >
Heh.. that does not sound too encouraging... For both errors, they seem to be blaming bind in libbsd.a so I guess that is where one would have to look first. I have no idea at all how to do anything about it though. "normal" compilation issues where the corresponding code can be traced down are definitely easier ;)
