9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Martin Neubauer <m.ne@gmx.net>
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: Thu, 10 Jul 2008 18:51:01 +0200	[thread overview]
Message-ID: <20080710165101.GA1065@shodan.homeunix.net> (raw)
In-Reply-To: <91ca1c8d0807100832h51a5916fs98786765429d3896@mail.gmail.com>

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.

I hope that gets you going,
	MArtin

* Nikolai Saoukh (nms+9fans@otdel-1.org) wrote:
> $ uname -a
> FreeBSD NetFaker 7.0-STABLE FreeBSD 7.0-STABLE #13: Wed Jul  2
> 15:04:57 MSD 2008     nms@NetFaker:/usr/obj/usr/src/sys/NETFAKER  i386
> $ gmake
> gcc -g -O3 -MD -std=gnu99 -I.  -I. -I9vx -I9vx/a -Wall
> -Wno-missing-braces -c -o 9vx/a/chan.o 9vx/a/chan.c
> 9vx/a/chan.c:1220: error: conflicting types for 'memrchr'
> /usr/include/string.h:62: error: previous declaration of 'memrchr' was
> here {void    *memrchr(const void *, int, size_t) __pure;}



  reply	other threads:[~2008-07-10 16:51 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 [this message]
2008-07-11 14:58   ` Nikolai Saoukh
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=20080710165101.GA1065@shodan.homeunix.net \
    --to=m.ne@gmx.net \
    --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).