From: Jens Staal <staal1978@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ape/errno.h
Date: Tue, 18 Dec 2012 07:08:48 +0100 [thread overview]
Message-ID: <CAK8RtFp2+cVWLi5bd6rX1hT1NgL_nTb-wdsWvCT6DCXP5XVXBw@mail.gmail.com> (raw)
In-Reply-To: <0e795bddf090054bd1044826f5444679@ladd.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
In my porting of stuff using APE, I often notice that many applications
assume more members of the struct stat in sys/stat.h, especially
st_blocksize. Is there any reasonable similar information available
elsewhere in the system that could be used in a local "rpl_stat" struct for
those ports?
other annoying stuff are normally related to malloc/alloca and sys/mtio.h
stdint.h is normally easily just redirected to inttypes.h and stdbool.h can
also easily included.
2012/12/18 erik quanstrom <quanstro@quanstro.net>
> On Mon Dec 17 17:38:33 EST 2012, jas@corpus-callosum.com wrote:
> > I'm not familiar with the full history of /sys/include/ape/errno.h, but
> it looks like EISCON should be EISCONN to fit with other systems that at
> least pretend to be POSIX compliant. SunOS 5.11 did have EISCON, but...
>
> makes sense to me; there are no references to EISCON
> on the system other than the include file.
>
> - erik
>
>
[-- Attachment #2: Type: text/html, Size: 1455 bytes --]
next prev parent reply other threads:[~2012-12-18 6:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 22:06 Jeff Sickel
2012-12-17 23:25 ` erik quanstrom
2012-12-18 6:08 ` Jens Staal [this message]
2012-12-18 6:37 ` Lyndon Nerenberg
2012-12-18 8:35 ` tlaronde
2012-12-18 10:16 ` Richard Miller
2012-12-18 16:43 ` Jeff Sickel
2012-12-18 17:04 ` arnold
2012-12-18 18:03 ` Jeff Sickel
2012-12-18 18:21 ` arnold
2012-12-18 20:02 ` David du Colombier
2012-12-21 18:38 ` Jeff Sickel
2012-12-21 18:39 ` erik quanstrom
2012-12-21 18:54 ` tlaronde
2012-12-24 5:56 ` Jens Staal
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=CAK8RtFp2+cVWLi5bd6rX1hT1NgL_nTb-wdsWvCT6DCXP5XVXBw@mail.gmail.com \
--to=staal1978@gmail.com \
--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).