From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon, 19 Aug 2013 18:28:51 +0200
From: Jens Staal <staal1978@gmail.com>
To: 9fans@9fans.net
Message-ID: <20130819182851.57522957@Krypton>
In-Reply-To: <03049f58153987df93dbff46f9242c91@proxima.alt.za>
References: <20130819171736.3d6621a9@Krypton>
	<03049f58153987df93dbff46f9242c91@proxima.alt.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] libbsd: incompatible type signatures
Topicbox-Message-UUID: 7282517e-ead8-11e9-9d60-3106f5b1d025

On Mon, 19 Aug 2013 17:30:52 +0200
lucio@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 ;)