From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ext2srv problem with too many files
Date: Fri, 19 Oct 2012 11:42:19 -0400 [thread overview]
Message-ID: <210856a59562cc3870fd7e858d428e10@ladd.quanstro.net> (raw)
In-Reply-To: <CAM6ozu5mo18=OeRaFt89Co2sTwFZL7oEMrnjvXbiV36bS9VJFg@mail.gmail.com>
> I forgot to say that I'm using the ext2srv version from Plan
> distribution, not the Iruata's from contrib/iru;
> compiling iru's ext2srv gives error:
> term% mk
> 8c -FTVw xfssrv.c
> 8c -FTVw xfile.c
> 8c -FTVw ext2fs.c
> 8c -FTVw ext2subs.c
> 8c -FTVw chat.c
> 8c -FTVw iobuf.c
> 8l -o 8.out xfssrv.8 xfile.8 ext2fs.8 ext2subs.8 chat.8 iobuf.8
> ??none??: incompatible type signatures 392d4f87(xfssrv.8) and
> 2569e19(/386/lib/libc.a(chartorune)) for chartorune
sounds like you have a 9atom-compiled libc.a, but then updated
/386/include/u.h from the distribution overwriting the definition
of Rune. (changing it from uint to ushort). you either need to
recompile all your libraries, or put u.h back the way it was.
- erik
next prev parent reply other threads:[~2012-10-19 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 7:51 Peter A. Cejchan
2012-10-19 13:52 ` Peter A. Cejchan
2012-10-19 15:42 ` erik quanstrom [this message]
2012-10-24 15:00 ` Peter A. Cejchan
2012-10-25 1:40 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=210856a59562cc3870fd7e858d428e10@ladd.quanstro.net \
--to=quanstro@quanstro.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).