From: jamos@oboj.net
To: 9front@9front.org
Cc: 9front@hera.eonet.ne.jp
Subject: Re: [9front] ape
Date: Sun, 16 Feb 2020 13:47:36 +0200 [thread overview]
Message-ID: <b80b6aaf583f7388f1e248c9e7b6e98c@oboj.net> (raw)
In-Reply-To: <7E33F0D2C6E26293A203442BCED35D57@hera.eonet.ne.jp>
If you compare
/amd64/include/ape/stdarg.h with
/arm/include/ape/stdarg.h or /386/include/ape/stdarg.h
you'll se that it defines some macros differently.
The header files that are different between architectures
lives under $objtype/include, so also for ape headers.
The ports repo that is updated (i.e. the most 'supported' one)
would be the one you find if you go to 9front.org, click on
the menu 'code' and then on 'hg' and scroll down to 'ports'
(i.e. https://code.9front.org/hg/ports) You can clone it with
'hg clone' + that URL.
Jonas
On 2020-02-16 06:59, kokamoto@hera.eonet.ne.jp wrote:
> Stdarg.h is put under $objtype/include/ape, not /sys/include/ape, why?
>
> One more, what is the status of /sys/ports, which is supported?
>
> Kenji
prev parent reply other threads:[~2020-02-16 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 4:59 ape kokamoto
2020-02-16 11:47 ` jamos [this message]
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=b80b6aaf583f7388f1e248c9e7b6e98c@oboj.net \
--to=jamos@oboj.net \
--cc=9front@9front.org \
--cc=9front@hera.eonet.ne.jp \
/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).