From: "Nikolai Saoukh" <nms+9fans@otdel-1.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] vx32 @ FreeBSD: 9vx/a/chan.c:1220: error: conflicting types for 'memrchr'
Date: Fri, 11 Jul 2008 18:58:52 +0400 [thread overview]
Message-ID: <91ca1c8d0807110758q218febafx6054534011c44d3e@mail.gmail.com> (raw)
In-Reply-To: <20080710165101.GA1065@shodan.homeunix.net>
> FreeBSD added memrchr to its libc a couple of weeks ago. The system one uses
> size_t for the len argument; the 9vx one long. Changing that to unsigned
> long probably would make the compiler happy but would most likely choke the
> linker up. I chickened out and just commented out the definition in chan.c.
> Another approach could be to rename memrchr to memrchr9 or the like. By the
> way, drawterm and inferno are affected by that, too.
This function is used exactly one time in the same file (~30 lines
below). What kind (version) of OS does not have memrchr?
next prev parent reply other threads:[~2008-07-11 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 15:32 Nikolai Saoukh
2008-07-10 16:51 ` Martin Neubauer
2008-07-11 14:58 ` Nikolai Saoukh [this message]
2008-07-11 15:24 ` Martin Neubauer
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=91ca1c8d0807110758q218febafx6054534011c44d3e@mail.gmail.com \
--to=nms+9fans@otdel-1.org \
--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).