From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] libbsd: incompatible type signatures
Date: Mon, 19 Aug 2013 17:30:52 +0200 [thread overview]
Message-ID: <03049f58153987df93dbff46f9242c91@proxima.alt.za> (raw)
In-Reply-To: <20130819171736.3d6621a9@Krypton>
> 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
next prev parent reply other threads:[~2013-08-19 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 15:17 Jens Staal
2013-08-19 15:30 ` lucio [this message]
2013-08-19 16:28 ` Jens Staal
2013-08-19 17:04 ` erik quanstrom
2013-08-20 7:17 ` Jens Staal
2013-08-27 3:32 ` erik quanstrom
2013-08-27 6:21 ` Jens Staal
2013-08-27 12:29 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03049f58153987df93dbff46f9242c91@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).