From: kokamoto@hera.eonet.ne.jp
To: 9fans@9fans.net
Subject: [9fans] what is differece(s) between sources and atom kernel?
Date: Fri, 4 Apr 2014 11:03:17 +0900 [thread overview]
Message-ID: <3448b9061bd0930eb5dc5ac2d1b669a7@jitaku.localdomain> (raw)
I've been considered why pc kernel dosen't work for go compiling,
however pcpae kernel does. The 'sources' pc kernel works fine
(from David's talk here).
In the 'sources' pc kernel, there is a definition of fpssesave etc
in its l.s.
On the other hand, no definition in atom's pc kernel.
However, pcpae kernel have them in l.s (named ssesave etc).
I think this is the cause of different behaviours between them.
Am I right?
If so, why atom's pc (not pcpae) kernel dosen't have them?
I also checked two distributions these a few days.
Atom's distribution has libaml libfis, libxml, but
'sources' doesn't.
May I ask you, developpers of both, what the roadway of the
future of Plan 9?
Kenji
next reply other threads:[~2014-04-04 2:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 2:03 kokamoto [this message]
2014-04-04 2:13 ` erik quanstrom
2014-04-04 3:10 ` Kurt H Maier
2014-04-04 4:13 ` kokamoto
2014-04-04 4:23 ` erik quanstrom
2014-04-04 4:55 ` kokamoto
2014-04-04 5:05 ` lucio
2014-04-04 5:03 ` lucio
2014-04-04 4:49 ` lucio
2014-04-05 4:24 ` kokamoto
2014-04-05 4:40 ` kokamoto
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=3448b9061bd0930eb5dc5ac2d1b669a7@jitaku.localdomain \
--to=kokamoto@hera.eonet.ne.jp \
--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).